iPhone Dictation Not Working in Slack? 9 Fixes That Work

Short answer: Slack has no dictation of its own on iPhone. The mic key on the iOS keyboard does the transcribing, so most failures are keyboard-level: dictation disabled, a stuck language download, Screen Time limits, or a company device policy. Test in Notes first, then work through the fixes in order.

You open Slack on your iPhone, tap into a channel, hit the mic to dictate a reply, and nothing happens. Or the mic key is greyed out. Or dictation starts and then quits after two words. Meanwhile the same mic works perfectly in Messages, which makes the whole thing feel random.

It is not random. Slack is one of the most common apps people dictate into on a phone, because Slack messages are exactly the kind of text voice is good at: short, conversational, and frequent. But Slack is also an app where three different microphones live within a centimeter of each other on screen, and where a work account can carry policies that silently change how the keyboard behaves. Both facts generate a steady stream of "dictation is broken" reports that have nothing to do with dictation being broken.

This guide sorts it out in a specific order: first identify which microphone you are actually tapping, then run a 60-second test that tells you whether the problem lives in iOS or in Slack, then apply nine fixes ranked by how often each one is the real cause.

First: Slack shows you three microphones. Only one of them dictates.

A surprising share of "dictation not working in Slack" cases are not failures at all. They are the wrong microphone. On the Slack message screen you can encounter three separate mic-shaped things:

• The keyboard mic. The small mic key on the iOS keyboard itself, below the letters. This is Apple's dictation. Tap it, speak, and text appears in the message field. This is the one this article is about.
• Slack's audio clip button. The waveform or mic icon inside Slack's own composer toolbar. This records an audio message and sends it as a playable clip. It does not type text into the field. If you tapped this and got a recording instead of words, nothing is broken; you used a different feature.
• The huddle mic. The microphone inside a Slack huddle, which is for live audio conversation and has nothing to do with text.

So before any troubleshooting: tap into the message field so the keyboard comes up, and look for the mic key on the keyboard itself, not in Slack's toolbar. If the keyboard mic is there and works, you are done. If it is missing, greyed out, or fails when tapped, continue.

The 60-second test that isolates the problem

Dictation on iPhone is a system feature that apps receive, not a feature each app implements. That architecture is good news for troubleshooting, because it means one comparison tells you where the fault lives:

1. Open Apple Notes, tap into a note, tap the keyboard mic, and say a sentence.
2. Open Slack, tap into any message field, tap the keyboard mic, and say the same sentence.

Three outcomes, three diagnoses:

• Fails in both. The problem is iOS-level, not Slack. Skip straight to fixes 2 through 6, and see our general iPhone dictation troubleshooting guide for the full system-level checklist.
• Works in Notes, fails in Slack. The problem is specific to Slack: focus, the app itself, or a policy attached to your workspace. Go to fixes 1, 7, 8, and 9.
• Works in both, but badly. Wrong words, cutouts, or early stops point at microphone routing or connectivity rather than settings. Fixes 5 and 6.

Sixty seconds, and you have eliminated roughly half the fixes on every list on the internet.

The 9 fixes, in order

1. Confirm you are tapping the keyboard mic, not Slack's waveform

Covered above, but it earns the top slot because it is the most common cause and the fastest to rule out. The keyboard mic types text; Slack's composer mic records a clip. If your "dictation" keeps producing audio attachments, this is the whole answer.

2. Toggle Enable Dictation off and back on

Go to Settings, then General, then Keyboard, and find Enable Dictation. If it is off, that explains a missing mic key entirely; someone or something turned it off, and turning it back on fixes it. If it is already on, toggle it off, wait a few seconds, and turn it back on anyway. This forces iOS to re-register the dictation service and re-check its language resources, which clears a class of stale states that otherwise survive an app restart.

If the Enable Dictation toggle is missing or greyed out, that is not a bug. It means a restriction is in place, which is exactly what the next fix and fix 9 are about.

3. Check Screen Time restrictions

Screen Time can block dictation without any visible sign inside Slack. Go to Settings, then Screen Time, then Content & Privacy Restrictions. If restrictions are on, check the allowed-apps list for Siri & Dictation. A family device, a device set up from an old backup, or a Screen Time profile you configured years ago and forgot can all carry this block. Allow Siri & Dictation, then retest in Notes first, then Slack.

4. Unstick the dictation language download

Dictation for your language depends on downloaded speech resources. If those resources never finished downloading, dictation can appear enabled but do nothing, or start and produce nothing. This state commonly follows an iOS update, a language change, or a long stretch on cellular-only data.

The fix is to give the download the conditions it needs: connect to Wi-Fi, plug the phone in, turn Low Power Mode off, and leave the phone alone for a while. You can also nudge it by toggling Enable Dictation (fix 2) while on Wi-Fi. If you recently added a keyboard language, check Settings, then General, then Keyboard, then Keyboards, and confirm the language you dictate in is actually listed.

5. Turn off Low Power Mode while you test

Low Power Mode does not disable dictation, but it pauses background downloads (which starves fix 4) and forces aggressive auto-lock, which can end a hands-free dictation session mid-sentence. If the yellow battery icon is showing, charge past 80 percent or toggle Low Power Mode off in Settings, then Battery, and retest. If dictation suddenly behaves, you have your answer, and we cover the full mechanics in iPhone dictation and Low Power Mode.

6. Fix Bluetooth microphone routing

If dictation produces wrong words, fragments, or silence, the phone may be listening through a Bluetooth device that is not near your mouth: AirPods in a bag, a car that grabbed the audio route, a speaker across the room. Open Control Center, check the audio output, and either move the earbuds in, disconnect the device, or turn Bluetooth off entirely for one test. A microphone that hears a muffled room transcribes a muffled room.

7. Watch where the cursor actually is

Dictation types wherever the text cursor sits, and Slack has more text fields than it appears to: the channel composer, a thread reply box, an edit-message field, the search bar, a canvas. Two Slack-specific traps come up repeatedly:

• Thread vs. channel. You opened a thread, but the keyboard is attached to a different field than you think, so dictation seems to go nowhere. Tap directly inside the field you want until the cursor visibly blinks there, then dictate.
• Focus loss on refresh. If Slack refreshes, reconnects, or pops a notification banner while you are dictating, the field can lose focus and dictation stops early. Redraft in a stable moment, or dictate the message first and paste it.

8. Update Slack, then reinstall it if needed

If Notes dictates fine and Slack does not, and focus is not the issue, update Slack from the App Store. Keyboard-handling bugs in an app build are rare but real, and an update is cheap. Reinstalling is the heavier version of the same fix, with one warning: if you use Slack with a work account on a company-managed phone, check with IT before deleting the app. On managed devices, reinstalling can require re-enrollment steps that turn a five-minute fix into an afternoon.

9. Ask IT about managed-device and managed-app policies

This is the fix nobody puts on generic lists, and for Slack it matters more than for almost any other app, because Slack is so often a work app on a managed device. Companies that manage iPhones through mobile device management can disable dictation on the device entirely. Companies that manage just the app through app protection policies can restrict what keyboards and input methods work inside managed apps like Slack, while everything behaves normally in your personal apps.

The signature of this case is precise: dictation works everywhere except Slack (or except all your work apps), your personal apps are unaffected, and no setting you can reach explains it. There is no user-side workaround, and that is by design. The honest advice is to ask your IT team whether dictation or third-party input is restricted for managed apps, and to make the case that voice input is an accessibility and productivity feature, not a data risk, especially with tools that keep transcription out of the clipboard-sharing paths policies worry about.

If everything checks out and dictation is still flaky

Suppose you have been through all nine and dictation in Slack now technically works, but it still feels fragile: it times out while you think, mangles product names and coworker names, and forces you to fix punctuation afterward. That is not a broken setting. That is the built-in dictation experience, and Slack's rapid-fire, name-dense messages expose its weak spots more than most apps do.

This is the point where a purpose-built voice keyboard is the structural fix rather than another settings toggle. Voice Keyboard Pro is a third-party iPhone keyboard with a built-in mic button, so dictation arrives with the keyboard itself and works in any iOS app, Slack included. You tap the mic, speak naturally, and the transcription engine handles punctuation and pacing without the short-timeout behavior. Because it is the keyboard, there is no separate app to switch to and no copy-paste step.

Two of its features map directly onto Slack use. Voice Edit lets you fix a message by speaking the change, so "change 3 pm to 4 pm" edits the draft instead of forcing you to retype it. And two-way translation while dictating covers 24 languages, which turns a multilingual team channel from a friction point into a non-event. There is a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year if voice becomes your default way of writing messages.

If you dictate into Slack on your Mac as well, the desktop side has its own failure modes and its own fixes; we cover those separately in Mac dictation not working in Slack. And once dictation is reliable, dictating better Slack messages covers the habits that make voice-written messages read well: keeping them short, front-loading the ask, and knowing when a thread deserves typing instead.

Why this keeps happening with Slack specifically

It is worth understanding why Slack generates so many of these reports, because the pattern predicts where to look next time.

First, Slack sits at the intersection of personal device and corporate policy. The same app binary behaves differently depending on whether your workspace is managed, and iOS gives you no banner saying "your keyboard options were restricted by policy." Silence looks like breakage.

Second, Slack's composer is unusually busy. Audio clips, huddles, canvases, emoji, shortcuts: lots of adjacent tap targets that do microphone-ish things. Feature confusion masquerades as failure.

Third, Slack messages are exactly the length where dictation friction shows. A two-sentence reply is fast to speak and annoying to type, so people dictate in Slack more than in most apps, and higher usage surfaces more edge cases: Bluetooth routing in the car, Low Power Mode at the end of the day, focus loss during a reconnect on hotel Wi-Fi.

None of that means voice input and Slack are a bad match. The opposite: short conversational text is the best possible match for speaking at 130 to 150 words per minute instead of thumb-typing. It just means the failure points are mostly around dictation rather than inside it, which is why the ordered checklist above resolves the overwhelming majority of cases.

Frequently asked questions

Why is there no mic key on my keyboard in Slack?

Either Enable Dictation is off (Settings, General, Keyboard), a Screen Time restriction blocks Siri & Dictation, or a device management policy has disabled dictation. If the mic key is also missing in Notes, it is one of those three. If it is missing only in Slack, suspect a managed-app policy and ask IT.

Why does Slack send an audio recording instead of typing my words?

You tapped Slack's audio clip button in the composer toolbar rather than the mic key on the keyboard. The clip button records and sends audio; the keyboard mic transcribes into text. They sit close together and are easy to confuse.

Why does dictation stop after a few seconds in Slack?

Built-in dictation ends a session when it detects a long pause, when the text field loses focus, or when the app interrupts it. Slack reconnecting or a notification banner can steal focus mid-sentence. A hold-to-speak voice keyboard avoids the timeout by recording exactly as long as you hold the button.

Does dictation in Slack need an internet connection?

For many languages, iPhone dictation can run on the device once its language resources are downloaded, though features and accuracy can differ from the connected experience. Voice Keyboard Pro's transcription uses a connection to deliver full accuracy. Slack itself needs a connection to send the message either way, so in practice you are rarely dictating into Slack truly offline.

Can my company really block dictation just in Slack?

Yes. App protection policies can restrict input methods inside managed apps while leaving the rest of the phone alone. If dictation works in your personal apps and fails only in work apps, that is the likely cause, and only your IT team can change it.