The dashboard’s Language and ASR controls are unsaved previews. Use API drafts for configuration authoring. Voice publication is currently unavailable, even when the language and speech settings are compatible.
Language settings
Use valid language tags and the selected model’s actual coverage. Choosing
recognized_language requests responses based on recognized input; it does not establish working automatic language switching.
Prepare a language draft
1
Choose the base response language
Set the base language and write the first message in that language. Ask a fluent reviewer to check names, dates, numbers, and task-specific terms.
2
Review recognition separately
For a voice draft, select a compatible ASR model and its supported recognition mode. Follow voice configuration; a response-language tag does not configure microphone input recognition.
3
Prepare additional-language text
A language preset requires an
overrides object. It can include agent.first_message, agent.max_conversation_duration_message, turn.soft_timeout_config, and tts.voice_id within that object.Translation records use source_hash and text. Do not assume the preview translation controls have saved or translated the agent’s complete prompt.4
Save and inspect
Save the complete server draft, preserving unrelated fields. Read it back and compare the base language, response policy, preset keys, and reviewed text. Keep voice publication pending.
Frequently asked questions
Does the base language choose the ASR language?
Does the base language choose the ASR language?
No. Base response language and input recognition are separate settings. Check both against the current model catalog.
Can a language preset change the model or tools?
Can a language preset change the model or tools?
The language-preset contract has a limited override set. It does not accept a replacement LLM, tool list, or arbitrary conversation configuration.