1. Decide which Slack artifact you want
Use the message composer when teammates should receive editable text in a channel, thread, or DM. Use Slackbot voice dictation when the destination is a prompt for Slackbot. Use a clip when the recording itself, with an optional generated transcript, is the message.
Those paths are not interchangeable. A transcript attached to a clip does not become an ordinary draft in the composer, and Slackbot dictation does not document a workspace-wide voice keyboard for every channel field.
- Editable message: dictate into the active composer.
- Slackbot request: use Slackbot’s own microphone where available.
- Recorded update: create an audio or video clip.
2. Dictate ordinary Slack messages with the Mac text path
Turn on Dictation under System Settings → Keyboard, confirm the displayed shortcut and language, then click the Slack message field before starting. Speak the draft, stop Dictation, and review the text before pressing Enter or choosing Send.
Apple describes Dictation as text input for places where you can type. Slack’s composer is still an app-owned field, so test a short unsent draft before depending on it. If the field does not receive text reliably, retry in a plain DM, test TextEdit, or keep the clipboard as the fallback.
3. Use Slackbot’s microphone only for Slackbot prompts
Slack’s current Slackbot guide documents a microphone icon that dictates a prompt on desktop and mobile. Slack says the dictated audio is transcribed, the audio data is not stored, and the feature is optimized for English while supporting Slack’s languages and others.
Slackbot availability is plan- and administrator-dependent. Slack currently lists it for the new Business+ and Enterprise+ plans, plus certain legacy plans with the Slack AI add-on. That is useful for asking Slackbot a question, but it is not the same workflow as drafting a message to a person or channel.
4. Treat Slack clips as saved media
In a channel or DM, Slack’s microphone icon records an audio clip up to five minutes. After recording, you can send the clip and choose Generate transcript so recipients can read it.
Slack states that clips follow the workspace retention policy for other files. Choose this route when vocal delivery matters or a recording is easier than text. Choose dictation into the composer when the result should be searchable, editable message text without an attached recording.
5. Troubleshoot the microphone path that actually failed
If macOS Dictation fails in Slack, test it in TextEdit. A failure in both places points to the Mac shortcut, language, input source, or Dictation configuration. If TextEdit works, the problem is likely the Slack field, browser, extension, or insertion path.
If a Slack-owned clip or Slackbot microphone fails, check Slack or the browser under System Settings → Privacy & Security → Microphone. Slack’s clip documentation also recommends checking the selected input device under Slack → Preferences → Audio & video. These app permissions are separate from whether a system-level dictation tool can place finished text through Accessibility.
6. Review workplace text before it enters the channel
Before sending, verify channel or DM destination, mentions, names, dates, amounts, links, code tokens, and negations. A fluent transcript can still send the wrong commitment to the wrong audience.
Never dictate passwords, API keys, customer secrets, or other restricted data merely because one speech stage is local. The final text still enters Slack and follows the workspace’s access, export, retention, and compliance rules.
7. Use IraVoice for the distinct local, cross-app requirement
IraVoice 0.7.1 is the separate option for macOS 26+ Apple-silicon Macs when speech recognition should run on the Mac or the same held-key habit should cover supported editable fields across Slack, email, notes, and developer tools. Models still download on first use, and Gumroad verifies paid activation.
IraVoice does not integrate with Slack APIs, send messages, or bypass a workspace’s controls. It targets the focused editable field exposed through macOS Accessibility and falls back to the clipboard when insertion is uncertain. You remain responsible for reviewing and sending the message.