## Why One Message Doesn't Fit Every Language If your subscriber list spans more than one country, you are almost certainly sending to people who speak more than one language. Many teams still send a single text to everyone, usually in English, and hope it lands. Some recipients read it fine. Others skim past a message that feels foreign, misread the offer, or reply STOP because the text looks like spam.
Multilingual SMS fixes that by sending each recipient a version written in their language. It sounds simple, but it touches almost every part of a campaign: how you store language data, how you write and approve templates, how you handle recipients whose language you don't know, how character encoding changes the cost of each message, how opt-out replies arrive, and how you measure results by language rather than in one blended number.
This guide walks through how to plan and run multilingual SMS campaigns without doubling your workload or your error rate. It covers collecting language data, building template sets, choosing fallbacks, keeping translations short enough for SMS, managing encoding and segment costs, timing sends across countries, and reading the results. ## Country Is Not the Same as Language The most common shortcut is to infer language from the phone number's country code.
It is a reasonable starting point, and sometimes it is the only signal you have. But country and language are not the same thing, and treating them as identical produces predictable mistakes. - **Multilingual countries.** Switzerland, Belgium, Canada, India, and many others have more than one widely spoken language. A +41 number tells you nothing about whether the person prefers German, French, or Italian.
- **Expats and travelers.** A subscriber with a UK number may prefer Spanish or Polish. A number registered in one country may belong to someone who signed up in another language entirely. - **Shared regional languages.** Spanish, Arabic, French, and Portuguese are spoken across many countries, with differences in vocabulary, tone, and formality that matter in short marketing copy. Use country as a fallback signal, not the main one.
The best source of language is what the subscriber told you, either explicitly or through the context in which they signed up. ## Collect Language Data at Signup The cheapest moment to learn someone's language is when they join your list. A few practical options: - **Record the language of the signup form.** If someone subscribes on the German version of your site, store "de" with their contact record.
This is usually the most reliable signal you can get without asking. - **Add an optional language field.** A short dropdown on the form lets people choose. Keep it optional so it doesn't hurt conversion, and fall back to the form language when it's empty.
- **Pass language through your API or import.** If contacts arrive from a CRM, ecommerce platform, or lead source, include a language column or field with every record rather than reconstructing it later. - **Use a consistent code format.** Pick one convention, such as two-letter ISO 639-1 codes ("en", "de", "fr", "ar"), optionally with a region ("pt-BR", "es-MX"). Mixed values like "English", "EN", "eng", and "en_US" in the same column turn segmentation into guesswork.
When you import an existing list, clean the language column the same way you clean phone numbers: normalize the values, map variants to your standard codes, and flag anything you can't map. A list with a reliable language field is worth far more than one with a field that's right most of the time. ## Build Template Sets, Not Separate Campaigns There are two ways to run a multilingual send.
The first is to split your audience by language and create a separate campaign for each. It works for two languages. At five or ten, it becomes a maintenance problem: separate schedules, separate links, separate reports, and many chances for one version to drift out of sync with the others.
The second is to keep one campaign with a **template set**: one logical message that has a version for each language you support, with the right version picked for each recipient at send time. The offer, the link destination, the schedule, and the reporting stay in one place. Only the wording changes. A good template set has: - **One source message.** Write the master version first, get it approved, and translate from it.
Every language version should say the same thing, with the same offer, the same deadline, and the same call to action. - **Matching merge fields.** If the source uses a first name and a discount code, every translation must use the same fields with the same names. A translation that renames or drops a field will either send a raw placeholder or leave a gap.
- **A version owner.** Someone who reads the language should review each version before it goes live. Machine translation is a useful first draft for SMS, but short promotional copy is exactly where awkward phrasing shows. - **A default.** Every set needs a version that goes to recipients whose language is missing or unsupported. More on that below.
### Example: one offer, three languages Here is what a small template set might look like for a weekend sale. Each version keeps the same structure: brand, offer, deadline, link, opt-out. - **English (default):** "Brand: 20% off everything this weekend only. Shop now: [link] Reply STOP to opt out" - **German:** "Brand: Nur dieses Wochenende 20 % auf alles.
Jetzt shoppen: [link] Abmelden: STOP antworten" - **Spanish:** "Brand: 20 % de descuento en todo solo este fin de semana. Compra ya: [link] Responde STOP para darte de baja" Notice that the Spanish version is noticeably longer. That's normal, and it's the next thing to plan for. ## Translations Change Length, and Length Changes Cost SMS is priced per segment, and translated text rarely stays the same length as the source.
Romance and Germanic languages often run longer than English. Some languages are more compact. That matters because a message that fits in one segment in English may spill into two in another language, doubling the cost for that part of the audience. Encoding makes the difference bigger. A standard SMS using the GSM-7 character set holds up to 160 characters in a single segment, or 153 per segment when the message is split.
As soon as a message includes a character outside GSM-7, it's typically sent as Unicode (UCS-2), which holds 70 characters in a single segment, or 67 per segment when split. For a deeper look at how this works, see our guide to SMS character limits and encoding. In practice, that means: - **Languages written in non-Latin scripts**, such as Arabic, Hebrew, Russian, Greek, Hindi, Chinese, Japanese, Korean, and Thai, will generally be sent as Unicode.
Plan your copy around the 70-character limit, not 160. - **Latin-script languages can still trigger Unicode.** GSM-7 covers many accented characters, but not all. Letters such as á, í, ó, ú, ã, and õ are not in the basic GSM-7 set, so a single one of them in Spanish or Portuguese copy can switch the whole message to Unicode.
- **Some characters count double in GSM-7.** Characters from the GSM-7 extension table, such as the euro sign, square brackets, curly braces, and the tilde, use two character positions each. - **Hidden characters cause surprises.** Curly quotes, long dashes, and non-breaking spaces pasted from a document or translation tool often aren't GSM-7 characters. They can silently push a message into Unicode even when every visible letter is fine.
Some networks support national language shift tables that let certain languages use more characters within a GSM-style encoding, but support varies, so don't count on it when budgeting. ### How to keep translated messages in budget - **Set a segment target per language,** not just a character count. "One segment" means 160 characters for one version and 70 for another.
- **Write the source short.** Every word you cut from the master version gets cut from every translation. - **Ask translators for SMS copy, not literal translation.** A good SMS translation keeps the meaning and the call to action, not every word. - **Decide deliberately about accents.** Removing accents can keep a message in GSM-7, but in some languages it makes the text look careless or changes meaning.
Make that choice per language with a native reader, not by default. - **Check every version before sending.** Preview each language with real merge data and confirm its encoding and segment count. Long names or codes inserted by merge fields can push a borderline message over the limit.
## Choose a Fallback for Unknown Languages No matter how carefully you collect data, some contacts will have no language on file, and some will have a language you don't support yet. Every template set needs a rule for them. Common options: 1. **A default language.** Send your main language, often English, to anyone without a match. It's simple and predictable, and it's the right choice when most of
Related Articles
One SMS route is a single point of failure. Learn how to design country routes, provider chains, safe failover, and rotation that keep texts moving.
Customers want relevant messages. They also want stronger privacy. That tension shapes SMS and email programs today.
Cross-border SMS can outperform email for time-sensitive offers and alerts. It can also become expensive and non-compliant quickly if you treat every...
Privacy expectations keep changing. So do messaging rules. Customers want useful SMS and email without losing control of their data. Compliance protects...
If you send application-to-person SMS to U.S. consumers over 10-digit long codes, A2P 10DLC registration is part of normal operations. Carriers use brand...
Discover essential strategies and best practices for building a compliant, engaged, and high-performing SMS subscriber list in 2026. Maximize your marketing ROI.
Master SMS marketing strategies while navigating the complex world of A2P, TCPA, and opt-in compliance. Learn to build effective, legal campaigns.
Black Friday and Cyber Monday reward SMS programs that are prepared. Learn how to clean and segment your list, pace your sends, write clear texts, and protect subscribers.
Explore SESender
SESender brings audience preparation, contact validation, sender and provider controls, scheduling, delivery tracking, and campaign reporting into one workspace. Review the current product and pricing information before deciding whether the platform fits your messaging workflow.
Explore the platform or review pricing.