Solutions · Mobile & SMS Marketing
A message that fits in 160 characters in English can blow its budget to 70 the moment it switches encoding for a non-Latin script. Here's exactly how a message moves from a carrier and compliance audit to a delivered send that actually fits, and stays compliant.
01 · Strategy
Before a single alert is written, we audit carrier delivery norms in that market, map which languages trigger a switch from 160-character GSM-7 to 70-character UCS-2 encoding, and review local data-privacy and consent law (GDPR, POPIA, and equivalents) for what an opt-in actually has to say.
02 · Production
Alerts and push notifications move through the same engine, with the character-budget constraint from Strategy built into generation, not discovered after the fact.
Hyper-concise, transcreated alerts are written inside that language's real character budget, 160 characters for GSM-7 scripts, 70 for UCS-2 scripts like Arabic, Japanese, Korean, or Cyrillic.
Every message is scored on character-budget overflow risk, consent/compliance language, and claim density before it's queued.
Compliance review confirms opt-in and consent language meets that market's law; a native linguist sign-off catches anything that reads clipped or unnatural inside the tighter budget.
| Signal | What it measures here | Weight |
|---|---|---|
| Character-budget overflow risk | Whether a single non-Latin character silently drops the segment limit from 160 to 70 | High: any overflow forces a rewrite |
| Consent/compliance risk | Whether opt-in and data-use language meets that market's privacy law | High: any hit forces Needs Rebuild |
| Claim/regulatory density | Pricing or promotional claims that trip local advertising or telecom regulations | High |
| Carrier delivery risk | Known delivery or filtering issues for that message type on that market's carriers | Medium |
03 · Delivery
Delivery accounts for the consent record and the carrier, not just the message text.
Messages push directly into your SMS gateway, pre-validated against that language's character-budget limit.
Push payloads formatted for each OS's notification-length limits per locale, not a one-size guess.
Linked mobile-web pages stay in sync with the message's claims and offer, so the tap matches the text.
Consent records sync per market, so a send never reaches someone whose opt-in doesn't meet that market's requirement.
04 · Optimization
We track delivery and opt-out by carrier and market, and re-audit compliance language as local rules change.
Send us a current SMS or push campaign and the markets it's running in. We'll show you the encoding and compliance risk, free.
Request a Content Intent Audit Or talk it through first, schedule a call → See all 8 channels →