Voice bug reports
Users describe what broke in their own words. You get steps, expected and actual.
The widget asks
"What went wrong? Tell us what you were doing."
Press and talk, or type instead
Your team gets
- A one-line title
- Steps to reproduce
- Expected and actual result
- Page, browser and device
- Urgency
An example, said and sorted
What the user said
"Um, hi, so I was trying to export my invoices, the March ones, and I click the export button and it just spins. Like forever. I tried twice, I refreshed, same thing. I'm on Safari on my Mac. It worked fine last week, and I kind of need these for my accountant by Friday."
What the team gets
Invoice export spins forever on Safari
Exporting March invoices never finishes. It worked last week.
- Steps: open Invoices, pick March, click Export
- Expected: a file downloads
- Actual: spinner never stops, same after a refresh
- Browser: Safari on macOS
Mood: Frustrated · Urgency: High, needed by Friday · Sent to: Issue tracker, Billing team
Written example to show the format. Not a real customer.
Questions
Why would a user speak a bug report instead of typing it?
Describing a problem out loud takes a few seconds and needs no form. People tend to include the steps and the context they would leave out of a text box.
What does my team receive from a voice bug report?
A written ticket: a short title, steps to reproduce, what the user expected, what happened, urgency, and the page and browser it was sent from. The full transcript is attached.