Voice Isn't Available

The microphone control is missing or disabled: what each specific cause means and how to fix it.

Voice fails in one of a few specific, distinguishable ways. The interface names which one applies rather than just showing a disabled button, so check the exact message before assuming the whole feature is broken.

No transport configured

If nobody has connected a LiveKit project yet on this install, voice is unavailable for every organization, not just yours. This is an install-wide setting under Settings → Voice. Ask whoever administers your install to complete it. See Voice Setup.

Transport disabled

A LiveKit connection exists but has been switched off. This is different from never configured: the credentials are retained, just not in effect. Re-enable it from the same settings page rather than re-entering the connection details.

Transport unverified

The connection has either never been tested, or the last test failed. Run Test connection in Settings → Voice before relying on it.

No transcription provider

Transport can be fine while your organization simply has no active speech-to-text vendor connected. This is the most common per-organization cause, distinct from the install-wide transport settings above: an admin needs to connect Deepgram or ElevenLabs for the transcription role, even if a different admin already set up LiveKit for the whole install.

The microphone works but the agent never replies out loud

Expected if only transcription is configured and no text-to-speech provider is active. Voice input-only is a supported mode, not a bug. Connect a text-to-speech provider if you want spoken replies too.

Voice Setup: connecting transport and a speech provider
Voice: what each of these pieces does