Multilingual conversations
Configure assistant languages and maintain translated scenarios and forms without duplicating their logic.
Choose your assistant languages
Set the default language and the languages your assistant should offer in its language settings. Complete the welcome message, input placeholder and other visible copy for each language. The dashboard itself is available in Czech and English; customer-facing content can use the configured assistant languages.
How a language is selected
The chat selects its language automatically: a supported page language takes priority, followed by a supported browser language. Otherwise, the assistant’s configured default is used. Scenarios use a published variant in that language when available, or their published source language as a fallback. Forms likewise use their own published default when the requested translation is unavailable. Authored text is not translated automatically during a conversation.
Translate content, keep one path
A scenario has one source language and one shared graph. Select another language to translate its public title, messages and answer labels. Each editable translation shows the original above it for reference. Form translations are managed separately in Forms. Translated buttons retain their identifiers and follow the same branches. For action steps, translate the result message and selected response-field labels; action IDs, input mappings, response paths and the three outcome branches stay shared.
Prepare a translation with AI
Choose “Translate this step with AI” for a selected step or “Translate missing texts with AI” for the whole scenario, including its public title. Review and edit the suggested texts, then choose “Apply draft”. Existing translations are kept by default. For a single step, you can explicitly choose to replace the existing translations shown in the proposal; newer manual edits are always preserved. A changed original makes the proposal outdated. Applied suggestions remain an unreviewed draft: mark the complete translation as reviewed using the prominent button beside the language status in the editor header, then publish separately. AI receives only authored source texts and language information, never customer conversations or submitted form answers. Linked forms are not translated by this action.
Review changes before publishing
When source content changes, existing translations need review. Confirm a translation only after checking it against the source. Publishing includes the complete source variant and only current translations with matching published variants of every linked form. Other languages use the complete fallback variant. Saving a draft does not change the version already running in customers’ chats.
Keep the guide’s language consistent
A running guide keeps its selected language as the customer moves between steps or resumes after reloading. A fallback language used by a scenario does not change the language of the rest of the chat. Visitors do not need to select a language manually. Submitted answers stay in the form response and are not copied into AI context.
Check every supported language
Test the guide in each language. Follow every choice, test both branches of conditions and check the titles, required-field messages and confirmation text in linked forms. Also test an unsupported browser language, a missing translation, a free-text interruption and resuming after a reload.