Languages & locale
A single pipeline can speak many languages. You write your message once as the default, then add versions for any languages you support — and each recipient receives the version that matches their own language. This page explains how that works and how to keep it reliable.
Default content and language versions
Every pipeline has default content: the message most people will receive — a subject and body for email, a body for SMS, or a body and SMS fallback for Viber. On top of that, you can add a separate version of your message for any supported language.
The languages you can add versions for are:
- Bulgarian
- Catalan
- Greek
- Greek (formal)
- English
- English (US)
- Spanish
- French
- Dutch
- Romanian
For each language you fill in only the fields your channel needs — email needs a subject and a body, SMS needs a body, Viber needs a body and an SMS-fallback body. The default content stays as the fallback underneath every language you add.
Default content is your source, not a translation
The default content is the base message everyone falls back to — it isn't one of the languages above, and it isn't counted toward translation progress. Think of it as the master copy that the language versions sit on top of.
Tracking translation progress
Two indicators help you see what's still outstanding:
- A progress ring around the Translations button on each pipeline card shows the share of expected content that's filled — every supported language multiplied by the fields your channel needs. At a glance you can tell whether a pipeline is fully translated or just getting started.
- Inside the translations editor, a small status dot next to each language shows whether it's still empty, partly filled, or complete — so you know exactly which languages still need work.
Write your default content
Start with a complete default message. This is the version everyone falls back to.
Add a language
Pick a supported language and fill in the fields your channel requires.
Check the status dot
Aim to get each language marked complete so recipients in that language get the full message.
How a recipient's language is chosen
A recipient's language comes from their own information — the language attached to their item in the dispatch queue. The pipeline reads that language and looks for a matching version of your message.
- Set a specific language on the queue item and the recipient gets that version — or your default content if that language hasn't been translated.
- Leave it on Auto detect and the platform picks the best match, falling back to your default content when there's no match.
A queue item with no language set is treated as Auto detect and simply receives your default content. You can also give a pipeline a default language of its own, which sets the version used when nothing more specific applies.
Fallback behaviour
When a message is about to go out, the pipeline follows a simple rule:
- If the recipient's language has a version, that version is used.
- If it doesn't, the default content is used instead.
- Recipients with no language set (Auto detect) always receive the default content.
A message still sends even if an optional field is left blank — for example, an email with no subject line will still go out.
Always keep your default content complete
The default content is your safety net. Any recipient without a matching language version — including everyone on Auto detect — receives it. If the default is incomplete, those recipients get an incomplete message. Make sure your default is always finished before you rely on language versions.