Opt-in description must carry the registered brand name
The requirementstatement
The CTA / message-flow field must name the brand, matching the registered Brand or 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.display_name + campaign.message_flow
- 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
- BandwidthTelnyxAWS
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Name the brand explicitly in the opt-in description, and quote the consent wording the consumer agrees to — that wording should name the brand too.
A compliant exampleexample
Customers opt in at acmecoffee.com/signup by ticking an unchecked box agreeing to receive recurring automated marketing texts from Acme Coffee.
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-011 is one of 13 brand ↔ campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.