The brand name must be identical across samples, SMS terms and the opt-in disclosure
The requirementstatement
The brand or DBA used in the message samples must match the brand name in the SMS terms and the name shown in the opt-in disclosure.
- 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
- campaign.sample[] + terms body + consent disclosure
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- 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 policyTERMINAL_POLICY
- The fix lives in your privacy policy or SMS terms. Ekas can generate the missing clauses.
- Who requires itauthorities
- TCRCTIABandwidth
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
A consumer encounters the brand name three times — when they opt in, in the messages, and in the terms they consult later — and reviewers check that all three describe one sender. Marketing teams routinely use a shortened trading name in messages and the legal name in the terms, which reads as two different businesses sharing a programme.
How to fix itremediation
Choose one customer-facing name and use it identically in the samples, in the SMS terms, and in the opt-in disclosure. Register that name as the brand display name or DBA so the registration matches too.
A compliant exampleexample
All three use "Acme Coffee" (registered as the DBA of Acme Coffee Co, LLC).
Rules you will hit next
Other policy pages rules at the same severity. A registration is judged as a whole, not rule by rule.
POL-021Policy URLs must not redirectHighHIGHPOL-023A social profile is not a policy pageHighHIGHPOL-025Exactly one privacy policy must be discoverableHighHIGHPOL-026The policy on the site and the policy attached to the registration must agreeHighHIGHPOL-030Both documents must be linked from the site footer on every pageHighHIGHPOL-053The clause must say NOT SHARED, not merely "not sold"HighHIGH
POL-226 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.