Configuring Languages
Use language settings to make an Agent available to audiences in the languages they expect.
Purpose
Choose which languages an Agent supports, set the language it falls back to, decide whether a conversation keeps its first language, and optionally extend its reach with real time translation.
Prerequisites
- A configured Agent. See Quickstart.
- A list of the audience languages you intend to support.
- Permission to edit Agent settings for your team.
Steps
Open the Agent's Language Settings
Select Agents in the left-hand navigation, open your Agent, then choose the General page and the Language tab.

Choose the Supported Languages
In Supported Languages, select each language the Agent should offer. Search only lists languages the Agent’s model supports, each one by its English name.
Leave the field blank to offer every language that model supports. Select languages only when you want a shorter list. Real time translation can add languages the model does not support. When the visitor list has one language, replies use Default Language and messages are not detected, unless a channel lists a different language.
Set the Default Language
First-time visitors on the Agent’s site start in Auto. Each message is detected on its own, and the reply uses that language when it is one you support.
Default Language is the fallback when detection finds no language, and when a supported list is set and the detection is not on it. A supported language can list detector codes. A message read as one of those codes uses that language when the detected language itself is not supported. The site also uses the default for the chrome when the browser language is not supported. If neither the Agent nor a channel has supported languages, the detected language is kept.
This list uses the same English names. It includes the languages you selected under Supported Languages, or every language the model supports when that field is blank. If you narrow the supported languages later, confirm the default is still among them.
Disable Language Detection (Optional)
Turn on Disable Language Detection Mode when replies should stay in Default Language until someone picks another language in the selector. The selector then has no Auto option, and a first visit with no saved language opens in the default language.
Leave it off to keep Auto. Each message is detected, and the reply uses that language when you support it.
Persist Conversation Language
Persist Conversation Language is off by default. A language chosen in the selector is sent with the message and is the reply language. That message is not detected.
In Auto, the message is detected. While Persist Conversation Language is off, the selector stays on Auto, so the next message is detected again. The page language, its direction, and the Bible list still follow each reply. Turn it on and a detection the Agent offers selects that language in the switcher, so later messages there name it until someone chooses Auto again. A messaging channel, and any other request that does not name a language, detects each message on its own while this is off.
Turn it on to keep the first language for later messages that do not name one. That includes a visitor who returns the selector to Auto, and each later message on a channel. A language chosen in the selector is still sent as-is.
Extend Reach With Real Time Translation (Optional)
Expand Advanced Language Settings to find two more controls:
- Use Real Time Translation for Specified Languages translates incoming prompts into English and translates the Agent’s responses back into the language the user wrote in. This widens language coverage well beyond the built-in list.
- Real Time Translation Languages limits that behavior to specific languages. Search lists every language a translation provider offers, not only Supported Languages. Each language is listed once per translation provider, as
Spanish · Google Cloud Translate API (100 credits), and you can select more than one provider for the same language. The field stays disabled until the toggle above is on. Leaving it blank applies real time translation to every non-English language the base model does not support. With languages selected, Auto uses a supported language or one of those selected languages. Any other detected language uses Default Language and is not translated. A language selected both here and under Supported Languages uses real time translation instead of the model’s own support for that language.
The visitor language selector lists Supported Languages, or the model’s languages when that field is blank. With real time translation on, a blank Real Time Translation Languages field adds every translation provider language, and a selected list adds only those languages. Each language appears once, in ISO 639-3 order.
The language selector in the Console header includes both Supported Languages and Real Time Translation Languages. Each language appears once, by its English name.
English never uses real time translation, whether or not it is selected.
Real time translation consumes the number of additional credits shown on the selected language for every response it handles. Leaving the language list blank applies it to every non-English language the base model does not support, using the default provider’s credit amount. Select the specific languages you need.
If you do not see Advanced Language Settings, real time translation is not included in your team’s current plan.
Expected Result
The Agent offers the languages you selected. A first visit opens in Auto, or in the default language when Disable Language Detection Mode is on or only one language is supported. The first Auto message is detected. That language is the reply when the Agent lists it, and the default language is the reply when it does not. While Persist Conversation Language is off, the selector stays on Auto. Turn it on and a detection the Agent offers is selected in the switcher, so later replies stay in it until someone chooses Auto again. A detection the Agent does not offer leaves the selector on Auto. While a message still does not name a language, it is detected on its own when Persist Conversation Language is off, and it stays in the first language when that setting is on. A language chosen in the selector is the reply language either way. Real time translation can cover additional languages.
How the Language and Bible Translation Are Chosen
Every message is answered in one language, and scripture in that answer comes from one translation. While the selector stays on Auto, the page language, its direction, and the Bible list follow the latest reply. Those two results are the effective language and the effective Bible translation.
The Page Language
A language prefix on the path is saved and opened as a language in the address. The introduction and the other translated page text follow this page language. The first message is still detected while the selector says Auto.
The Reply Language
A named language is one the visitor picked in the selector, or one an API request sent. On the site, Persist Conversation Language decides whether a detection the Agent offers also moves the selector off Auto. While it is off, Auto stays selected and the next message is detected again. While it is on, later messages name that language until someone chooses Auto again.
A channel has no selector. With Persist Conversation Language off, each of its messages is detected. With it on, the first language is kept for later messages that do not name one. The first language is stored on the conversation either way. A channel list is checked only while a message is being detected, ahead of the Agent list. A detection on that list or the Agent list is kept. A detection on neither uses the Agent default. Leave both lists empty and the detected language is kept. The Agent default is also used when detection finds no language.
How the Reply Language and Translation Are Used
The reply language and the Bible translation chosen for it are what the answer is built from.
The model is instructed to answer in the reply language. When real time translation handles that language, the model answers in English and the finished answer is translated back. Language Handling Instructions receive the language the model is answering in through the {language} tag, so the tag is English on a translated turn and the reply language on every other turn.
Scripture is fetched from the chosen translation, and Scripture Handling Instructions receive its name through the {bible} tag. The verses are in the reply language. When that language has an explicit scripture fallback, the verses stay in the fallback language. When no edition exists, the model writes the verses in the reply language.
Sources are retrieved in the reply language. When that language is not the site default, sources in the default language are included as well. The reply language is stored on the conversation, and Persist Conversation Language decides whether a later message that does not name a language reuses it.
About the Page Language Switcher
The language dropdown in the top right of the Agent pages is a different control. It does not change what the Agent supports. It selects which language’s content you are currently editing. Its options are the Agent’s supported languages and real time translation languages, with each language shown once by its English name.
Several settings store a separate value per language, including the Bible translation defaults covered in the next guide. When you edit those, check the page language switcher first so your change lands on the language you intended.
Troubleshooting
- A language is missing from Supported Languages. The model does not support it. Real time translation can still offer it.
- A language is missing from the Default Language list. Add it to Supported Languages first, or leave that field blank when the model already supports it, then reopen the Default Language field.
- Later messages stay in the first language. On the site, that means Persist Conversation Language is on: a successful Auto detection selects that language in the switcher. Choose Auto again when the next message should be detected. While that setting is off, the selector stays on Auto and each message is detected. On a channel, or any request that does not name a language, the same reuse means Persist Conversation Language is on. A language chosen in the selector is used either way.
- Advanced Language Settings is not shown. Real time translation is a plan feature. Confirm your subscription tier.
- The Real Time Translation Languages field is greyed out. Turn on Use Real Time Translation for Specified Languages first.
- The live Agent still shows other languages. Confirm you saved the change, then reload the Agent’s site.
Next Step
Continue to Configuring Bible Translations.
