Auto-Detect Language
Read the visitor's browser language automatically — no questions asked. The routing happens silently before the first message appears.
Language Router for
Multilingual Chat Support
The Language Router detects each visitor's browser language — or lets them choose from a menu — and routes the conversation to a language-specific workflow, agent team, or AI model. Serve global audiences in their native language without building separate chat widgets for every locale.
- No credit card
- 14-day free trial
- UK hosted
- Visual builder
What Is the Language Router Module?
The Language Router module reads the visitor's browser language setting — the Accept-Language header that every browser sends — and uses it to branch the workflow by locale. English-speaking visitors go down one path, French speakers down another, German speakers down a third, and so on. You can also configure a manual override that presents a language-selection menu, letting visitors choose for themselves.
For businesses that operate across borders, language is the single biggest barrier to a good support experience. A French customer forced to chat in English is already frustrated before the conversation starts. The Language Router removes that friction entirely. It ensures every visitor is greeted, supported, and resolved in a language they're comfortable with — whether that's through a native-speaking agent, a localised AI model, or translated workflow content.
The module supports any number of language branches. You can route the top five languages to dedicated teams and funnel everything else into a default branch with AI-powered translation. Or you can start with two languages and expand over time. Each branch is a full workflow path, so you can customise not just the language but the entire experience — different greeting text, different data-collection fields, different handoff destinations. A Spanish visitor might see a "Nombre y correo electrónico" collection form while an English visitor sees "Name and email." Every detail can be tailored.
Manual Selection
Present a language menu so visitors can choose explicitly. Useful when browser settings don't match the visitor's actual preference.
Team-Based Routing
Route each language to a specific agent team. French to Paris, German to Berlin, English to London — keeping conversations native.
AI Model Per Language
Send each language to a tuned AI model with localised training data, tone, and vocabulary for natural-sounding automated support.
How the Language Router Fits Into a Workflow
The Language Router is best placed as the very first decision node — even before a greeting message. Why? Because the greeting itself should be in the correct language. If you send "Hello! How can we help?" before detecting that the visitor speaks French, you've already created a mismatch. By routing first, every message the visitor sees is in their language from the start.
Each language branch then contains its own complete sub-workflow: localised greetings, data-collection forms with translated labels, department routing specific to that region, and handoff to agents who speak the language. This architecture keeps the workflow tree clean and each branch independently maintainable. When you add a new language, you simply create a new branch — existing ones are untouched.
Example: European E-Commerce — Three-Language Support
An online retailer serving the UK, France, and Spain uses the Language Router to provide native-language experiences.
START
Language Router
EN / FR / ES
English
Human Chat
UK team
French
AI Chat
FR support
Spanish
Step-by-Step Breakdown
- Language Detection: The router reads the browser's language header. English, French, and Spanish are mapped to dedicated branches; all others fall to a default (English).
- English Branch: UK-based visitors are greeted in English and connected to the London support team via live chat.
- French Branch: French visitors are routed to an AI model trained on French product documentation and FAQs, providing instant answers in their native tongue.
- Spanish Branch: Spanish visitors receive a localised greeting and enter a workflow with translated collection forms before being routed to the Madrid team.
Best Practices & Tips
Multilingual chat is a powerful differentiator but requires thoughtful implementation. These tips will help you get it right from the start.
Always Have a Default
Not every browser sends a language you support. Define a default branch (usually English) that catches all unmatched locales so no visitor is left without a path.
Localise Everything
Don't just translate the greeting — localise every message, button label, form field, and error text in the branch. Half-translated experiences feel worse than fully English ones.
Offer a Language Switch
Some visitors have browser settings that don't match their preference. Include a "Switch language" button at the start of each branch so they can change without restarting.
Review Analytics by Language
Monitor which language branches see the most traffic. If 30% of your visitors are French but only 5% use French chat, your detection or content may need attention.
Frequently Asked Questions
How does the Language Router detect the visitor's language?
The module reads the Accept-Language header sent by the visitor's browser. This header reflects the language preferences configured in their browser or operating system settings. The router matches the primary language code (e.g., fr, es, de) against your configured branches.
Can visitors choose their language manually?
Yes. You can configure the Language Router to present a selection menu instead of (or in addition to) auto-detection. This is useful for visitors whose browser language doesn't match their preference, or for sites where visitors frequently switch between languages.
How many languages can I route to?
There's no practical limit. You can create as many language branches as you need. Most businesses start with two or three and expand as demand grows. Each branch is an independent workflow path with its own nodes, messages, and handoff targets.
What happens if a visitor's language isn't in my configured list?
Unmatched languages are sent to your default branch. We recommend setting English (or your primary business language) as the default so every visitor gets a complete, functional experience regardless of their browser settings.
Related Modules
The Language Router works alongside these modules to deliver tailored, multilingual chat experiences.
Support Every Visitor in Their Language
Set up multilingual chat routing in minutes. Detect languages automatically, route to the right teams, and deliver native experiences — no separate widgets needed.