← Back to Blog

Short answer: Help Scout has no built-in dictation, but a system-wide voice-to-text tool like Voice Keyboard Pro types wherever your cursor is. Click into a reply, note, or Docs article, hold a hotkey, speak, and release. Your words appear as clean text, ready to send.

Help Scout built its reputation on making support feel human. Replies come from a named person, not a ticket robot, and the whole product is designed around conversations rather than case numbers. There is just one problem with human-sounding support: humans have to write it. A support inbox with forty conversations in the queue means forty replies that each need a greeting, a real answer, and a sign-off that does not sound copy-pasted.

Most support professionals speak far faster than they type. Average typing speed sits around 40 words per minute, while natural speech runs 130 to 150 words per minute. Over a full day of replies, private notes, and knowledge base updates, that gap is the difference between clearing the queue and carrying it into tomorrow. This guide covers how to dictate every writing surface in Help Scout, which fields you should still type, and the habits that keep dictated support replies sounding as warm as Help Scout intends them to be.

Why Help Scout Does Not Have a Mic Button

Help Scout runs in the browser, and browsers do not give web apps a dictation button by default. macOS has a built-in dictation feature, but anyone who has tried it in a busy web editor knows the limits: it needs to be toggled from a menu or a double-press of a key, it struggles with product names and technical vocabulary, and it inserts text with a delay that makes the editor feel unreliable.

The better approach is a voice tool that works at the operating system level. Voice Keyboard Pro is a small Mac menu bar app that types wherever your cursor is, in any application. Hold a hotkey, speak, release, and the text appears at your cursor. Because it behaves exactly like typing, Help Scout cannot tell the difference. The reply editor, the note field, the search bar, and the Docs article editor all accept dictated text the same way they accept keystrokes.

That system-wide behavior matters more in support than almost anywhere else, because a support person's writing is scattered across surfaces. In a single conversation you might write a customer-facing reply, an internal note for a teammate, and a quick edit to the Docs article the customer should have found. One hotkey covers all three.

The Four Writing Surfaces in Help Scout

1. Replies: the main event

The reply editor is where you spend most of your day, and it is the surface where dictation pays off fastest. Open the conversation, click Reply, and speak your answer the way you would explain it to the customer on a call:

"Hi Maya, thanks for the screenshot, that helped a lot. The export button greys out when the date range is longer than 12 months. If you split the export into two ranges it will run fine. We're working on lifting that limit, and I'll follow up on this conversation when it ships."

Speak the punctuation ("comma", "period", "new paragraph") and the reply arrives formatted and ready to review. Notice what happens to the tone: dictated replies naturally come out the way you speak, which is exactly the register Help Scout's whole philosophy aims for. Typed replies drift toward stiff, abbreviated support-speak because typing is effort and effort gets minimized. Spoken replies stay conversational because speaking full sentences costs nothing.

The same pattern applies in other help desks too. We have written similar guides for dictating in Zendesk and dictating in Intercom, and the core rule carries over: speak the sentences, and let the tool handle the typing.

2. Private notes: where honesty lives

Help Scout's notes are the internal side channel: "@Sam this is the third report of the export bug this week, can you check if the fix is in the next release?" Notes are exactly the kind of writing people skip when typing is the bottleneck. The result is conversations that get assigned to a teammate with zero context, and the teammate has to re-read the whole thread.

Dictation removes the excuse. A thorough handoff note takes fifteen seconds to speak: what the customer wants, what you already tried, what the teammate should do next. Speak the @-mention trigger by typing @ and selecting the teammate, then dictate the rest. Your future colleagues will notice the difference.

3. Saved replies: draft them out loud

Saved replies are Help Scout's canned response system, and the reason most teams' saved replies sound robotic is that they were written as templates rather than as answers. Here is a better workflow: the next time you dictate a particularly good reply to a common question, copy it into a new saved reply before you send it. Because it was spoken first, it reads like a person wrote it, and every future use inherits that tone. Dictate the variable parts fresh each time (the customer's name, the specific detail) and let the saved reply carry the structure.

4. Docs articles: the knowledge base you keep postponing

Help Scout Docs is the self-service knowledge base, and it is the highest-leverage writing surface in the product: one good article deflects hundreds of future conversations. It is also the writing that always slips, because it feels like a project rather than a task.

Dictation changes the economics. You just answered the question in a conversation, so the explanation is already in your head. Open Docs, create the article, and talk through the answer while it is fresh: what the feature does, the steps in order, the one gotcha customers hit. Speak "new paragraph" between steps, then spend five minutes tightening the draft, adding screenshots, and formatting the headings. An article that would have waited three weeks as a to-do item exists by lunch. For a broader look at voice workflows across the support role, see our guide to voice to text for customer support.

Speak the Sentences, Type the Identifiers

Dictation is for prose. It is not for the structured fields around the prose, and knowing the boundary keeps your Help Scout data clean:

A spoken order number like "1-0-0-4-7-3-9" will usually transcribe correctly, but "usually" is not good enough for an identifier that routes a refund. Copy-paste identifiers from the customer's message instead. The prose around them ("I've issued the refund for order 1004739, you'll see it in 3 to 5 business days") is fair game for the mic, since you can verify the number at a glance before sending.

Teach It Your Product's Vocabulary

Every product has a private language: feature names, plan tiers, integration partners, internal code names. Generic dictation tools mangle these because they have never seen them. "Webhookrelay" becomes "web hook really" and you spend the saved time fixing it.

Voice Keyboard Pro's Smart Vocabulary is a personal dictionary with replacement rules. Add your product's feature names, your plan names, and the third-party tools your customers mention, and the transcription engine gets them right the first time. Support teams should also add the short list of customer-facing spellings that matter: is it "sign-in" or "log in" in your docs? Add the rule once and every dictated reply matches your style guide automatically.

The Tone Trap (and the Fix)

One honest warning about dictating support replies: speed cuts both ways. When a customer is rude, the frustrated reply you would have cooled down while slowly typing can now be produced at full speed. The mic is faster than your better judgment.

Two habits fix this. First, dictate the venting version into a private note instead of the reply box if you need to get it out of your system. Second, on iPhone, Voice Keyboard Pro includes Voice Edit: select the text, speak a change like "make this friendlier" or "remove the second sentence", and the fix is applied. It is the fastest way to turn a heated first draft into the reply you actually want on the record.

Help Scout on iPhone: Triage Without Thumb-Typing

Help Scout's mobile app is good for triage: checking the queue in the morning, reassigning conversations, sending quick replies. What makes mobile support painful is thumb-typing anything longer than a sentence.

Voice Keyboard Pro's iPhone app is a custom keyboard with a built-in mic button, so it works inside the Help Scout app the same way it works everywhere else on iOS. Tap into the reply field, tap the mic, and speak the answer. Two features matter especially for support:

Swipe typing rounds out the keyboard for the words you would rather not say out loud on a train.

A Realistic Day of Voice-First Help Scout

Here is what the workflow looks like in practice, without pretending everything becomes voice:

  1. Morning triage (iPhone): scan the queue over coffee, dictate two quick replies to the easy ones, leave a spoken note on the tricky one so it lands assigned with context.
  2. Queue block (Mac): work through conversations oldest-first. Dictate each reply, type the tags, click the workflows. A reply that took three minutes to type takes about one to speak and review.
  3. After a repeated question: thirty seconds to save the reply you just dictated as a saved reply, or ten minutes to talk a Docs article into existence.
  4. End of day: dictate handoff notes on anything still open, so tomorrow's first hour is not archaeology.

The point is not that you never touch the keyboard. It is that the keyboard becomes the tool for identifiers, shortcuts, and edits, while your voice handles the part that was always the real work: explaining things clearly to another human being.

What About Customer Data and Privacy?

Support conversations contain customer information, so it is fair to ask where dictated audio goes. Voice Keyboard Pro's transcription happens through the app's transcription engine, and our server stores only operational pings: no audio recordings and no transcript content are stored on our servers. Your dictated text goes to your cursor and stays in your Help Scout account, where your existing data policies already apply.

That said, if you work somewhere with a formal policy about third-party tools touching customer data, check with your IT or compliance team before rolling any dictation tool out to the whole support team. We would rather you ask first than assume.

Frequently Asked Questions

Does Help Scout have built-in voice dictation?

No. Help Scout has no native dictation feature in the web app or the mobile apps. You need a system-level tool: macOS dictation at minimum, or a dedicated app like Voice Keyboard Pro for speed, accuracy on product vocabulary, and hotkey convenience.

Will dictated text work in Help Scout's Beacon or live chat?

Yes. Because a system-wide voice tool types at your cursor, it works in any text field Help Scout renders, including chat replies. For live chat, keep replies short and review before sending, since chat customers see response timing.

Can I dictate in Help Scout on Windows?

Voice Keyboard Pro is built for Mac and iPhone. On Windows, the built-in Win+H voice typing works in the browser, though without the personal dictionary and hotkey workflow described here.

How much does Voice Keyboard Pro cost?

There is a free tier with daily limits, which is enough to test the workflow on a real day of support. Pro is $4.99 per month or $34.99 per year, which unlocks unlimited use. For a support professional writing several thousand words a day, the time saved covers the cost in the first morning.

The Bottom Line

Help Scout wants support to sound like a person. Speaking is how people sound like people. Put the two together and the tool fits the philosophy: dictate your replies, your notes, and your Docs articles, type your tags and order numbers, and spend the reclaimed hours on the conversations that actually need thought. Try Voice Keyboard Pro free and clear tomorrow's queue with your voice.