Your users report it at the moment of friction.
A launcher on your site that starts recording a user's voice and screen in one click. No account, no form.
- Who it is for
- Teams whose users are outside the building, where nobody on your team is in the room when the frustration happens.
- The situation
- You cannot invite a stranger to a call the moment their export hangs. What you can do is be there when it happens — a launcher in the corner of your own product, or a link you paste into a support reply.
Four steps, and you only do the first one.
- 01One click starts the recording
The launcher captures the user's voice and screen together. No account to make, no form to fill in.
- 02They can point at the problem
Snapshots can be cropped, drawn on, and commented, so the report shows the thing rather than describing it.
- 03You approve what comes in
Nothing enters your workspace until you let it, so the inbox stays yours.
- 04Reports arrive already triaged
Each one is read against the project's goals and lands as bugs, requests and friction — with the reporter still attached, so you know who to tell when it ships.
- Public intake links collect feedback from people who have no account and no login — same pipeline, nothing to embed.
- This site runs the widget. The launcher in the corner of this page is the real thing, not a mockup.
What it is called inside the product.
Every capture route works in every project — a template only decides which one you reach for first. These are the ones this surface gives you.
Share a link, or embed a widget in your product, so anyone can send feedback without an account.
The same five hops, whichever door it came through.
Nothing along this chain is a summary. Each anchor keeps its offsets into the transcript, so the action item at the end still points at the words that were said.
- 01Capture
One recording, upload, paste, or widget submission.
- 02Signal
It lands as a timestamped transcript with the recording attached.
- 03Anchors
The lines that answer a goal get pulled out verbatim and tagged.
- 04Insights
Anchors group into a finding, often spanning more than one goal.
- 05Backlog
Findings become action items, each linked back to its evidence.
One project reaches for this first.
Every workspace is seeded with all six projects, so none of this is a choice you make on day one. These are the ones whose capture card puts this surface at the top.
Try it on your own product.
Create a workspace and the projects are already there, goals and capture order set up. Nothing to configure before your first capture.