← BlogFor non-native-english

Sharp on calls, careful in Slack: why voice dictation doesn't solve the real ...

Sharp on calls, careful in Slack: why voice dictation doesn't solve the real problem

You explained it perfectly on the call. Three minutes, clean thread, the decision was clear. Then you open Slack to recap for your team and stare at a blank message for 20 minutes.

You know exactly what you said. You know it was coherent. But typing it out, something changes. The sentences feel less direct. The tone feels hedged. You read the draft again. Then again. The real barrier isn't vocabulary or grammar. It's the person who appears on the page.

This is the tax of writing in your second language when you're not a beginner.

The gap between the call and the message

Maria is a senior account executive. German background, eight years closing deals with US enterprise buyers. On client calls, her presence is there. Her manager's last review: "Exec presence is a real strength." Then the same review: "Could be more concise in writing."

Maria knows this isn't actually true. She's not less concise when she speaks. The medium is different. Speaking is her native tool, accent and all. Writing is where she feels exposed, so she becomes careful. Three reads before send. Four, sometimes.

The time cost is real. A message that explains itself live in three minutes might take 25 minutes to draft in Slack, because the drafting isn't about finding the words. It's about finding the voice that survives the page.

Why Wispr Flow and other voice tools don't solve this

Maria tried Wispr Flow six months ago. It seemed like the obvious answer: dictate into Slack, no more typing. The pitch is simple: speak naturally, get clean text.

What actually happened was worse. Wispr captured everything. Her filler words. Her German sentence rhythms bleeding into English word order. The hesitation in her voice became hesitation in the text. She had to rewrite anyway, which meant the voice tool didn't save time; it just moved the rewrite point. And because it captured her natural speaking patterns, she felt more exposed, not less.

Otter.ai, which charges $14.99 per month for unlimited recordings, works differently: it's a transcription service. It captures everything you say, verbatim, including "um" and false starts. For learning conversations or interviews, that's useful. For real-time Slack composition, it means you're sending a transcript, not a message. You still have to edit.

Microsoft Voice Typing, which is free and native to Windows, at least doesn't charge. But it does the same thing Wispr does: captures speech as-is. For native English speakers, that works fine. For non-native speakers whose accent shapes their rhythm, it's a mirror you don't want to see.

The pattern is the same across all of them: they capture your voice exactly as it comes out. For someone excellent on calls but careful in writing, that's not the problem. The problem is the medium. Your voice survives your accent. The page doesn't. So you rewrite. And the rewrite tool just moved your bottleneck to a different step.

What actually needs to happen

The real solution isn't to capture your voice. It's to reshape your voice into writing while keeping the directness of speech.

When Maria speaks on a call, her words come out in the order she thinks them. They have rhythm, directness, and confidence. That's what she wants on the page. But the page has different conventions. Longer sentences look lazy in writing. Filler words disappear when written but carry conversational tone when spoken. Her German-influenced phrasing (which sounds natural in speech) sounds slightly off when typed.

A voice tool that just records doesn't help. What helps is one that listens to what you're saying, understands it, and then reshapes it into text that reads with the same directness your voice carries.

Recitey works this way. It takes your voice, understands the intent, and polishes it into clean writing, no filler words, no false starts, no sentence fragments that work in speech but fall apart on the page. The accuracy is high enough that you're not re-editing for understanding, just for nuance. For Maria, that means a message that used to cost 25 minutes now costs 6. More importantly, the voice that emerges on the page sounds like the person on the call.

It works everywhere you type: Slack, email, your browser, code editors, any Windows app. No word limit, no metering. The system clipboard handles the integration, so there's no context switching. You speak into Slack. It polishes into a message. No transcript step, no capture step, no rework cycle.

The trade-off: you lose the rewrite as thinking

There's a cost to not rewriting. The long thinking time is gone. For some kinds of decision-making, that pause is necessary. You might want to sit with a message before sending it.

But most of the time, the pause isn't thinking. It's doubt. It's the moment when you wonder if you sound smart enough, senior enough, direct enough. The rewrite cycle isn't adding clarity. It's adding caution.

When the writing is faster, when it's closer to how you actually speak, that caution falls away. Some people will find that uncomfortable. If you wrote a message 15 times because you needed to think it through, that's real. If you wrote it 15 times because you were afraid of how you'd sound, that's the tax.

Who this is for, and who it isn't

This isn't for learning English. Grammarly is better for that; it's designed for it. This isn't for trying to sound like a native speaker either, because native speakers don't sound like one thing.

This is for people who are already fluent on calls but lose themselves in async writing. If you know you sound sharper when you speak and more careful when you type, this closes that gap. If you think the problem is your English, you're looking at the wrong tool. If you know the problem is the medium, that you're excellent when you speak and careful when you write, then the solution is to type less and speak more.

The careful version of yourself isn't who you actually are. But it's who shows up in Slack, because that's where you're constructing instead of expressing. Close that gap, and the writing gets faster. More importantly, it gets truer.

More posts
Keep reading

More like this.

  1. For non native english

    Sounded like the careful version of yourself

    You're sharp on calls. Your manager knows it. Your clients hear it. Then you move to Slack and you rewrite the message three...

  2. For non native english

    The 30-minute Slack problem nobody talks about

    You're sharp on the call; your manager noticed it. Your last review said "executive presence." Then you write the follow-up in...

  3. For non native english

    The Slack message you spent 30 minutes on still sounds careful.

    Maria's performance review this year mentioned what it always does: sharp on calls, could be more direct in writing. She'd heard...

All posts →