Dictate Your Dispute Letter Instead of Typing

The Dispute Letter Generator asks for one piece of writing: a few sentences, in your own words, about what happened. For plenty of people that box is the hardest part of the whole dispute — not because they don't know what happened, but because typing it is genuinely difficult. So the box now has a second way in. In browsers that support it, a Speak instead button lets you say what happened out loud and watch it land in the box as ordinary, editable text. This guide explains who that helps, how it works, which browsers can do it — and, in full, the privacy trade-off that comes with it, because that trade-off is real and you should hear it from us before you ever tap the button.

Who this is for

Dictation exists as an input route for people whom keyboards fail. App listings for dictation tools say it plainly: they are built for users who have difficulty typing on a mobile keyboard, including people with motor impairments or hand-mobility limitations. A dispute letter lands on exactly the people least placed to wrestle a phone keyboard — someone stressed about money, often older, often doing this on a small screen, sometimes with hands that hurt. It also helps if you are simply more confident speaking English than writing it: a spoken account, read back and corrected, is a better letter than a blank box.

Nothing about the letter changes. The structure, the reason templates, the legal framing — all of it is the same generator. Voice is an input method. The dispute intelligence is the product; the microphone is just another way to reach it.

How it works, step by step

Open the Dispute Letter Generator and fill in the short fields as usual — name, bank, card, date, amount. Those are typed fields, and they stay typed (the accuracy section below explains why).
At the "Briefly, what happened?" box, read the line above the button. It tells you, before anything starts, that the dictation is done by your browser and what that means. Then tap Speak instead.
Allow microphone access when your browser asks. Nothing is heard until you allow it, and the page works over a secure connection, as speech recognition requires.
Speak your account — what you bought, what went wrong, what the merchant said. Your words appear in the box as you speak, including rough interim text that settles as you go. If the browser pauses the session, what you already said stays in the box.
Tap Stop, then read the box. Fix anything mis-heard with the keyboard — names especially. The box has a 500-character limit, like typed text; dictated words count the same.
Generate the letter exactly as a typing user does, read the letter itself once through, then copy or download it and send it to your bank yourself. Nothing is ever sent by this page.

The privacy truth, in full

Most voice features are announced as if the words simply appear by magic. They don't, and the honest mechanics matter enough that we print them above the button itself, before first use:

Voice typing is done by your browser — in Chrome, your voice is sent to Google to turn into text. Nothing is recorded by this site. Prefer not to? Typing works exactly the same.

Here is what sits behind that line. The technical documentation for the web's speech-recognition interface (MDN's guide to the Web Speech API) states it without decoration: "By default, using speech recognition on a web page involves a server-based recognition engine. Your audio is sent to a web service for recognition processing, so it won't work offline." In Chrome, that service is Google's. In Safari, the browser asks before sending audio to Apple's service. Either way, the transcription is performed by your browser vendor — not by this website, and not on this page.

What this site itself does is: nothing. There is no recording code here, no audio is sent to us, nothing about your dictation is stored or shared by Chargeback Clock, and the text that lands in the box is handled exactly like typing — it stays in your browser and leaves only when you copy the finished letter yourself. But because the browser's half of the bargain involves your voice leaving your device, we will never describe this feature as private, and we would rather lose the tap than win it under a false impression.

If the trade-off isn't for you, you have real options. Typing works exactly the same — every field, every template, nothing held back. Or use your phone keyboard's own dictation button, which fills the same box: that route is run by your phone's maker rather than your browser, so check its settings if the same question matters to you there.

Which browsers can do it

Speech recognition on the web is unevenly supported, and pretending otherwise would strand a large minority of visitors. From MDN's browser-compatibility data:

Chrome — supported (version 33 onward, via the prefixed interface).
Edge — supported (Chromium-based, prefixed interface).
Safari — supported (14.1 onward on macOS, 14.5 onward on iOS, prefixed; it prompts before sending audio to Apple's service).
Firefox — not supported. The interface exists only behind an experimental flag, so for Firefox visitors the button is replaced by a short note saying voice typing isn't available in their browser — and typing carries on, exactly as usual.

The feature detects support before offering anything: if your browser can't do it, you are never shown a button that fails. Sessions can also end on their own mid-dictation — the browser's service closes them — so the tool preserves everything already dictated and can resume without losing your words.

Accuracy: read it before you send it

Speech engines are tuned for conversation, and a dispute letter is not conversation. The content it handles worst is precisely the content a bank letter can least afford to get wrong: an amount like "$1,247.09 on March 3rd", a merchant's exact name, a reference number. That weakness is designed around, not wished away:

Figures stay typed. The amount, the transaction date, your name and the card's last digits are separate typed fields in the generator. Dictation can only ever fill the free-text story box — dictated numbers are never read out of your speech into the letter's structured facts.
Everything dictated is a draft. The words land as editable text, and the normal flow already puts the finished letter in front of you before you copy it. That preview is your check: read the story and the figures once through, the way you would proofread anything you sign.
Say it plainly. If you mention dates or amounts inside your story, say them slowly and simply, then verify them in the box against your statement. Where a spoken detail and your statement disagree, the statement wins.

A mis-heard word in a chat message is a laugh. The same error in a formal letter to your bank is a factual mistake with your signature under it — which is why the guardrails above are part of the feature, not fine print under it.

The alternatives, honestly

Voice input for complaint letters is not an idea we invented, and one product deserves naming. WordIt (wordit.app) is a complaint-letter service whose own FAQ says you can describe your problem "typing or using the mic". It is a general tool — billing disputes among many consumer problems — and it is freemium: a small number of free letters a month, with paid tiers (listed at $4.99 and $9.99 a month) for full use. If you want a general complaints assistant and are happy to pay, it exists and it works.

What is different here is the combination, not the microphone: the dictation is free, needs no account, and feeds a letter built on dispute structure — the reason templates, the Fair Credit Billing Act and Regulation E framing, the deadline awareness the rest of this site is built around. Generic dictation apps, for their part, turn speech into tidy text and know nothing about disputes at all. Use whichever route gets a true, checked letter to your bank before your deadline; that deadline, not the tooling, is the part that cannot move.

FAQ

Does Chargeback Clock record or store my voice?

No — this site has no recording code and receives nothing when you dictate. The transcription is done by your browser's own speech service: in Chrome your audio is sent to Google to be turned into text, and Safari asks before sending audio to Apple's service. What appears on this page is text in a box, handled exactly like typing. If that trade-off is not for you, typing works exactly the same — that is written above the button, before you ever tap it.

Which browsers can use Speak instead?

Chrome, Edge and Safari in their recent versions — all three expose the browser speech-recognition interface (in prefixed form). Firefox cannot: Mozilla's compatibility data lists speech recognition as unsupported there, present only behind an experimental flag. If your browser cannot do it, the button is replaced by a short note saying so, and every field works by typing, exactly as before.

Can I dictate the amount and the date too?

No — deliberately. In the generator, the amount, the transaction date, your name and the card details are separate typed fields, and dictation only ever fills the free-text "what happened" box. Speech engines are built for conversation and are at their weakest on exactly the things a bank letter cannot afford to get wrong: figures, dates and names. A mis-heard amount in a letter you sign is a real error with your name on it, so the figures stay typed, where you can check them digit by digit.

What if the words come out wrong?

Then you fix them the ordinary way: everything dictated lands as editable text in the box, nothing is finalised and nothing is sent anywhere by the page. Read the box before you generate the letter, correct names and details with the keyboard, or delete the lot and type instead. The finished letter is only ever copied or downloaded by you, so the last check before anything reaches your bank is always yours.