Translating Zendesk
Zendesk translates its own interface into a long list of languages. Everything you typed yourself stays exactly as you typed it, so to translate Zendesk properly you handle both halves.
Translate Zendesk: changing the language you see
Two settings control this and people confuse them constantly.
The account default language is what Zendesk falls back to when it has nothing better. It sets the tone for notifications, the help centre and anything without a translation.
The per-user language overrides that for one person. An agent in Madrid sets their own profile to Spanish and gets a Spanish agent interface while everybody else keeps English. Same account, different chrome.
End users have the same field, and it does more work than the agent one, because it decides which language of email notification they receive. Exact menu paths for both move between releases, so check the current Zendesk docs rather than following a screenshot from a forum post.
One caveat worth knowing before anybody panics: adding a language to your account and adding it to your help centre are separate acts. You can have Spanish agents and an English-only help centre for years without noticing.
What translates, and who does it
The middle column is the one that surprises people.
| Layer | Translated by | If you do nothing |
|---|---|---|
| Agent interface labels | Zendesk | Follows each agent's profile language |
| Help centre buttons and chrome | Zendesk | Follows the visitor's locale |
| Help centre articles | You | Visitor gets the default language or nothing |
| Trigger and automation emails | You, via dynamic content | Everyone gets your default language |
| Macro bodies | You, via dynamic content | Agents paste English into Spanish tickets |
| Ticket field and form names | You, via dynamic content | A half-English form |
| Drop-down field values | You, via dynamic content | Untranslated options |
| Tags, group names, view names | Nobody | Stays as typed, forever |
Dynamic content is the mechanism
Almost every "you" in that table is the same feature doing the work. Dynamic content lets you define a piece of text once with a variant per language, then reference it by placeholder wherever the text is needed.
Zendesk serves whichever variant matches the language of the user in context, and falls back to the default when there is no variant. That fallback is why it fails gracefully instead of leaving a blank in an email.
Do it before you scale. Retrofitting dynamic content into forty existing triggers is a horrible afternoon, and it's entirely avoidable. The multilingual support guide covers the strategy; Guide localization covers the article side.
Translating the conversation itself
Different problem. A customer writes in Portuguese and your agent reads English.
Machine translation is genuinely good for understanding an inbound message well enough to route it. It's riskier for outbound, and the risk isn't accuracy, it's tone. Legal, financial, medical and anything where somebody is already angry: the words come out correct and the register comes out wrong. Customers notice.
Most teams settle in the same place. Translate to understand and route, reply in a language somebody on the team actually speaks, and keep a short list of languages you claim to support rather than pretending to cover everything.
A translation project that finishes
The feature isn't the hard part. Sequencing is, and here's an order that has worked more than once.
Then the part nobody budgets for. Each language you add is a permanent commitment, not a one-off translation cost, because every article edit becomes an edit in five places. Teams that support four languages well beat teams supporting nine badly, and customers only notice the second kind.
What never translates
Tags. Group names. View and trigger names. Internal notes. Ticket subjects. Attachment filenames. Anything an agent typed into a free-text field.
That isn't a bug. It just means your internal vocabulary is permanently in one language, so pick that language deliberately on day one and write it down. Teams that let tags drift across three languages end up with facturacion, billing and rechnung all meaning the same thing, and every report built on them is wrong.
Frequently asked questions
Where are the Zendesk language settings?
In the Admin Center, under localisation. The Zendesk language settings control which languages the account offers, which one is the default, and what an agent sees in their own profile.
How do I change the Zendesk interface language?
Set the language on the user profile. It overrides the account default for that person only, and it changes both the interface labels and the notifications they receive.
Does Zendesk translate help centre articles automatically?
No. Guide stores a translation per language under one article, and somebody has to supply each translation. Machine translation through an app or a vendor is common, and it should be reviewed.
Can Zendesk translate tickets automatically?
Through apps and AI features, yes, mainly for understanding inbound messages. Sending the machine translation back untouched is the part to be careful with.
Why is my customer getting English notifications?
Either their user language is unset or wrong, or the trigger uses hard-coded text rather than dynamic content. Check the user record first, since it is the faster of the two to fix.
How many languages does Zendesk support?
A long list for its own interface, and a shorter list for some products and features. Availability varies by plan and by product, so check the current Zendesk docs for your account.
The multilingual duplicate
A customer writes in their own language, hears nothing fast enough, then rewrites it in English. Two tickets, one problem, and requester matching catches it.
Start free trial14-day free trial. No credit card required.