The description must name the registered business
The requirementstatement
The campaign description must name the registered legal name or the registered DBA.
- Severityseverity
- BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- brand.company_name + campaign.description
- Where it liveslayer
- Brand ↔ campaignCROSS
- 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
- BandwidthInfobipAWSSinchPlivo
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Open the description with the registered name — the one on the brand record, not a product or campaign nickname — and keep it there. Done when the first sentence names the same business the brand record does.
A compliant exampleexample
Acme Coffee sends weekly promotional offers to customers who opted in at checkout — not "We send weekly promotional offers to our customers".
Common mistakespitfalls
- A product or programme name is not the registered name: "Acme Rewards" does not match a brand registered as Acme Coffee Co, LLC unless Acme Rewards is the registered DBA.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Bandwidth | 2006 | Yes |
| Infobip | 603 | Yes |
Notesnotes
Rules you will hit next
Other brand ↔ campaign rules at the same severity. A registration is judged as a whole, not rule by rule.
XBC-014 is one of 13 brand ↔ campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.