Every entity allowed to send must be named in the consent

The requirementstatement

The consent language must name each business that will send under it, not only the one the consumer is transacting with.

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: consent disclosure text
Where it liveslayer: Consent flowCONSENT_FLOW
How Ekas settles itdetectability: AI · crawlCRAWL; Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
What the fix involvesfailureClass: Fix the websiteTERMINAL_WEBSITE; The fix lives on your site. No amount of rewording the form clears it.
Who requires itauthorities: AT&TT-Mobile
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

AT&T requires consent to explicitly name the entities authorised to send, because the consumer's expectation is set by the name they read. A franchise group, a dealer network or a parent with several trading brands routinely collects once and sends from all of them, and every message from a name the consumer never saw reads to them as a leak of their number.

How to fix itremediation

List each sending entity by name in the consent sentence, or narrow the programme so only the named brand sends. Where the list is long, name the group and link a page that enumerates the members — the page must be reachable before the consumer agrees. Done when every number that will appear as a sender traces to a name in the disclosure.

A compliant exampleexample

By checking this box you agree to receive recurring automated marketing texts from Acme Coffee and from your local Acme Coffee franchise location.

Common mistakespitfalls

Naming a parent company the consumer has never heard of instead of the trading name they recognise satisfies the letter and defeats the purpose — name both.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Twilio	30506	Yes

Rules you will hit next

6 other rules read consent disclosure text. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

CON-060The opt-in language must actually say SMS or text messageBlockingBLOCKING CON-080The disclosure must name the programme the consumer is joiningBlockingBLOCKING CON-125Consent must not be claimed on behalf of unnamed partnersBlockingBLOCKING CON-DISC-BRANDConsent disclosure must identify the sending brand by nameBlockingBLOCKING CON-DISC-NOT-CONDITIONPromotional consent must state it is not a condition of purchaseBlockingBLOCKING CON-DISC-PURPOSEConsent disclosure must state the message type or purposeBlockingBLOCKING

All consent flow rules

CON-123 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.