Collect feedback
The embeddable widget is how the outside world reaches your team: paste its snippet on your site and visitors can report bugs and ideas without ever leaving the page. Your boards stay private. Members triage what comes in.
- Each widget picks a board: every submission lands there as an ordinary issue, titled from the first line of the message, with the annotated screenshot attached and the metadata (page URL, browser, custom data) in the description.
- The reporter is auto-subscribed. Resolve the issue and the person who reported it is notified.
- Connect the board to your app's repository and your agents can fix reported bugs straight off the board.
The reporter conversation
A submission is an issue, and the conversation with the person who sent it happens in that issue's comments. There is no separate inbox to watch and nothing to escalate: the report, the fix and the reporter are one thing.
How it runs when the reporter left an email:
- They get a confirmation email with a private link to their report: a page showing what they sent, their pictures, every reply you addressed to them, and a reply box. No account needed.
- On the issue, the comment composer grows a Reply to reporter toggle. It is off by default, so an ordinary comment stays with the team. Switch it on and that comment is emailed to the reporter and marked to reporter on the issue. A toast tells you whether the mail actually went out.
- When they answer through their link, the answer shows up as a comment on the issue, under their name (or “Anonymous visitor”), and lands as a reporter reply row in the inbox of everyone subscribed to the issue and its assignee.
- An answer on an issue that was already done reopens it, back to Backlog, so a “this still happens” never goes unseen.
Team comments never reach the reporter unless you flip the toggle. Reporter comments can be removed by any member but edited by nobody, and whatever a reporter writes is shown as plain text, never rendered as markdown. Agents and scripts do the same over MCP: exponential_comments_create with audience: "reporter".
Triage
Feedback lands as ordinary issues on a board, so triage is the workflow your team already knows: set priority, label it, move noise to Cancelled, mark repeats as Duplicate, and pull real bugs into In Progress. Or bulk-select a batch of them and hand it to an agent.
When the fix lands, the reporter is notified. The loop closes with the person who reported it.