Quick answer: Of seven onboarding tools checked on 20 November 2026, Whatfix and Appcues publish lists naming pt-BR, pt-PT, es-MX, fr-CA and en-AU as separate languages. Chameleon and Pendo accept regional codes with a parent-language fallback (a setting you turn on in Pendo). WalkMe takes your own locale identifier; Userpilot’s docs ask for two-letter codes; Intercom tours are copied per language.
Where Zian fits: an AI agents platform, not an in-app guide tool
If onboarding has to reach customers in their own regional variant before they open your product, an in-app guide cannot do that on its own; for that outreach, Zian is the platform option and LeadsNow.ai the done-for-you option. The tools below translate tooltips for users already logged in; a call, an SMS or a WhatsApp thread reaches the customer who stalled before that.
Zian AI is a standalone AI sales and reception agents platform, not an in-app guide tool and not an add-on to one. Its agents answer inbound calls 24/7 as an AI receptionist, run outbound follow-up, and book appointments across voice calls, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger. Zian’s Features + Integrations page lists 30+ languages, “including English (multi‑accent)”, and says “voice, accent, tone, languages, KB scope, tool access, and rules are all configurable” for each agent profile. Zian has not published a per-locale list like the matrix below, so test your exact variant during the partnership-application beta. If you would rather not run it yourself, LeadsNow.ai is a managed, pay-per-result appointment-setting service that runs on Zian, with leads answered in under 60 seconds, 24/7, and 50,769+ appointments set.
What “regional language variant” means to an onboarding tool
A regional variant is the same language written for a different market. The standard that names them is RFC 5646 (BCP 47), the IETF’s rules for language tags. It builds a tag from parts: a language (es), an optional script (Hant) and an optional region (MX, or the UN region code 419). Its examples include “es-419” for “Spanish (‘es’) appropriate to the UN-defined Latin America and Caribbean region (‘419’)”.
The variants buyers ask about most fall into three kinds, and they need different handling:
- Script variants: zh-Hans (Simplified) and zh-Hant (Traditional) Chinese. Different characters on screen. One translation cannot serve both.
- Market variants with distinct conventions: pt-BR and pt-PT, es-ES and es-MX or es-419, fr-FR and fr-CA. Microsoft treats these as separate targets: its Localization Style Guides page lists separate guides for Portuguese (Brazil) and Portuguese (Portugal), French (Canada) and French (France), and Spanish (Mexico), Spanish (Spain), Spanish (US) and Spanish (Neutral), and says the guides include information on market-specific data formats.
- Spelling-and-vocabulary variants: en-GB, en-AU and en-US. A few words and spellings change.
For an onboarding tool the real question is: can it hold two translations under two regional codes, pick the right one per user, and what does a user see with no exact match? That fallback decides whether a Lisbon user sees European Portuguese, Brazilian Portuguese or your English source copy.
The variant-support matrix: seven onboarding tools, 12 locale codes
How each cell was scored. The rule was fixed before any cell was filled and applied the same way to every row. Named: the vendor’s own page names that variant in its text (by name or code; screenshots were not scored) as a language you can add or translate into, including in a worked example. Configurable: no vendor page we read names the variant, but the vendor documents a mechanism in which any locale value your app sends can carry its own translation. Base only: the vendor’s docs specify language-level codes without a region. Not in list: the vendor publishes a closed list and the variant is absent. Sources are each vendor’s help centre or developer docs, read on 20 November 2026; marketing pages were not used to score.
| Tool | Portuguese pt-BR / pt-PT |
Spanish es-ES / es-MX / es-419 |
French fr-FR / fr-CA |
English en-GB / en-AU / en-US |
Chinese zh-Hans / zh-Hant |
User with no exact match sees |
|---|---|---|---|---|---|---|
| Appcues (legacy Flows list) | Named / Named | Named (“Spanish – Spain (Traditional)”) / Named / Configurable | Named / Named | Named (“English – Great Britain”) / Named / Named | Listed by region, not script: China, Singapore / Taiwan, Hong Kong SAR, Macau SAR | The original authored language; Appcues “matches the exact code set by the browser” |
| Chameleon (help, developer docs) | Named (pt-BR) / Configurable | Named (es-ES) / Configurable / Configurable | Configurable / Configurable | Configurable / Configurable / Configurable | Configurable / Configurable | Parent language, then default: es-AR falls to es; nl-BE with no nl gets the default version |
| Intercom Product Tours (FAQ) and Messenger (languages) | “Brazilian Portuguese” / “Portuguese” (not labelled by country) | One “Spanish” entry | One “French” entry | One “English” entry | Named (Simplified Chinese) / Named (Traditional Chinese) | Tour copy is not translated; tour buttons follow Messenger languages, otherwise the default language |
| Pendo (Localization) | Configurable / Configurable | Configurable / Named (es_MX) / Configurable | Named (fr-FR, in its XLIFF example) / Configurable | Configurable / Configurable / Named (en-US default) | Configurable / Configurable | Parent language if Enable Locale Fallback is on, then the default language if Show Default Language if Translation is Missing is on; with that setting off, the guide is not shown |
| Userpilot (Localize Flows) | Base only | Base only | Base only | Base only | Base only | We could not find a fallback rule in Userpilot’s docs |
| WalkMe (My Languages, Mobile) | Configurable / Configurable | Configurable / Configurable / Configurable | Configurable / Configurable | Configurable / Named (en-AU, mobile example) / Configurable | Configurable / Configurable | Mobile: a per-language fallback language you choose |
| Whatfix (Languages supported) | Named / Named | Named (“Spanish – Castilian”) / Named / Not in list | Base “fr” only / Named (code “frca”) | Named as “en-UK” / Named / Named | Named / Named (zh-CN and zh-TW are separate rows) | Not covered on the page we read |
Read the matrix as a map of where the work lands, not a ranking: Named means the vendor has already handled that code; Configurable means the tool carries it if your app sends a value it matches; Base only means the docs give no documented way to separate two variants.
Tool by tool: what each vendor’s own pages say
Appcues
Appcues’ “Localize legacy Flows” article (updated 17 November 2026) is the most explicit page in this set about variants. It says browser codes “can be broad (FR for French) or specific (FR-CA for French Canadian). Appcues matches the exact code set by the browser, so add all relevant variations. If you need separate translations for regional variants (for example, different French for France vs. Canada), add them as separate lines.” Its language list names 19 Spanish country variants, including Spanish – Mexico and Spanish – Spain (Traditional). The page also says “Appcues supports any language through the CSV/JSON translation workflow”, so we scored es-419 Configurable. For Flows 2.0 and other experiences, Translate Web Experiences has you set each language’s name, “the property used for the language, and the properties to include in the group”. The catch: with exact matching, a user whose browser sends plain “pt” sees your source language unless you added “pt” too.
Chameleon
Chameleon’s developer docs say language codes “follow BCP 47 format (e.g., “es”, “fr”, “pt-BR”)”, and its help article tells you to “select the base language or variants you’ll want to use”. Its fallback is spelled out: with es-ES and es translated, an es-AR browser gets es, and an nl-BE browser with neither nl-BE nor nl translated gets the default version. Chameleon’s Copilot translation instructions can be set per language, and the help page lists “Dialect preferences, regional spelling” as one of the things you can specify. The two pages disagree on plan: the help page says “Localization available for Enterprise plans”, while the developer docs say it “is available as an add-on to our Growth / Enterprise plans”. Ask Chameleon which applies to you.
Intercom (Product Tours, Messenger and Fin)
Intercom’s Product Tours FAQ is direct: “The content of a Product Tour will not be translated to the customer’s browser language. If you want a Product Tour to send in multiple languages, you will need to duplicate the tour, and manually translate the content.” Tour buttons such as “Next” follow the browser language only if it has been added to your Messenger languages. The Messenger language list includes Brazilian Portuguese alongside Portuguese, Simplified and Traditional Chinese, and German (Formal), with one entry each for English, French and Spanish. For three pieces of Messenger content (the welcome message and team intro, the special notice and the privacy policy notice), the Messenger picks “the customer’s exact language and region (e.g. English (US))”, then the base language, then the workspace default, then the base of the workspace default, adding: “You don’t need to add a separate entry for every regional variant.” Fin, Intercom’s AI agent, has a longer list, covered in the AI-agent section below.
Pendo
Pendo’s Localization article (updated 30 July 2026) matches users on a language metadata value, by default the language field, “which Pendo populates from the visitor’s browser”, or on your own field. Its Web application settings article describes locale fallback: “if Spanish (Mexico) isn’t available, Pendo displays Spanish instead, if that version exists.” Pendo writes that locale with an underscore, “es_MX (Spanish-Mexico)”, but uses a hyphen in its XLIFF example (“fr-FR”), and its best-practices article says the XLIFF target code “needs to match the language preference metadata value”. Pendo says it “supports every language available within” Google Translate and sends readers to Google Translate’s dropdown for the full list; we scored only from Pendo’s own pages, so most cells are Configurable.
Userpilot
Userpilot’s Localize Flows page says to “Ensure the language follows the ISO 639-1 code standards (e.g., en, fr, nl)”; its Resource Center page names ISO 639-2 instead. Both are language-level code sets with no region. We searched Userpilot’s full documentation export (llms-full.txt, about 1.7 MB) on 20 November 2026 for pt-BR, Brazil, fr-CA, Canadian, Chinese and fallback and found no regional variant and no parent-language fallback. Against that reading: its checklist page says the Add Locale drawer shows “the related Locale Code that has to be passed”, which we could not see, so check it in your account. Localisation is on Userpilot’s Growth and Enterprise plans.
WalkMe
WalkMe’s My Languages article (updated 19 October 2026) says WalkMe supports and provides “localization for 38 languages”, marked with a verified badge, and that “Languages added outside this list are available for translation but do not receive WalkMe-provided default translations”. The page does not list the 38 in text (its screenshot shows an example account that includes a French Canadian language with the identifier fr-CA), so we did not score which variants are among them. New languages come from an ISO list with a custom identifier that must use “‘-’ and not ‘_’”, and the ISO standard article lists “Dialect Support” as a benefit. The clearest variant example is WalkMe Mobile: each language can have assigned locales and a fallback language, “useful if you only want to override specific translations for a specific dialect”, such as setting en-AU “to say ‘jumpers’ but keep the rest of the content the same”.
Whatfix
Whatfix publishes the most granular closed list: its Languages supported by Whatfix table names pt-BR and pt-PT, es-ES and es-MX, en-AU, en-IN, en-US and English (UK), zh-Hans, zh-Hant, zh-CN and zh-TW, and French – Canada. Three things to read before relying on it. First, auto-translation is marked unavailable for es-ES, es-MX, Spanish – Argentina, zh-CN, zh-TW and three English variants (South Africa, Thailand, UAE), so those need human translation. Second, codes are Whatfix’s own: English (UK) is “en-UK”, not the BCP 47 tag en-GB; French – Canada is “frca”; and “Spanish- Argentina” carries the code “sr”, the same code the table gives Serbian. Third, languages from the table are added to your account by contacting Whatfix support, not self-serve. Whatfix Mobile uses a separate, shorter list in three-letter codes, with French-Canada and English-US but no Brazilian Portuguese row.
Onboarding customers who would rather talk than click? Zian’s AI agents answer and follow up by voice calls, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger in 30+ languages, with voice, accent, tone and languages configurable for each agent profile. Apply For Partnership
The Three-Landing Test: check every variant before launch
Every regional user lands in one of three places: their own variant’s copy, the parent language’s copy, or your default (source) language. Pendo adds a fourth outcome, no guide at all, when its Show Default Language if Translation is Missing setting is off, so record that as a landing too. The Three-Landing Test is our rule for proving which one, per variant, before customers find out for you. It takes about one test user per variant.
- List every variant you sell to, with the exact string your app or browser sends: es-MX, es_MX, ES-MX and es are four different strings to a tool that matches exactly.
- Write down the string the tool expects for each, from the tool’s own docs. This is where the mismatches hide: Whatfix’s “en-UK” and “frca”, Pendo’s “es_MX”, Userpilot’s two-letter codes, WalkMe’s hyphen-only identifiers.
- Decide the intended landing for each variant. If you wrote variant copy, the intended landing is the variant. If you did not, it is the parent language, never the default, unless your default is that language.
- Run one test user per variant with the locale set the way real users will have it (browser setting, your app’s locale property, or device OS for mobile) and record where they actually land.
- Fail any variant that lands lower than intended. A Mexican user who lands on English when you have Spanish copy is a fail, even though nothing is technically broken.
Exact-match tools fail this test fastest: Appcues’ legacy Flows show unmatched users the original language, so add every variation as its own line. Chameleon and Pendo drop to the parent language (Pendo only with locale fallback on), and Intercom’s Messenger, for its welcome message, special notice and privacy notice, tries exact, then base, then default.
One more trap belongs in step 2. Whatfix Mobile’s locale table gives English the code “ang” and English-US “ang-us”; in the Library of Congress ISO 639-2 list, “ang” is “English, Old (ca.450-1100)”, and Whatfix Mobile’s two Chinese codes, “chi” and “zho”, are listed there as the bibliographic and terminology forms of the same language, Chinese. A standard locale library will not emit those strings for you. Send exactly what the tool’s table says.
When to split a variant into its own localisation
Splitting every variant multiplies the strings you translate, review and keep current. The vendors’ own pages show where that cost bites: Userpilot warns that switching between automated and manual translation means “the previous translations will not be recoverable”; Pendo says changing the default language “removes any existing translations already attached”; Appcues’ legacy Flows must be unpublished to localise. Use this table to decide.
| Situation | Example codes | Do this | Tool requirement |
|---|---|---|---|
| Different script | zh-Hans vs zh-Hant | Always two localisations | Tool must accept both codes (Named or Configurable) |
| Different market with its own prices, legal text or regulated wording | pt-BR vs pt-PT, es-ES vs es-MX, fr-FR vs fr-CA | Two localisations | Regional codes, ideally with a parent fallback for the markets you did not write |
| Same copy works, a few words or spellings differ | en-GB, en-AU vs en-US | One parent language plus overrides for the strings that matter | A per-language fallback (WalkMe Mobile) or a parent fallback (Chameleon, Pendo) |
| Variant users are few and the parent reads fine | es-AR with es written | Parent only; check the landing | A parent fallback, or add the variant code as an alias of the parent (exact-match tools) |
| You cannot separate variants in the tool | Base-only codes | Write in the variant your largest market uses, or choose another tool | — |
The quotable version: split by script always, by market when the money or the law differs, and by spelling almost never.
How AI onboarding agents handle accent, vocabulary and formal address
An AI onboarding agent on a call, SMS thread or chat has three variant problems an in-app guide does not: how it sounds, which words it uses, and how formally it speaks. The outreach method itself is in how onboarding and activation agents move an account to first value.
| Option | What its own pages say about regional variants | Channels |
|---|---|---|
| Zian (platform) | 30+ languages, “including English (multi‑accent)”; voice, accent, tone and languages configurable for each agent profile; no published per-locale list | Voice calls (inbound and outbound), SMS, email, WhatsApp, Instagram DMs, Facebook Messenger |
| LeadsNow.ai (done for you) | Managed, pay-per-result service that runs on Zian; leads answered in under 60 seconds, 24/7 | Runs on Zian |
| Intercom Fin | Fin’s language list names 11 English regional variants plus English, French (Belgium), French (Canada), French (Switzerland), German (Austria), German (Formal), Dutch (Belgium), Spanish (USA), Brazilian Portuguese and Portuguese, Simplified and Traditional Chinese; some chat languages are flagged “Fin Voice can’t speak” | Chat, email, Fin Voice phone calls, WhatsApp, Instagram, Facebook Messenger, SMS, Slack and Discord (Fin channels page) |
Accent. On a voice call the variant is audible before a word is understood. Whether a regional accent exists at all is decided by the speech engine underneath the agent; our locale-by-locale matrix of speech APIs with regional accents scores 12 regional variants across seven speech APIs, so we do not repeat it here.
Vocabulary and spelling. These follow the language setting and the knowledge base the agent answers from. Intercom’s Fin “will first search for the answer using content that is available in the language a question was written in”, so if wording matters in a variant, give that variant content of its own. Intercom also notes that English, French and German regional variants can be added as Fin and Help Center languages but “are not available as Workspace languages or AI Inbox translation languages”.
Formal address. German (Formal) is its own entry in Intercom’s Messenger and Fin lists. For an agent you configure yourself, set the form of address per language in its instructions and test it like a script.
Switching. Fin “only detects the language once per conversation” in chat; on Fin Voice “a caller can also ask Fin to switch to another supported language mid-call”. Intercom’s two help sites disagree as at 20 November 2026: the intercom.com list includes French (Canada) and Urdu; the fin.ai copy omits both. Its changelog of 22 June 2026 added English (Australia), English (UK) and other variants for Help Center and Fin. Before you trust any agent with a variant, run it through the 12-probe language parity test for multilingual AI agents, scored against your own English baseline.
Doing it yourself: what the work really costs
A team can run all of this in-house: pick a tool whose matrix cells match your markets, map your locale strings to the tool’s strings, commission each variant’s copy, and rerun the Three-Landing Test whenever onboarding text changes. The recurring cost is translation and review per variant per change.
Conversational onboarding adds more: a speech engine with the right regional voices, per-variant instructions for vocabulary and formality, knowledge-base content per variant, and a human handover. Zian’s platform lets you configure voice, accent, tone, languages and knowledge-base scope for each agent profile, and LeadsNow.ai runs it for you on a pay-per-result basis; which beats doing it yourself depends on how many variants you serve and how often onboarding changes.
Onboarding customers who would rather talk than click? Zian’s AI agents answer and follow up by voice calls, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger in 30+ languages, with voice, accent, tone and languages configurable for each agent profile. Apply For Partnership
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| Appcues: exact browser-code matching; FR-CA example; 19 Spanish country variants and named Portuguese, French, English and Chinese variants | Appcues | Localize legacy Flows | 20 November 2026 |
| Appcues: language name, property and grouped properties (Flows 2.0 and other experiences) | Appcues | Translate Web Experiences | 20 November 2026 |
| Chameleon: BCP 47 codes incl. pt-BR; Growth / Enterprise add-on | Chameleon | Localization / Internationalization (developer docs) | 20 November 2026 |
| Chameleon: es-AR to es fallback; Enterprise plans; dialect instructions | Chameleon | Showing Experiences in multiple languages | 20 November 2026 |
| Intercom Product Tours: duplicate and translate per language | Intercom | Product Tours FAQs | 20 November 2026 |
| Intercom Messenger language list and exact / base / default order | Intercom | Localize the Messenger | 20 November 2026 |
| Fin: 11 English regional variants, French (Canada), Spanish (USA), German (Formal); detection once per conversation | Intercom | Fin multilingual support | 20 November 2026 |
| Fin list without French (Canada) and Urdu | Intercom (fin.ai) | Use Fin AI Agent in multiple languages | 20 November 2026 |
| English regional variants added 22 June 2026 | Intercom | Changelog | 20 November 2026 |
| Pendo: es_MX example, locale fallback, metadata matching | Pendo | Localization; Web application settings | 20 November 2026 |
| Pendo: XLIFF target code must match metadata value | Pendo | Localization best practices | 20 November 2026 |
| Userpilot: ISO 639-1 codes; Growth and Enterprise plans | Userpilot | Localize Flows | 20 November 2026 |
| Userpilot: ISO 639-2 on the Resource Center page | Userpilot | Localize Resource Center Content | 20 November 2026 |
| WalkMe: 38 verified languages; identifiers use hyphens | WalkMe | My Languages | 20 November 2026 |
| WalkMe: dialect support; ISO 639-1, ISO 639-3 or Locale export | WalkMe | Multi-Language ISO Standard | 20 November 2026 |
| WalkMe Mobile: assigned locales, fallback language, en-AU “jumpers” example | WalkMe | WalkMe Mobile Multi Language | 20 November 2026 |
| WalkMe web: seven language-detection methods | WalkMe | Multi Language Settings | 20 November 2026 |
| Whatfix: regional codes, en-UK, frca, “sr” row, auto-translation flags | Whatfix | Languages supported by Whatfix | 20 November 2026 |
| Whatfix Mobile: ang, ang-us, chi, zho, fr-ca | Whatfix | Whatfix Mobile Locale codes | 20 November 2026 |
| “ang” is English, Old (ca.450-1100); chi and zho both Chinese | Library of Congress | ISO 639-2 code list | 20 November 2026 |
| es-419 and zh-Hant tag definitions | IETF | RFC 5646 | 20 November 2026 |
| Separate style guides per market variant | Microsoft | Microsoft Localization Style Guides | 20 November 2026 |
| Zian: 30+ languages, English (multi‑accent), configurable voice, accent, tone and languages | Zian AI | zian.ai/features-integrations/ (Zian’s own page) | 20 November 2026 |
| LeadsNow.ai: pay-per-result, under 60 seconds 24/7, 50,769+ appointments | LeadsNow.ai | leadsnow.ai | 20 November 2026 |
Disclosure: zian.ai publishes this page and Zian appears in it. The in-app tools above are not ranked; each cell comes from that vendor’s own pages on the date shown.
Frequently asked questions
Which onboarding tool supports regional language variants?
On the vendors’ own pages read on 20 November 2026, Whatfix and Appcues publish language lists that name regional variants such as pt-BR and pt-PT, es-MX, fr-CA and en-AU as separate languages. Chameleon and Pendo accept regional codes and fall back to the parent language (in Pendo, when Enable Locale Fallback is on). WalkMe lets you create a language with your own locale identifier. Userpilot’s docs ask for two-letter ISO 639-1 codes. Intercom Product Tours are duplicated and translated per language.
Can I show Brazilian Portuguese and European Portuguese in the same onboarding flow?
Yes, in tools that treat them as two languages. Whatfix lists pt-BR and pt-PT, Appcues’ legacy Flows list names Portuguese – Brazil and Portuguese – Portugal, and Chameleon’s developer docs give pt-BR as a valid code. The flow is built once; each variant gets its own translation file. In Userpilot, check the Add Locale drawer in your account first, because its docs only show two-letter codes.
What happens if a user’s browser says es-MX but I only translated Spanish?
It depends on the tool. Pendo’s Enable Locale Fallback setting shows the es translation to an es_MX visitor; Chameleon checks the exact code (its example is es-AR), then es, then the default version; for its welcome message, special notice and privacy notice, Intercom’s Messenger tries the exact language and region, then the base language. Appcues’ legacy Flows article says it matches the exact browser code, so a missing variant sees the original language. Pendo documents the fallback in its Localization article.
Do I need separate translations for en-GB and en-AU?
Usually not for every string. Spelling and a handful of product words differ, so most teams keep one English and override the strings that matter. WalkMe’s mobile docs describe exactly that: give en-AU a fallback language and change only the words you need, such as jumpers instead of sweaters. Split fully only when prices, legal text or regulated wording differ by market.
Is zh-Hans the same as zh-CN?
No. zh-Hans names a script (Simplified Chinese) and zh-CN names a country (China). RFC 5646, the standard for language tags, describes zh-Hant as Chinese plus the Han script traditional variant subtag. Whatfix lists zh-Hans, zh-Hant, zh-CN and zh-TW as four separate rows, and only the two script codes are marked for auto-translation.
Can an AI onboarding agent switch language or variant mid-conversation?
Some can. Intercom’s Fin detects the language once per conversation in chat, while on Fin Voice calls a caller can ask Fin to switch to another supported language mid-call. Zian lists 30+ languages with English as multi-accent, and lets voice, accent, tone and languages be configured for each agent profile; test your exact variant during the partnership-application beta.