Feature
The chat speaks your visitors’ language
Every label the widget shows — the composer, the menus, the invitations — comes in a set of languages, chosen from the visitor’s browser or fixed by you.
Automatic by default
The widget reads the visitor’s browser language and uses it if we have it, falling back to English.
Or pinned
Set a language for the site and everybody gets that one, which is what you want on a single-market site.
Your wording is separate
The text you write — the invitation, the offline message — is yours, and is not translated for you.
How it works
Reading a room that is not in your language
Translation is per reader
Somebody turns it on for themselves. The message is stored as it was written, so nobody else’s view changes and the original is never lost.
The original stays reachable
A translated message can be shown as it was sent. Machine translation gets things wrong, and a reader who can tell it has should be able to check rather than argue with a mistranslation.
It is not the same as the interface language
The buttons and labels are a separate setting, and most sites want them fixed to their own language while leaving translation to the reader.
Questions
- Is the translation any good?
- It is machine translation, which is to say: good enough to follow a conversation, not good enough to negotiate a contract in. It is shown as an aid alongside the original rather than as a replacement for it.
- Does it translate what I type?
- Your message is sent as you wrote it. Translation happens for the reader who asked for it, which keeps the record of what was actually said intact.
- Which plans include it?
- The higher tiers, alongside the other features the plans genuinely differ on.
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.