Your users report it. It arrives as a backlog item.
End users report bugs and ideas through an embedded widget.
- For
- Teams whose users are outside the building — nobody on your team is in the room when the frustration happens.
- Leads with
- Feedback widget
- Preset goals
- 4 — editable, up to five
- Also uses
- The feedback widget — no install, works in any browser
Feedback comes from people outside your team, so the ways in are asynchronous — they send, you collect.
You cannot invite a stranger to a call the moment their export hangs. What you can do is be there when it happens: a widget in the corner of your own product, or a link you paste into a support reply. They send on their time, you collect on yours.
The capture routes this project puts in front of you.
All seven capture methods work in every Sense project. This template only decides the order — and for collect user feedback, that order starts here.
Share a link, or embed a widget in your product, so anyone can send feedback without an account.
Drop in audio, video, or a document you already have and we will transcribe it.
4 preset goals, written for this situation.
A goal is an extraction prompt: it tells the AI what to pull out of every transcript in this project. These ship with the template and are yours to rewrite — a project holds up to five.
What the user was trying to do, what actually happened, any error message, steps to reproduce, the affected screen, and how badly it blocked them.
The underlying need behind the ask, not just the surface request — plus how often and how urgently it comes up.
Confusion, hesitation, wrong paths, unclear labels, hidden actions, and where in the flow they happened.
What users like, rely on, and are trying to achieve — so the wins can be protected as you change things.
One line becomes an action item, without losing the words.
Nothing here is a summary. Each hop keeps a link back to the one before it, so the item at the bottom still opens onto the sentence at the top.
- 01Capture
A user opens the widget inside your product and sends a report — no account, no install. A widget submission is one person talking to you.
Give us feedbackRecord your screen and voice to walk us through what you ran into.
Record an audioRecord your screen or tab - 02Signal
It lands as a transcript — timestamped, searchable, with the recording attached.
0:01MayaI'm pulling the quarterly numbers out like I do every Monday.0:06MayaI tried to export the report three times and it just spun forever. Ended up screenshotting the whole thing.0:14MayaThe date picker also jumps back to this month every time I reopen it. - 03Anchor
Read against this project's 4 goals, the passage that answers one gets lifted out verbatim and tagged. The anchor keeps its offsets into the transcript.
0:01MayaI'm pulling the quarterly numbers out like I do every Monday.0:06MayaI tried to export the report three times and it just spun forever. Ended up screenshotting the whole thing.0:14MayaThe date picker also jumps back to this month every time I reopen it.Tagged toBugs & breakage - 04Insight
Anchors group into a finding. One insight often draws on more than one goal.
Exporting a full quarter hangs, so people screenshot the report instead
3 anchorsBugs & breakageUsability friction - 05Action item
The finding becomes a backlog item on the workspace kanban, still linked to the anchor it came from.
Fix report export timeout on large rangesTodoTraces back to Maya at 0:06
Every report becomes a signal, and the insights land in your backlog as things to fix or build.
Action items live on the workspace backlog, not inside a single project — so a fix that came out of a testing session sits next to one that came out of an interview, each carrying its own evidence.
A raw complaint arrives already triaged.
- No account, no install, no browser requirement — the widget embeds in your product or lives behind a link you can paste into a support reply.
- The report does not land in a queue for someone to read. It lands tagged against your goals, grouped into an insight, and linked to the sentence that produced it.
- "It just spun forever" and "the date picker jumps back" are two different goals in one submission. Both get pulled; neither gets flattened into the other.
Turn on your feedback widget
Embed the widget or share a link so users can report bugs, requests, and friction without an account. Every report lands here as a signal.
- No account and no install — anyone with the link can send a report
- Embed it in your product, or paste the link into a support reply
- Works in any browser, on the page where the problem happened
The widget and the Chrome extension solve the same problem for different audiences. This template ships with the widget; internal testing and concept demo ship with the extension.
All seven capture methods are available in every project. A template only decides what you see first.
Rewrite, remove, or add to the preset goals at any time. A project holds up to five.
A new workspace is seeded with one project per template. Nothing is locked behind a choice you make on day one.
Every anchor carries its citation offsets into the transcript, so each claim traces back to the words that were said.
Every workspace starts with this project already in it.
Create a workspace and all six projects are seeded for you — this one included, goals and capture order set up. Nothing to configure before your first capture.
Your first run in this project ends on “Set up the widget”. The project tour spotlights the widget zone — the one template you can finish setting up on the spot.