use case · support teams
Answer at talking speed. Show, don't retype.
Support is explaining — the same steps, the same fixes, ticket after ticket, typed by hand. Say the reply instead, and when the answer is "click here, then here", send a picture with the here already circled.
replies at talking speed
Put the cursor in the reply box — helpdesk, shared inbox, live chat, whatever your team uses in the browser or on the desktop — press Ctrl ` , and talk. The reply appears as editable text: check it, tweak it, send it.
Fast shouldn't read as rushed. A voice mode tidies the grammar and drops the filler before the words land, so spoken answers still sound considered — free on the built-in local model or your own Ollama server, and Pro can route it through your own OpenAI or Claude account.
show them where to click
- 1
Press Alt `
Drag over the part of the screen the customer needs — the panel, the button, the field.
- 2
Talk while you draw
Arrow the button, circle the field, box the setting — and narrate the fix as you go.
- 3
Paste into the ticket
The annotated screenshot and your transcribed words land together — no save, no attach, no writing the steps up twice.
and for what you pass along
The bugs customers find have to travel onward too. Same gesture: crop the error, circle the odd part, say what happened — and paste it into the team chat or the bug tracker. The picture carries the evidence; your words carry the story.
customer data stays put
Support screens are full of other people's details, so where this runs matters: by default your speech becomes text on your machine, screenshots stay in a local folder, audio isn't uploaded to anyone, and the app tracks nothing. What reaches the ticket is exactly what you paste into it. The full network-use table →
Windows 10/11 today — macOS and Linux builds are on the way. Also see dictating email and speech to text for Windows.