Voice and calls
Fix calls that won't start or can't hear you, bots that don't speak, missing voices, dictation that doesn't work and voice notes that never arrive.
Voice in Murage has four parts, and each can fail on its own: hearing you (the microphone and transcription), thinking fast enough to talk (the voice host), speaking (the voice), and doing real work (the bot's engine). Work out which part is missing first.
A call won't start
A call needs three things. Check each one:
- A voice host. Flux Router, or your own xAI, Anthropic, OpenAI, Groq or OpenRouter key. A Claude or ChatGPT subscription doesn't count.
- A voice for the bot: set it in Bot settings → Voice & alerts.
- A way to hear you. On a Mac, Apple's on-device recognition. On Windows and Ubuntu, Flux Router, or your own Groq or OpenAI key.
If Flux Router is your route, check you have credits. Murage shows Flux Router needs credits when you've run out.
Calling a channel needs a voice for every member.
The call can't hear me
- Mac: allow Microphone and Speech Recognition for Murage in System Settings → Privacy & Security.
- Windows: allow microphone access for Murage in Settings → Privacy & security → Microphone.
- Ubuntu: check the right input device is selected in the system sound settings.
- Check the microphone works in another app, and that no other app is holding it.
On Windows and Ubuntu, Murage hears you about 1.5 to 3 seconds after you stop speaking, and there are no live words on screen. That delay is normal.
The bot talks but can't do the work
The voice host answers quickly and hands real work to the bot's engine. If the engine can't run, you'll hear the bot explain that. Test the bot in an ordinary chat first. See Troubleshooting engines.
Approvals during a call
Approve out loud. "Yes for the rest of the call" covers ordinary requests only. If a request isn't picked up by voice, answer its card in the app.
The bot doesn't speak its replies
- Check a voice is chosen in Bot settings → Voice & alerts.
- Turn on Read replies aloud if you want every reply spoken.
- Check your system volume and output device.
- If you use your own voice key, check it's saved and still valid.
A voice is missing from the list
- The Flux voices need Flux Router.
- Some xAI voices only show when the xAI route is available, through Flux Router or your own xAI key.
- Built-in Mac voices and Built-in Windows voices only appear on those systems. Ubuntu has no built-in system voice in Murage.
- ElevenLabs voices need your ElevenLabs API key.
Dictation doesn't work
- Mac: dictation uses Apple's on-device recognition. Allow Microphone and Speech Recognition.
- Windows and Ubuntu: hold to talk; the transcription comes back from Flux Router. Check you have credits.
- Transcribing an attached audio file uses Flux Router too, and has a file size limit. Try a shorter clip.
Voice notes never arrive
- Voice notes need a voice for the bot and an engine that can use Murage's tools.
- A bot sends at most three voice notes in a turn, each up to about 90 seconds.
- In Telegram, Slack or Discord, voice notes come from your Chief of Staff only, and only when you're talking to it there.
Voice messages in Telegram, Slack or Discord
If your Chief doesn't answer a voice message with one, check its voice (above), and see Troubleshooting channels.
Still stuck
Note your system, the bot's voice engine and voice host, and the exact message you saw, then see Collecting a bug report.
See also: Voice.