Skip to main content
At the end of this page, your agent talks to end users in every language you enable, with nothing left untranslated.

​
Before you start

Before you start, sign in to the dashboard and select the organization you want to work in.
  • Open your agent and select Configure in the builder sidebar, then select Language in the Settings list on the Configure page.

​
Add your languages

1

Set the primary language

Under Primary Language, pick the language your flow is written in. It is the default language and the fallback for any untranslated content.
Language selected in the Settings list on the Configure page, with the Primary Language picker, the Multi-Language switch, and the System Messages groups below
2

Turn on Multi-Language

Turn on the Multi-Language switch. Select Add language and search by name, native name, or language code. Each added language appears as a chip with a remove button.
3

Save

Select Save Languages. A confirmation states that the language settings are saved.

​
Translate the flow content

Each added language gets its own content set. In the builder, open a gambit and a strip of language flags appears above its content. Select a flag to edit that language. Messages, buttons, and cards are edited independently per language. An added language starts empty. While its flag is selected, a Translate from button, named for your primary language, sits above the content. Select it to fill the fields with an automatic translation of the primary content, then review the result and edit where needed. Anything you leave untranslated falls back to the primary language.

​
Override the system messages

Flow content is not the only text end users see. The System Messages section, below the language settings on the same tab, overrides the built-in texts per language. The fields sit in five groups:
  • Input Placeholders
  • Validation Errors
  • UI Labels
  • Status Messages
  • Conversation History
Each field shows the default translation as its placeholder. Leave a field empty to keep the default. With more than one language enabled, tabs above the groups switch which language you are editing, and a badge counts the overrides in each group. Select Save Messages to apply. The launcher callout text is translated per language on the Design page instead. See Design the widget.

​
What end users experience

The widget resolves the conversation language from the embed configuration, the page URL, and the browser, in that order. The exact rules live in Script and config. To let the end user switch language mid-conversation, add the Language gambit from the Flow Control group. Right-to-left text direction is detected per message, so mixed-language conversations render correctly.

​
Verify

Select Validate in the builder toolbar. Missing translations appear as warnings that name the gambit and the affected languages. Warnings do not block publishing, but the publish button labels the release as with warnings. See Drafts and publishing.