Feedback & helpdesk

Collect user reports with the embeddable widget, answer reporters by email from a shared support inbox, and fix the bugs on the same boards your team already works.

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 target board: feedback reports land there as ordinary issues, 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.

Helpdesk & support inbox

One switch gives your whole team a helpdesk: Settings → Feedback widget → Helpdesk (Team plan). With it on, support requests from the widget open tickets in your team's shared Support inbox: standalone email conversations with the reporter, not issues. Every member sees the inbox and can answer.

EExponential
Boards
Support
Mara WinklerScreenshot upload never finishes

Hi, when I attach a screenshot to a bug report the upload spinner never finishes. Safari 17 on macOS.

Mara Winkler · 1h

Thanks Mara, I've reproduced it on Safari. The annotation layer is blocking the upload callback; fix is underway.

Danny Strähhuber · 48m

Internal

Same root cause as EXP-13. The annotation flatten re-encode stalls on Safari WebP. Fix rides the next widget release.

Danny Strähhuber · 45m

Great, thanks for the quick response! Happy to test a build.

Mara Winkler · 12m

Reporter
Mara Winkler
mara@heliolabs.io
Last seen 12m ago
Context
https://app.heliolabs.io/reports
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Safari/17.6
Viewport 1728×1024
Escalate
Create an issue from this ticket on one of the team’s boards.
Replies are emailed to the reporter with a private conversation link.

How a thread runs:

  • The reporter gets a confirmation email with a magic link to their own /support/… page (a live view of the conversation, no account needed). They can reply from that page or just answer the email.
  • Your side happens in the Support inbox: replies you write there are emailed to the reporter from your team.
  • Internal notes stay internal, visible to your team on the thread and never sent to the reporter.
  • Closing a thread stops further replies but keeps the transcript readable at the reporter's link.

Escalate to an issue

When a ticket turns out to be a real bug, it becomes work with one click: escalate it into an issue on any board. The ticket keeps the conversation with the reporter. The issue carries the work: status, priority, assignee, labels, and a coding session if the board has a repository.

The thread shows its linked issue, so whoever answers support always knows where the fix stands and can tell the reporter the moment it ships.

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 promote real bugs to Todo. 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.

DogfoodExponential's own feedback runs exactly this setup: the feedback button in the corner of this site is the real widget, the helpdesk answers the support requests, and agents fix the bugs.