Freshdesk Language Support, Vietnamese Included
Freshdesk Vietnamese language support, like every other language, is really three separate settings people assume are one. Confusing them is why half a portal ends up in English.
Freshdesk language support is three settings, not one
Before you configure anything, separate these. They are set in different places and they do different jobs.
A team supporting Vietnamese customers usually needs the second and third, and often not the first. Your agents may well prefer working in English even while every customer touchpoint is in Vietnamese. That's a perfectly normal configuration and it surprises people.
Freshdesk language support in the agent interface
Each agent picks their own display language in their profile settings, from the list Freshdesk supports for the agent interface.
Two honest caveats. The agent interface list is generally shorter than the portal list, so a language you can offer customers is not automatically a language your agents can work in. And translation coverage of newer features tends to lag, so parts of a translated interface occasionally show English strings.
Check the list in your own account rather than trusting any published summary, including this one. Freshworks adds languages and the lists move.
The thing that never translates is your own configuration. Group names, ticket status labels you created, custom field names, canned response titles. Those are strings you typed, and they appear exactly as typed to every agent regardless of their interface language. Worth thinking about before you name a status in one language and hire in another.
Freshdesk language support on the customer side
This is the part that matters commercially, and the order of operations matters.
First, pick your primary language. This is the fallback, and everything falls back to it when a translation is missing. Choose it deliberately, because changing it later is disruptive.
Then add your supported languages, Vietnamese in our example, in the admin area. Once a language is enabled, three things become translatable: the portal interface strings, your solution articles, and the customer-facing email notification templates.
That last one gets forgotten constantly. A customer submits a ticket in Vietnamese through a Vietnamese portal, then receives an English acknowledgement email, because the notification templates were never translated. Go through each customer-facing template and translate it. It's tedious and it takes an afternoon.
Language is normally selected either by the customer on the portal or from the language attribute on their contact record. Set that attribute properly on import, because a customer whose record says English will get English notifications no matter what the portal shows them. If you run multiple portals, each one carries its own language configuration.
Freshdesk language support for solution articles
Your knowledge base is where multilingual support either works or quietly falls apart.
Freshdesk handles this by keeping translations attached to the same article rather than as separate articles. One article, several language versions, one set of analytics. That structure is the right one, because it means a Vietnamese reader landing on an English URL can be shown the Vietnamese version rather than a dead end.
The practical approach: translate your top articles by traffic, not your whole library. Twenty articles cover most of the volume in almost every help centre, and twenty is maintainable. Two hundred isn't, and stale translations do more damage than missing ones.
Freshdesk Vietnamese language support, and its limits
Set expectations here, because this is where multilingual projects disappoint.
It doesn't translate incoming tickets. A ticket written in Vietnamese arrives in Vietnamese and an agent who doesn't read Vietnamese cannot handle it. Some AI capabilities offer assistance with this, availability varies, and none of it removes the need for a routing plan.
It doesn't translate agent replies. If you promise support in a language, you need somebody who writes it.
So the real design question isn't which languages the software supports, it's how tickets in each language reach someone who can answer them. Route on the contact language attribute, or on the portal the ticket came from, into a group staffed accordingly. Set separate business hours if that group works a different timezone, because a Vietnamese-language queue staffed from Ho Chi Minh City has different SLAs from a London one whether you configure that or not.
Start with one additional language and do it completely. Portal, notifications, top twenty articles, a staffed queue. A single language done properly beats five done halfway, and the half-done ones generate more tickets than they deflect.
Frequently asked questions
How does Freshdesk portal translation work?
Per article and per portal string. Freshdesk multilingual support publishes a version of each solution article per language, and Freshdesk portal translation covers the interface text around them.
Does Freshdesk have Vietnamese language support?
Freshdesk supports a broad list of customer-facing portal languages and a somewhat shorter list for the agent interface. Check both lists in your own admin settings, since Freshworks adds languages over time.
How do I change the language in Freshdesk?
Agents set their own interface language in their profile. Customer-facing languages are enabled by an admin at the account level, with one primary language acting as the fallback.
Are solution articles translated automatically?
No. Translations are versions of the same article that you write or import, and they don't update when the source article changes. Keeping them current is a manual job.
What happens if an article has no translation?
The reader sees the primary language version rather than an error. That fallback is helpful and it's also how a portal can look complete while most of it is untranslated.
Can Freshdesk translate incoming customer messages?
Not as a core behaviour. Some AI capabilities offer assistance and availability varies by plan. Plan on routing each language to agents who read it rather than on machine translation.
Duplicates in any language
Ticket Merger matches on requester, ticket fields and subject keywords within a time window, so it merges duplicates regardless of the language they arrive in.
Start free trial14-day free trial. No credit card required.