Resonant + Slack
The average knowledge worker sends 50+ Slack messages a day. At 40 words per minute, that's an hour of typing. At 200 wpm with Resonant, it's 12 minutes.
Press a hotkey in any Slack thread. Speak your reply. Clean, well-structured text lands in the message box. All processed on your Mac.
The problem
In theory, detailed Slack messages prevent confusion. In practice, you abbreviate — because typing a thorough response to every thread takes forever. So you write “looks good” instead of the nuanced version. You write “let's discuss” instead of the actual context.
The result: more meetings to compensate for the context that didn't make it into the thread. More follow-up DMs. More “what did you mean by that?”
Voice removes the penalty for being thorough. You can say the full context in the time it takes to type the abbreviation.
Same conversation. Different input.
Thread reply after a standup
“looked into the auth issue, think it's the token expiry logic”
“I looked into the auth issue — the root cause is the token expiry check running before the version check, so tokens issued before the schema migration get rejected even though they're still valid. I'm going to swap the order and add logging to see how often this hits in prod. Should be a clean fix, will have a PR up by EOD.”
Channel update after a customer call
“call went well, they want a few changes to the proposal”
“Call with Acme went well. They're aligned on the overall approach but want three changes: (1) extend the pilot from 30 to 60 days, (2) include SSO in the pilot scope, and (3) move the pricing discussion to after the pilot results. I think all three are reasonable. Will send an updated proposal by Thursday.”
DM to your manager
“hey can we chat about the roadmap”
“Hey — I want to flag something about the Q3 roadmap before the planning meeting. The migration work is going to take longer than the two sprints we allocated, mainly because the legacy data has inconsistencies we didn't account for. I think we need to either cut the search feature from Q3 or add a contractor to the migration. Happy to talk through the tradeoffs whenever you have 10 minutes.”
Workflow
Navigate to the message, channel, or DM you want to reply to. Put your cursor in the message box.
Resonant activates in place. No window switch. No app to open. You're still looking at Slack.
Say everything — the context, the reasoning, the action items. Voice removes the penalty for being thorough.
Filler words removed. Sentences structured. The message appears in the Slack compose box, ready to send.
Tone
Resonant adapts to the context. Slack messages get a natural, conversational tone — not the stiff formal style you'd send to a client. The output sounds like you wrote it, just faster.
No “I hope this message finds you well.” No unnecessary formality. Just clear, direct communication — the kind that actually works in Slack.
Privacy
Resonant processes audio locally on your Mac. Your voice — including the filler words, the false starts, the version before the cleanup — never leaves your device.
The only thing transmitted is the final message, through Slack's normal channels. Exactly as if you'd typed it.
Free. Local. Works in any Slack field.
One hotkey. Every thread, channel, and DM. Clean text in seconds.
Requires macOS 14+ · Apple Silicon