Brand content must be submitted in English

The requirementstatement

Every brand text field must be submitted in English; non-English submissions are rejected as untranslatable.

Severityseverity
HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
all brand text fields
Where it liveslayer
BrandBRAND
How Ekas settles itdetectability
DeterministicDETERMINISTIC
Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
What the fix involvesfailureClass
Fix the fieldRETRY_FIELD
A better value in the form fixes it. Ekas can rewrite it and re-check.
Who requires itauthorities
BandwidthInfobip
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Reviewers work in English and the registry offers no translation step, so a record in another script is not read strictly — it is returned. Businesses that trade bilingually submit their own language honestly, and the rejection reason ("untranslatable") gives no hint that the fix is to transliterate rather than to correct anything. The messages themselves may be in any language; it is only the registration that has to be readable.

How to fix itremediation

Re-enter the named fields in English, transliterating the legal name into the Latin alphabet exactly as it appears on the English-language registration document. Done when every brand field is in Latin script and a reviewer with no other language can read the record.

A compliant exampleexample

company_name: Acme Coffee Co, LLC · city: San Francisco — Latin script throughout, whatever language the messages themselves use

Common mistakespitfalls

  • Accented Latin characters are fine — José, Zürich, Ñ. It is a change of script, not of alphabet, that stops the record being readable.

Notesnotes

Only the script half is mechanical, and that is all this check claims: it reports Cyrillic, Greek, Hebrew, Arabic, Devanagari, Thai, CJK and Hangul in a brand field. Whether Latin-script text is actually English — French, Spanish, German — is a judgement no predicate can make, and the rule deliberately does not pretend to. Emoji are BRD-269 and are excluded here so one defect is not reported twice.

Rules you will hit next

2 other rules read all brand text fields. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

All brand rules

BRD-271 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.