Conclude collects feedback through three surfaces, all of which feed into the same place — your product's feedback list.
The three surfaces
Public feedback board
A standalone, shareable URL where customers can submit, vote on, and read feedback. No login. Best for community-style product feedback.
In-app widget
A button you embed in your app that captures feedback in context, with optional screenshot and screen recording. Best for logged-in product surfaces where context matters.
REST API
A direct API for piping feedback in from anywhere — your own form, a chatbot, an internal tool, a CSV import. Best when you already have a funnel and want Conclude to enrich and organize it.
What happens when feedback arrives
Every piece of feedback runs through the same pipeline regardless of how it arrives:
- Capture — title, body, optional screenshot, optional recording, optional submitter identity.
- Categorise — AI assigns a category (bug, feature, idea, etc.). Available on every plan.
- Detect duplicates — Conclude checks for near-identical feedback already submitted and surfaces matches. Available on every plan.
- Embed — vector embeddings power similar-feedback search.
- Cluster into themes — on Pro+, similar items roll up into themes you can act on.
- Notify — your Slack channel pings if you've connected Slack and configured rules.
By the time you open the feedback in the dashboard, all of the above has already happened.
Where feedback lands
Feedback always lands in the product it was submitted against:
- Widget — uses the API key, which is scoped to a product.
- Public board — board URL is per-product.
- API — caller specifies the product.
You read all of it from the Feedback page inside that product.
What you can do with it
Once feedback is in the dashboard, your team can:
- Change its status (triage, planned, in progress, shipped, etc.).
- Comment on it (visible to your team only).
- Add labels for taxonomy.
- Link it to a Linear issue, or auto-create a Linear issue from it (Pro+).
- See it grouped with similar feedback in themes (Pro+).
- See it referenced in insights (Team).