Brand, website and campaign content must describe the same business
The requirementstatement
The registered brand name, the brand website, and what the campaign says it sends must be coherent.
- 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 + brand.website + campaign.description
- Where it liveslayer
- Brand ↔ campaignCROSS
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- 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
- TwilioTCRAWSBandwidth
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Make the campaign description describe the business the website actually presents, under the name the brand is registered with. If the website belongs to a parent or agency rather than the sender, register the brand that owns the customer relationship instead.
A compliant exampleexample
Website acmecoffee.com sells coffee subscriptions; description: "Acme Coffee sends order updates and promotional offers to subscription customers who opted in at checkout."
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twiliogen2 | 30907 | Yes |
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-013 is one of 13 brand ↔ campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.