Chat languages and translations

Overview

The chat widget works in any language the AI model supports. It starts in the language of the website it is installed on and then follows the language the visitor writes in. There is no language selector: if your page is in French, the chat starts in French; if a visitor on that page writes in Spanish, the chat switches to Spanish.

You write your chat title, welcome message and workflow texts in English. When a conversation needs them in another language and there is no current translation, AI translates them on the fly and saves the result as approved. Interface controls and standard chat notices are translated the same way. You can review and correct any translation at any time; your own approved wording is never replaced automatically.

How the starting language is chosen

For each new conversation, the widget uses the first language it finds in this order:

The language declared by the website page's <html lang> attribute.
The first language in the visitor's browser preferences.
The configuration's Default visitor language, which is English unless you change it.

Ask your website developer to set the page's language declaration correctly. You do not need a separate widget snippet for each page language.

To change the fallback language:

Open Insights → Widget generator and select your configuration.
Expand the Translations panel in Live Preview.
Choose Default visitor language.
Click Save default language.

Review and correct translations

Tenant owners and tenant admins can review translations for their own resources. Save the resource and its English text before starting.

Open the Translations panel for the content you want to check:

Widget title and welcome message: select the configuration in Insights → Widget generator.
Workflow visitor text: select a node in Chat → Workflows. The panel lists the workflow's messages, titles, option labels and form hints.
Callable workflows of an agent: open AI → AI agents → Edit → Callable workflows. Each saved attachment has a Title translations panel for its offer title and a Workflow step translations panel for the attached workflow's messages and labels.

Then:

In Translate to:, choose one of the 24 most used languages. The panel shows that language's translations; automatic ones are marked (automatic).
Check English source.
Click Generate draft, or Generate all drafts for the listed fields. Generation uses your normal AI allowance. If the workflow has too many fields for one batch, generate individual drafts.
Review the wording, meaning, names, numbers, links and any response tags. You can also write the translation yourself in the draft box.
After editing, click Save draft. Approve stays disabled until your edits are saved.
Click Approve to use that translation with visitors. Click Reject draft to discard a draft; an existing approved translation is kept.

Languages outside the list still work for visitors; they are translated automatically when first needed.

Keep response tags, links, formatting and numbers intact. Translating labels does not change workflow routing, internal field names or the information visitors submit. Agent instructions and rules for when a workflow should be offered are not visitor text and are never translated.

Automatic translation, English fallback and changed content

Automatic translation happens the first time a conversation in a language needs the text. When you publish an agent, its callable workflows are also translated into the languages your chats already use. When you change the English source, the next conversation in that language translates it again, unless you approved your own wording for the new text first. Automatic translations use your normal AI allowance. If AI is unavailable (for example, your allowance is used up), visitors see the English text until a translation can be made. The panel shows Missing approval, Approved or Outdated approval so you can see what needs review.

If another person changes the source or draft while you are reviewing it, click Refresh and review the latest version before retrying.

Published callable workflows use the current approved translation of any text that is unchanged since publication. Learn about callable workflow publication.

Switching languages during a chat

Each message the visitor types can switch the conversation language. Very short replies (such as "ok"), numbers, email addresses, links, option buttons and contact forms do not change it, and text that could be several languages keeps the current one. AI replies always answer in the language of the visitor's latest message. Interface text, the welcome and workflow texts then follow the new language, translated on the fly where needed. Values already entered or selected are kept.

Reloading or reconnecting resumes the conversation's saved language. Changing the website page's language does not switch an active conversation; it is used when the next new conversation starts.

Earlier messages and human replies are not translated or rewritten. Your team can see Chat language in conversation details. Visitor transcript email headings and standard text follow the conversation language, while transcript messages keep their original wording. Team transcript emails remain in English.

Tips

The first visitor in a new language may wait a few seconds longer while texts are translated; later visitors get the saved translations.
Review automatic translations for languages your visitors use most, especially legal or pricing wording.