GoHighLevel Languages: What Actually Translates (2026)

Search "GoHighLevel languages" and every result answers the same question: how do you switch the platform's display language. That is a real setting, and it works. It is also not the question most agencies actually have once they are running a sub-account for a client whose contacts, or whose own team, are not English-first.

The real question is narrower and more useful: when a lead, a client, or a team member is set to a language other than English, what in GoHighLevel actually follows them, and what quietly stays in English no matter what they pick. The two behave differently, and nothing currently ranking for this query says so.

Which parts of GoHighLevel actually follow a user's language?

Two things, and they follow different people.

The interface follows the logged-in user. Under Settings > My Profile, each person who logs into a sub-account picks their own Platform Language. An agency can also set an account-wide default under Sub-Account Settings > Business Profile > Platform Language, which new users inherit until they override it. HighLevel's own settings list Spanish, German, French (Canada and France), Portuguese (Portugal and Brazil), Italian, Dutch, Swedish, Danish, Finnish and Norwegian alongside English (help.gohighlevel.com, Business Profile Settings, retrieved 2 August 2026). Change it, and menus, buttons and system messages switch immediately. This is the setting every other page on this topic describes, and it is genuinely per-user: two people logged into the same sub-account can each see the platform in a different language.

The Client Portal and its child apps go further, supporting 12 language and locale options between web and mobile, with an admin able to set a portal-wide default that individual portal users can still override from their own account (help.gohighlevel.com, "Internationalization For Client-Portal & Child Apps," modified 20 January 2026).

Conversation AI follows the contact, automatically, per message. This is the one place GoHighLevel translates without anyone configuring anything. Conversation AI detects the language a contact writes in, Spanish, French, Portuguese, German and others, and replies in that language with no manual setup, as covered in our Conversation AI guide. It is the single feature in the platform that adapts to the other person in the conversation rather than to whoever is logged in.

What does not follow a contact's language?

Almost everything an agency sends automatically.

Default system emails are English only. Welcome emails, password reset emails, verification emails and the client portal invitation go out in English regardless of the recipient's Platform Language or the sub-account's locale. This is not an edge case; it is the platform's stated default behavior, and it is the exact complaint behind a HighLevel ideas board request, detailed below.

Voice AI language is chosen by the agency, not detected from the caller. Voice AI supports a long list of languages, over 50 in HighLevel's own documentation, but the language is set per agent under AI Agents > Voice AI > Language, a deliberate configuration choice made once when the agent is built (help.gohighlevel.com, "Multi-Language Support for Voice AI Agents in HighLevel," modified 22 June 2026). A caller who speaks a different language than the one the agent was configured for gets the configured language, not their own. That is a real capability, but it is the opposite pattern from Conversation AI: you pick the language in advance, the caller does not.

"Outbound Communication Language" is not a translation setting. Business Profile's Address & Locale section lists Platform Language and a separate Outbound Communication Language field, and it is easy to assume the second one controls the language your automated messages send in. HighLevel's own documentation describes it as governing "formatting dates and numbers" only (help.gohighlevel.com, Business Profile Settings, retrieved 2 August 2026), not message translation. It is a formatting setting wearing a name that sounds like a bigger feature.

Workflows and automations do not translate their content by default. A workflow you build sends whatever text you typed into the Send Email or Send SMS action, in whichever language you typed it, to every contact it fires for, regardless of that contact's language field. GoHighLevel does not read a contact's language and swap the message automatically.

Has HighLevel acknowledged the gap?

Yes, in both directions, on its own ideas board, under Language - Internationalization.

"DEFAULT EMAILS ONLY IN ENGLISH" sits at 48 votes with status In Progress. A HighLevel team member, Aayushi Somani, replied on 27 February 2026: "We are working on translating all system and default emails sent from Highlevel" (ideas.gohighlevel.com, retrieved 2 August 2026). That is the specific problem this guide is about, confirmed by the vendor, with a status attached rather than silence.

"[Internationalisation]", the broader request covering translation quality and coverage across the platform, sits at 202 votes with status Upcoming, open since April 2022 (ideas.gohighlevel.com, retrieved 2 August 2026). No official reply is posted on that thread as of this writing.

Read together, the two threads say what the settings pages do not: the interface-level translation work is largely done, and the automated-communication layer, the emails and messages an agency doesn't hand-write per contact, is the part HighLevel has publicly flagged as unfinished.

What's the workaround for default system emails right now?

A partial one. HighLevel lets you customize three of the default templates: Welcome, Password Reset and Verification, including the logo and CTA button colors (help.gohighlevel.com, "How to Edit Agency System Email Templates in HighLevel," modified 7 April 2026). You can hand-edit the English text in any of those three into another language.

The limits are real. That edit is account-wide, not per-recipient, so a sub-account serving both English and Spanish contacts cannot have the same Welcome email arrive in each contact's own language this way; the whole template is in one language for everyone. And it only covers three templates. The client portal invitation email specifically has no accessible template to edit at all, a gap a commenter on the ideas board thread raised directly. If a sub-account is genuinely single-language, this workaround is a real fix. If it serves contacts across languages from one sub-account, it is not.

How do you make workflow-triggered messages follow a contact's language?

This is where a real, contact-level fix exists today, and it takes building, not a toggle.

1. Store the contact's language. Add a custom field, "Preferred Language" or similar, captured on your intake form or set manually for existing contacts.
2. Open the workflow. Any workflow that sends an email or SMS is a candidate.
3. Add an AI Translate action before the send step. This action takes text and a source and target language, and outputs a translated version as a variable you can drop into the message that follows (help.gohighlevel.com, "Workflow Action - AI Translate," modified 6 January 2026).
4. Set the target language to the contact's custom field, not a fixed language, so the same workflow produces a different translation per contact.
5. Use the translated variable in the Send Email or Send SMS action, replacing the hardcoded English text.
6. Test it with a contact record set to a non-English language before switching the workflow live.

This covers workflow-triggered messages, appointment reminders, follow-ups, nurture sequences, anything you build. It does not touch the three fixed default system emails above; those are a separate, more limited case. HighLevel's documentation for the AI Translate action does not mention a plan restriction, but confirm current availability on your own account before building around it, since AI-powered actions on this platform have moved between plan tiers before.

Who will this not be good enough for?

Be honest about where this leaves an agency, because the workaround above is real work, not a switch.

An agency running one sub-account per client, each client single-language, has the least to solve. Set that sub-account's Platform Language, hand-edit the three system email templates into the client's language, and the gap barely shows.

An agency running one sub-account that serves contacts across several languages, a bilingual local business, a multi-country brand, has the most exposure. The Welcome, Password Reset and Verification emails will go out in whichever single language you set, to everyone, until HighLevel ships the fix its own team has said is in progress. The AI Translate workaround covers workflow messages, which is most of what an agency actually automates, but it has to be built into every workflow individually; it is not a setting you flip once.

And an agency waiting for full parity, every automated touchpoint in a contact's own language without any building, is waiting on the "[Internationalisation]" request, which is marked Upcoming with no shipped date. "In Progress" and "Upcoming" are different distances away, and it is worth treating them that way when you decide how much of this to build around versus wait for.

For the workflow mechanics behind the AI Translate action, see our GoHighLevel automation workflows guide. For how the same default-English pattern shows up in campaign sending, see our GoHighLevel email marketing guide. If Voice AI's per-agent language setup is the piece you need to configure, that sits inside the CRM's broader contact and pipeline setup.