Capturing Feedback
Last updated
Was this helpful?
Last updated
Was this helpful?
Every great product starts with listening. Cycle gives you one home for all the voices — sales calls, support tickets, Slack threads, and more. No more scattered screenshots, lost emails, or “where did we hear this?” moments.
Picture this: A customer shares a bug in Intercom, your sales rep drops a product request in Slack, and your CS team uploads a call summary. All of it—automatically—lands in your Cycle Inbox, ready for action.
In Cycle, Feedback is the raw, unfiltered voice of your users or teammates.
Think of it as the “raw material” before you extract Quotes and connect them to requests. It becomes the system of record for everything your users are saying.
Feedback can be:
A message from Intercom
A support ticket from Zendesk
A screenshot from your phone
A voice recording
A transcript from a sales call
Every Feedback object includes:
Reporter: Who’s responsible for follow-up
Customer: Who gave the feedback
Source: Where did it come from?
Status: “To Process”, “Processing”, “Processed”, or “Canceled”
Any additional custom properties you want:
Feedback type: Churn survey, note, discovery interview,…
Importance: Critical, Medium, Low
Affected platforms: Windows, MacOS, Android, ...
and more,
You don’t need to chase feedback. Cycle brings it to you. There are two different ways of doing this.
Manually drag & drop images, PDFs, audio, videos, or links into Cycle.
Cycle scans screenshots for text (OCR), transcribes audio/video, and embeds files so nothing gets lost.
From anywhere in the app — no friction, no extra steps.
Feedback from those sources is instantly routed to your Cycle Inbox—tagged by source, with the right customer and assignee.
Once feedback lands in Cycle, it’s ready to process and turn into real product direction.
Want to learn how Cycle links every piece of feedback back to the right customer—and why it matters? Check out our
Connect tools like , , , (and ) to your workspace.
Want to set up a specific integration? See our