Availability: Voice Input is a Beta feature. An admin must turn it on for your org under Settings → Features → Beta. It also requires a transcription provider (OpenAI, Azure OpenAI, or your deployment’s managed proxy) to be configured on the deployment; if none is configured, the microphone control doesn’t appear even when the feature is enabled.
How It Works
1
Start Recording
Click the microphone icon in the composer. Your browser prompts for microphone access the first time.
2
Speak
Speak your question or instruction. Recording stops when you click the icon again or the maximum duration is reached.
3
Transcription
The recording is sent to the configured transcription model and converted to text.
4
Review and Send
The transcript appears in the composer as editable text. Review or edit it before sending, just like a typed message.
Limits
- Recording length: up to 5 minutes per recording.
- Upload size: up to roughly 4.8 MB per recording.
- Audio format: whatever your browser’s microphone capture produces (WebM/Opus, Ogg, MP4/M4A, MP3, WAV, or FLAC). No separate conversion step is needed.
Recording stops automatically once the duration limit is reached, and what you recorded up to that point is still sent for transcription. A recording that comes in over the upload size limit is rejected before transcription; split it into shorter clips instead.
Billing
Transcription usage is metered in ACUs, based on the audio processed and the transcript produced. See Pricing for current rates.Limitations
- Dictation only. Voice Input doesn’t let Ana speak responses back to you.
- If your browser denies microphone access, the composer guides you to re-enable it in your browser’s site settings; there’s no in-product fallback recording path.
- Turning the feature off in Settings → Features removes the microphone control for the whole org; there’s no per-user opt-out while it’s enabled.