Plan requirement
| Subscription | Any plan |
| Access | Admin |
It follows the visitor's browser language on its own, and one line overrides that. Your own text is a separate job, and so are the people answering.
What language does the widget speak?
The one the visitor set in their web browser. A Dutch browser gets Dutch labels with nothing configured, because the widget's own interface text is translated by Zendesk.
Telling it instead of letting it guess
Where your site already knows, because the visitor chose a language or is on a language-specific page, set it:
zE("messenger:set", "locale", "nl")
That overrides the browser match, and it belongs immediately after the widget snippet on the page. The codes it accepts are the Zendesk locale codes, listed at support.zendesk.com/api/v2/locales/public.json. Worth doing wherever your site has a language switcher: a visitor who chose Dutch on an English browser expects Dutch throughout.
What does that not cover?
Two things, and they are the ones customers read.
Your own text
Zendesk translates the labels. It does not translate what you wrote: greetings, out-of-office messages and trigger text stay in the language you typed them. Dynamic content gives you a version per language, and that is what makes a widget genuinely multilingual rather than half translated.
The people answering
A widget in Dutch invites Dutch conversations, which somebody has to answer in Dutch. Skills-based routing is how those reach the right person rather than the first free one.
Comments
0 comments
Article is closed for comments.