Cycle's help center
LegalCompany
  • πŸš€Get started
    • πŸ€”What is Cycle? [Start here]
    • πŸ“₯Centralize feedback
    • πŸ’‘Extract insights from feedback
    • 🌱Document features in your roadmap
    • πŸ“‘Write your release notes and close the loop
  • πŸ’ͺCore concepts
    • 🏑Home
    • πŸ“₯Feedback
    • πŸ’‘Insights
    • ⛰️Roadmap
    • πŸ”ŠReleases
    • 🀩Closing the loop
    • ⚑Cycle AI
    • πŸ“ŠCustomer voice dashboards
  • πŸ₯³Latest Features
    • 🧠Custom Prompts
    • πŸ“‚Product Areas
    • πŸ“ŠCycle Dashboards
    • πŸ€–Cycle Ask – Your On‑Demand Product Analyst
  • βš™οΈSetup
    • πŸ”ŒIntegrations
      • Slack
      • Linear
      • Intercom
      • Zendesk
      • Salesforce
      • Gong
      • HubSpot
      • Zapier
      • Chrome extension
      • Figma, Loom, Miro & Pitch
      • Email
      • Notion
      • GitHub
      • Modjo
    • Product areas
    • πŸ“‹Views
    • 🏷️Properties
    • πŸ‘±Customers
    • 🎭Manage workspace members
    • πŸ””Notifications
    • πŸ”€Statuses
    • ✏️Collaborative, rich markdown and AI-powered editor
    • πŸ”“Security
  • 🚲Advanced
    • πŸŽ‰Public changelog
    • πŸ€–AI & automations
    • πŸ“ΉCall recording
    • πŸ“šContent templates
    • πŸ”οΈAdvanced Roadmaps and custom views
    • βš’οΈMultiple doc types
    • πŸ”Search
    • πŸ†Pro Cycler tips shortlist
    • ⌨️Keyboard shortcuts
  • πŸ”SAML/SSO
  • πŸ‘¨β€πŸ«Cycle University
    • πŸ‘οΈBest practices for views
    • 🏎️Fast-track your onboarding
    • 🐞Bug handling with Cycle
    • πŸ’»API
      • ⚑Webhook event for all properties changes
      • πŸ”—How to integrate with Jira Product Discovery
    • ❓FAQ
  • πŸ€”Guides
    • ⬇️Migrate your data to Cycle
      • Canny migration
    • πŸ“–Glossary
    • Synchronise your customer data
  • 🧱Core Documentation
    • πŸš€Capturing Feedback
    • ⚑Processing Feedback
    • πŸ“ŠAnalyzing Data
    • 🀩Closing the Loop
    • βš™οΈGetting Started / First Workspace Setup
  • πŸ“šGuides
    • πŸ”—Integrations
      • HubSpot
      • Salesforce
      • Linear
      • GitHub
      • Notion
      • Slack
      • Intercom
      • Zapier
      • Call recording
      • Email
      • Chrome extension
      • Gong
      • Zendesk
      • Modjo
    • πŸŒ†Views
    • πŸ“AI-powered editor
  • πŸ“–Cycle Glossary
Powered by GitBook
On this page

Was this helpful?

  1. Get started

Extract insights from feedback

Insights are valuable pieces of information you want to link to a feature.

PreviousCentralize feedbackNextDocument features in your roadmap

Last updated 4 days ago

Was this helpful?

We see feedback like a diamond πŸ’Ž.

At first, it is rough, unfaceted, and unpolished. But with some work, it gets extremely valuable.

Here's how to create Insights from Feedback... or polish your diamond.

  1. Highlight the relevant piece of text in the feedback

  2. Click on πŸ’‘ (or hit ⌘1) to create an Insight

  3. Link it to the right 🌱 feature, or create a new one

Try it yourself πŸ‘‡

Every insight you create will appear in the insights panel on the right. They will also inherit the properties of the feedback they came from.

This includes:

  • Customer – Who gave the feedback?

  • Assignee – Who's in charge of processing the feedback or acting on it?

  • Source – Where did the feedback come from?

  • – You'll use them to organize feedback the way you see fit.

Once you're done extracting Insights from Feedback, mark the Feedback as "processed"

You'll find them all in your Insights section on the left side panel.

Now that you're familiar with creating Insights from feedback and linking them to features, let's πŸ‘€.

πŸš€
πŸ’‘
learn how to prioritize features and write your PRDs
Custom properties
Mark feedback as processed once you're done extracting Insights