Multilingual customer support comes down to one distinction most guides skip: translating a ticket isn't the same as resolving it. A translation layer, whether it's your helpdesk's built-in feature or DeepL, removes the language barrier, but a person still has to research and write every answer. An AI agent that reads your English docs and replies natively in the customer's language removes the work itself, and that's the part that actually scales.
The setup I'd recommend for most teams is a hybrid: let AI answer the routine questions in the customer's language, and give your people a translated summary and draft for everything that needs judgment. Start with one or two languages as drafts, compare each language against your English baseline, then expand. Keep one English knowledge base as the source of truth instead of translating every article.
That's the model eesel's AI helpdesk teammate runs inside the helpdesk you already have. Innr, a Dutch smart lighting brand on Freshdesk, gets 180 draft replies a month in Dutch, German, English or French, written from about 1,500 help center articles and past tickets in one Freshdesk account, with the language matched to each customer.
Why doesn't translating a ticket resolve it?
I look at search data for a living, and "multilingual customer support" is one of those keywords where the words hide the real question. Nobody searching it wants a definition. They're a support lead watching a queue fill up with Portuguese, Polish and Japanese tickets that nobody on the team can read, and they want to know what to do on Monday.
Across eesel's own rollouts, language is rarely the edge case people expect. One German jewelry brand running about 1,000 tickets a month on Zendesk and Shopify had its agent handle German, English, French, Dutch, Spanish, Polish, Croatian and Turkish without anyone setting that up. The tickets were already there. The team just couldn't answer them quickly.
The usual first move is to turn on translation. That helps, and it's the right tool for some tickets. But look at what still happens to a Spanish refund question after it's translated: an agent reads it in English, digs through your policy, writes an answer, then translates it back. You've saved the reading. You haven't saved the work.
Customers can feel the difference too. They notice when a reply is a stitched-together translation rather than an answer written for them:
"Translations are always bad. AI translations are bad AND dishonest. If I google something and see a result in my native language, I expect there to be someone who speaks it among the site's staff."
That's harsh, but it's a useful bar. A reply in someone's language reads as a promise that you can actually help them in it. Whichever model you pick below, the goal is a reply that resolves the issue in their language, not a reply that merely is in their language.
What are the four ways to handle multilingual customer support?
There are four real options, and most teams end up combining two of them. Here's how they compare before we go through each one.
| Model | What it does | What you pay for | Best when | The catch |
|---|---|---|---|---|
| Native speakers or outsourcing | People who speak the language answer the tickets | Salaries, or a provider's monthly fee | One big market, high-stakes conversations | Expensive per language, hard to cover a long tail |
| Translation layer | Translates tickets and replies for your existing agents | Helpdesk plan or add-on, or a translation tool | Low volume across many languages | Every ticket still needs a person |
| AI agent answering natively | Reads your docs and replies in the customer's language | AI usage (per ticket, credit or resolution) | Steady volume of repeat questions | Needs good source docs and a handoff path |
| Hybrid | AI answers routine tickets; people get translations and drafts for the rest | A mix of the above | Most growing teams | Needs clear rules for what goes where |
Pick the row closest to your situation and the widget below will show where I'd start.
1. Hire native speakers or outsource
The oldest answer is still the best one for your biggest market. A native speaker catches the things tools miss: the formal "Sie" a German customer expects, a joke that doesn't land in French, a policy that needs a local exception. If one language is a large slice of your queue, a person for that language is money well spent.
The problem is the long tail. You can't hire a Croatian speaker for eight tickets a week, and a follow-the-sun team in three time zones doesn't automatically cover twelve languages. Outsourcing helps with coverage but moves the cost rather than removing it, as my breakdown of customer service outsourcing cost shows. If you're weighing a full handover, eesel also runs Managed Support for ecommerce brands, but for most teams reading this, the next three options are where the savings are.
2. A translation layer for your human agents
This is the option most helpdesks now ship out of the box. Inbound messages get translated into your agent's language, and the agent's reply gets translated back before sending. It's fast to switch on and keeps a person in charge of every word.
It's the right choice when foreign-language tickets are occasional, or when every reply needs human judgment anyway. It's the wrong choice as your only answer to growing volume, because translation doesn't shorten the research and writing. I go through what each helpdesk includes further down.
3. An AI agent that answers in the customer's language
An AI agent reads the question, finds the answer in your knowledge base and past tickets, and writes the reply directly in the customer's language. Modern language models don't need your docs translated first: they read English and write Polish. That's the difference that matters. The agent isn't translating your answer, it's writing one. I compare the tools that do this in best AI for multilingual support.
This is where volume stops being a hiring problem. The catch is that the agent is only as good as what it reads, and it needs a clean path to hand off. eesel has watched confident-sounding bots give wrong answers for years, and a wrong answer in fluent French is worse than a slow right one. That's why I'd always run an agent on historical tickets first, and keep it on drafts until you've checked each language.
4. Hybrid: AI for the routine, people for the rest
The hybrid model combines the last two. The AI answers routine questions natively, and anything that needs judgment goes to a person with the translation, a short summary and a suggested reply already attached. Your agents never start from a blank page in a language they don't speak.
This is what I'd recommend for most growing teams, and it's the shape the multilingual eesel setups below take: the AI drafts or answers in the customer's language, and people keep the judgment calls. The rest of this guide is about making the hybrid work: what your tools already do, which tickets go where, how to handle the knowledge base, and how to measure it.
What does your helpdesk already translate?
Before you buy anything, check what your current plan includes. Every major helpdesk now translates tickets in some form, and the differences are in plans, limits and channels. All details below come from each vendor's own docs and pricing pages as of October 2026.
Zendesk: conversation translation and AI agents in 80+ languages
Zendesk's conversation translation translates inbound and outbound messages across every channel except voice. It's listed on Support Team, Professional and Enterprise, and on every Suite plan. Admins can switch from the default AWS engine to "AI translations", which Zendesk says gives higher quality, and add an optional "Translated by AI" label.
A few limits are worth knowing. Incoming chat and messaging translations aren't saved and rerun on each reload, translated messages can't be redacted, and an outbound email whose translation fails is sent in the original language after five minutes, per the same article. On the AI side, Zendesk's pricing page says AI agents "automatically translate AI agent responses into 80+ supported languages." Support Team starts at $19 per agent per month on annual billing, Suite Team at $55 and Suite Professional at $115. My Zendesk pricing breakdown and the guide to Zendesk translation options go deeper.
Gorgias: per-agent translation and an AI Agent that replies in any language
Gorgias ticket translation is available on all helpdesk plans. Each agent sets a default translation language and a list of "languages you know" in their own profile, so a bilingual agent only sees translations for the languages they don't read. Internal notes aren't translated, and outbound replies get translated from a toolbar icon before sending.
On the automation side, Gorgias's AI Agent "supports over 80 languages and replies in any of them, even when your knowledge isn't translated." That's the native-answer model inside Gorgias itself, and it pairs with a multilingual help center if you publish one. My Gorgias AI Agent pricing post covers what that costs.
Freshdesk: Live Translate, metered by Copilot seats
Freshdesk Live Translate detects the language of a ticket and translates it when an agent clicks Translate. It's on Pro and Enterprise, not Free or Growth, and it rides on the Freddy AI Copilot add-on, which Freshdesk lists at $29 per agent per month.
The meter is the part to read twice: the monthly limit is 100 translated tickets per Copilot license. A reopened ticket, a second agent translating the same ticket, or a ticket translated again after a month of inactivity each count again. With five Copilot seats, that's 500 translated tickets a month across the team. More in my Freddy AI Copilot review.
HubSpot, Front and the rest
HubSpot's help desk page mentions AI language detection and "automated translation tools," and HubSpot documents skills-based ticket routing so tickets in a language land with agents who speak it. Its knowledge base articles can be translated with AI on Service Hub Professional and Enterprise. Front has its own AI Translate for email and chat-like channels.
| Helpdesk | Ticket translation | Plan | AI that answers in the customer's language |
|---|---|---|---|
| Zendesk | Inbound and outbound, all channels except voice | Support Team+ and all Suites | AI agents, 80+ languages |
| Gorgias | Inbound and outbound, set per agent | All helpdesk plans | AI Agent, 80+ languages |
| Freshdesk | Click-to-translate, 100 tickets per Copilot seat a month | Pro and Enterprise + Copilot | Freddy AI Agent (separate) |
| HubSpot | Language detection, skills routing | Service Hub | Breeze customer agent (separate) |
| Front | Inbound and outbound translate | Starter, Professional, Enterprise | Separate AI products |
The pattern is the same everywhere: translation is cheap or included, and native AI answers are a separate, metered product. That's also why many teams add an AI layer on top of the helpdesk they already have, a trade-off I cover in my post on adding an AI layer.
Where does DeepL fit?
DeepL is the translation engine a lot of support teams reach for when the built-in option sounds stiff, and its quality on European languages is excellent. It's a strong pick for human-controlled replies, especially with a glossary that locks your product names and terms.
What changed for helpdesk users: as of October 1st, 2025, DeepL for Zendesk is no longer available, according to DeepL's support center. DeepL's browser extension now works inside Zendesk instead, and it needs a DeepL Pro Advanced or Ultimate plan. Free and Pro Starter users get 50 messages to test it.
If you want DeepL wired into your own workflow, the DeepL API has a free Developer tier with a one-time credit of 1 million characters and one glossary. Growth is $26 per month billed annually, with 12 million characters a year, 2,000 glossaries and extra characters at $27.50 per million.
The glossary is the feature people pay for. One Canadian user translating reports into French put it plainly:
"The sole reason I paid for the service is that it came with a single glossary with unlimited entries."
So where does it land? DeepL translates, it doesn't resolve. It makes a human agent's reply read better in German, but it doesn't know your return policy or look up an order. Use it on the human side of a hybrid setup. My DeepL pricing and DeepL alternatives posts compare the plans and the other engines.
How does a multilingual support workflow actually run?
Here's the hybrid model as a ticket actually moves through it. Five steps, and most of them happen before anyone on your team opens the ticket.
- Detect the language. Your helpdesk or AI tags the language on arrival. smava, a German loan comparison platform, has eesel tag the language, check eligibility and set a category on 14,600 Zendesk tickets a month before anything else happens.
- Triage and route. Routine questions go to the AI. Tickets that need a decision go to a person, ideally one who speaks the language if you have one.
- Answer routine tickets natively. The AI writes the reply in the customer's language from your English sources. Early on, it leaves these as drafts. On chat the reply has to be instant, which I cover in multilingual live chat.
- Hand the rest to a person, prepared. The agent gets the translated ticket, a short English summary and a suggested reply in the customer's language. They edit and send. A clean handoff is what makes this feel smooth to the customer.
- Review quality per language. Sample replies in each language every week, not just in English. More on that in multilingual support QA.
The language rules live in plain instructions, not settings screens. In eesel, a line like "match the customer's language; German replies use formal Sie" is enough, and the eesel docs state it plainly: it answers in the customer's language without you translating your help center.
What should you automate and what should stay human?
The split isn't about language at all. It's about risk. A tracking question is just as safe to automate in Polish as in English, and a refund dispute is just as risky in both. Sort tickets by what's at stake, then let language follow.
| Ticket type | Who handles it | Why |
|---|---|---|
| Order status and tracking | AI, sends directly | One lookup, one clear answer |
| Shipping, returns and policy questions | AI, sends directly | Answer is in your docs |
| Setup and how-to questions | AI, drafts first | Docs cover most of it, edge cases exist |
| Refund exceptions and goodwill | Person, with AI draft | Needs a judgment call |
| Disputes, chargebacks and fraud | Person | Money and evidence at stake |
| Legal, compliance or privacy requests | Person | Wrong wording has consequences |
| Angry or high-value customers | Person, with AI summary | Tone matters more than speed |
One thing translation-only setups miss: the "person" column still benefits from AI. Even when a human decides, the AI can write the first draft in the customer's language and the English summary for the agent. That's the time saver translation alone can't give you. For a deeper look at when AI should step back, see AI escalation.
Do you need to translate your knowledge base?
Usually not every article, and this is where teams waste the most money. There are two ways to run a multilingual knowledge base, and they suit different readers.
One source of truth. You keep a single English knowledge base, and the AI reads it and answers in any language. Nothing goes out of sync, because there's only one version to update. Koffer.ch, a Swiss luggage shop on Freshdesk, runs this way: eesel uses a matching Freshdesk macro first, translated into the customer's language if needed, and drafts in German, French, English or Italian. German drafts even use Swiss spelling, "ss" rather than "ß".
Translated articles. You publish each article in each language for customers who self-serve. This is worth doing for your top articles in your top languages, because customers do read help centers. But be careful with machine-translated articles left unreviewed. Zendesk's AI article translations don't update when the source changes, so every edit to the English article leaves the copies stale. And readers notice:
"Machine translated KB articles are destroying the japanese translations made by humans (and probably other languages too)"
My take: translate your 10 to 20 most-viewed articles into your top two languages, and let AI cover everything else from the English source. Zendesk only localizes the help center in 40+ languages from Suite Professional (Suite Team gets one default language), so check your plan before you plan a big translation project. My guides to multilingual knowledge base software and the Zendesk multi-language help center cover the publishing side.
Whichever way you go, keep a short terminology list. Product names that must never be translated, the formal or informal "you" for each language, and words with a house meaning. My support translation glossary guide walks through building one.
How do you roll out multilingual support in 30 days?
You don't need a quarter-long project. Four weeks is enough to go from "we can't read these tickets" to a working hybrid in your first two languages.
Week 1: count tickets by language. Pull 60 to 90 days of tickets and tag each by language. You're looking for two numbers: which languages make up most of the non-English volume, and which topics repeat inside them.
Week 2: fix the English source. The AI answers from what you've written, so gaps in English become gaps in every language. Fill the missing articles for your top repeat topics and write the terminology list. An AI knowledge base audit is a quick way to find the holes.
Week 3: pilot one or two languages as drafts. Turn the AI on for your top languages only, with replies saved as drafts or internal notes. Have someone who reads the language, even a colleague outside support, check a sample. Innr ran this way on Freshdesk: German replies use the formal "Sie" in every sentence, and a customer who writes in English gets English, whatever their country.
Week 4: compare each language to English. Look at draft acceptance, edits and customer replies per language next to your English baseline. Where a language matches English, let the AI send its safest categories. Where it lags, fix the docs or the instructions before expanding. Then add the next language. My AI support pilot guide has a fuller plan.
Which metrics should you track per language?
Track the same metrics you already use, but split by language. A blended number hides the problem: a 70% resolution rate overall can mean 85% in English and 40% in Japanese.
| Metric | What it tells you | Red flag |
|---|---|---|
| Language detection accuracy | Tickets tagged with the right language | Mixed-language or short tickets tagged wrong |
| Draft acceptance rate | Share of AI drafts sent with little or no editing | Much lower than English for one language |
| AI resolution rate | Tickets closed without a person | A language far below your English baseline |
| Reopen rate | Answers that didn't actually solve it | Customers replying "that's not what I asked" |
| CSAT by language | How customers felt about the reply | A language trailing English by 10+ points |
| Critical errors | Wrong policy, wrong order, wrong promise | Any, in any language |
| First response time | How long non-English customers wait | Non-English tickets waiting longer than English |
That last one is the quiet win. Before a hybrid setup, non-English tickets usually wait the longest because they sit until the one person who reads the language is free. If the gap between English and other languages closes, you've fixed the thing your customers felt most. My customer service KPIs guide covers the full set, and for scoring grammar and tone in each language, see support language quality.
Try eesel for multilingual customer support
eesel's AI helpdesk teammate joins the helpdesk you already run, including Zendesk, Freshdesk, Gorgias and HubSpot. It learns from your English help center, macros and past tickets, then answers in the customer's language without you translating anything first. You set language rules in plain words, like formal "Sie" for German or never translating your product names, and it holds them in every reply.
You don't have to trust it on day one. Start with drafts as internal notes in one or two languages, read what it writes, and let it send the safe categories once each language looks as good as English. SE Ranking runs it on Zendesk this way across three products, with eesel answering 2,100 live chats a month in the customer's language and drafting email tickets for the team.
Plans start at $299 a month for 500 credits, where a ticket or a chat is one credit however long, and there's a free trial with 100 credits and no card, per eesel's pricing page. Connect your helpdesk, point it at last month's foreign-language tickets, and see the drafts before you pay anything. Try eesel.