Feature
Which languages the widget speaks
The interface is translated; your own copy is not. This page is about the first part — what the buttons and menus say, and how that gets decided.
Chosen from the browser
By default the widget uses the visitor’s browser language. Nothing to configure and nothing for the visitor to pick.
Or set on the page
Set the language before the widget loads and it uses that instead — useful when your site already knows what the visitor reads.
English when we do not have it
An unsupported language falls back to English rather than showing blank labels.
How it works
How the widget decides what language to speak
You set it, or the browser does
Pass a language and the widget uses it. Say nothing and it follows the visitor’s browser, which is right for a site whose audience is not all in one country.
It can change without a reload
A site with its own language switcher can tell the widget through the JavaScript API, so the chat follows the rest of the page instead of staying behind in the previous language.
The wording is still yours
Custom wording overrides the built-in strings, so a site that calls its room something particular keeps that name in every language it offers.
Questions
- Which languages are built in?
- English, Spanish, German, French, Polish and Portuguese. A language that is not there falls back to English rather than showing an untranslated key, so a missing string is never visible to a visitor.
- Can I add a language?
- The custom wording settings let you replace the visible strings, which is how sites serve an audience in a language not in the list.
- Is this the same as translating messages?
- No. This is the interface — the buttons and labels. Translating what people write to each other is a separate feature on the higher plans.
Put a chat on your site this afternoon
One script tag before the closing body tag. Fourteen days free, and no card until you decide.