Dictate professional emails that don't sound robotic
Voice-dictated emails sound canned when the cleanup is wrong. The fix isn't more editing — it's picking the right tone preset, structuring how you speak, and building a snippet library that handles the boilerplate. Here's the playbook.
The most common complaint about AI-cleaned voice emails: "It sounds like a robot wrote it." Sometimes that's the model. More often it's how the user is speaking — and which tone they've picked.
Here's how to dictate professional emails that read like you wrote them deliberately, in 5 minutes instead of 15.
Why dictated emails sound robotic
Three failures, in order of how common they are:
- Wrong tone selected. Dictating with "Professional" tone for a quick check-in produces stilted formal output. The model did its job; the tone was wrong.
- Generic dictation. If you just say "I wanted to follow up on our conversation," the model produces a generic follow-up. Specificity in your input produces specificity in output.
- Default model instinct to formalize. Most cleanup models default to "polite business English." Without explicit tone guidance, they round off your voice into corporate prose.
The right tone for each email type
Internal team check-ins
Use Slack tone, not Professional. Output is tighter, less formal, drops the "Hi Sarah, I hope you're well" opener that feels weird from a coworker.
Example dictation: "let's move the design review to thursday at three instead of wednesday — i have a conflict"
Slack-tone output: "Can we move the design review to Thursday at 3 instead of Wednesday? I have a conflict."
External (clients, partners, vendors)
Use Email tone for these. Output has a proper greeting, structured body, clean closing.
Example: "thanks for sending the proposal — i had questions about headcount in year two and pricing on the implementation phase"
Email-tone output: "Hi [Name], thanks for sending the proposal. I had a couple of questions before we finalize: first, the headcount estimates for year two; second, the pricing on the implementation phase. Could you walk me through your thinking on these? Best, ..."
Sensitive or high-stakes (escalations, complaints, firings)
Use Professional tone. Output is measured, doesn't add familiarity, keeps emotional language out.
For these, edit carefully after dictation. AI cleanup is good but high-stakes emails deserve a human pass.
Warm replies to customers/users
Use Friendly tone. Adds light warmth without being saccharine, opens with acknowledgement, ends with an offer to help.
How to dictate so output reads natural
Be specific in your dictation
Generic input gets generic output. Compare:
- Generic: "I wanted to follow up on the project." → Output: bland follow-up.
- Specific: "I wanted to follow up on the API integration milestone — we're at 80% complete, the OAuth piece is the only remaining blocker, and I think we can ship by Friday if QA passes." → Output: detailed status with concrete asks.
The cleanup polishes phrasing; it doesn't add information you didn't say. Say the specifics out loud.
Speak the structure
If you want bullets, say "first... second... third..." The cleanup will format as a list. If you want short paragraphs, pause between them — the model uses pauses as paragraph signals.
Self-correct out loud
Don't backtrack and re-dictate. Just say "scratch that, I meant..." and continue. Cleanup applies the correction automatically and your first attempt vanishes.
End with the ask
Emails that end without an ask feel incomplete. Get in the habit of closing with "Could you...", "Would you mind...", "Let me know..." The Email tone formats this naturally into a closing.
The snippet library that handles the boilerplate
Email-specific snippets that save the most time:
- "sig" → your full signature block
- "name" → your full name (for emails where you intro)
- "email" → your email address (for forwarding requests)
- "phone" → your phone number
- "calendar" → link to your scheduling tool
- "thanks" → "Thanks for reaching out — appreciate your patience while I get to this."
- "sorrydelay" → "Apologies for the delay in response."
- "calltoaction" → "Let me know if Thursday works to discuss further."
Once these are in muscle memory, you dictate the personalized part and let snippets handle the framing.
The 4 emails you write every week — templated
The "thanks for connecting" follow-up
Tone: Friendly. Pattern:
- Acknowledge the conversation
- One specific thing they said you liked
- One concrete next step
- Close warmly
The status update to your boss
Tone: Slack (or Professional if senior leader). Pattern:
- One-sentence status
- What's done
- What's next
- Any blockers
The "checking in" with a stale lead
Tone: Friendly. Pattern:
- Light reference to last contact
- One specific reason you're reaching out now (new feature, new pricing, etc.)
- Concrete ask (a 15-min call, a yes/no on continuing)
The "saying no" email
Tone: Professional. Pattern:
- Thanks for the ask
- The no, plainly
- One sentence explaining (without justifying)
- Suggested alternative if you have one
How long it actually takes
Once you've got tone shortcuts + snippets dialed in:
- Short internal reply: 30 seconds
- External follow-up: 2 minutes
- 5-paragraph proposal response: 4-5 minutes
- High-stakes escalation (with edit pass): 8-10 minutes
That's roughly 1/3 of the typed equivalent. For a typical 30-email morning, you're talking 30 minutes instead of 90.
Try Pithflow free
Voice dictation that's faster than typing. Hold a key, speak, get clean text in any Windows or Mac app. Free tier: 2,000 words a week, no credit card.