The sending entities must be named before consent is captured

The requirementstatement

The authorised sending entities must be disclosed before the consumer acts, not on the confirmation screen or in the first message.

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: disclosure ordering on the opt-in surface
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&T
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Consent is given at the moment of the act, so a name disclosed afterwards was not part of what was agreed to. Brands get this wrong in a specific and understandable way: the confirmation page is where they put the full legal detail, because that is the page nobody has to be persuaded by.

How to fix itremediation

Move the entity names above the consent control, inside the sentence the consumer is agreeing to. Keep them on the confirmation as well if you like — the requirement is that they appear before the act, not that they appear only there. Done when the names are on screen at the moment the box is ticked.

A compliant exampleexample

☐ Text me offers from Acme Coffee and my local Acme Coffee franchise location.

[Join] — the names appear above this button, not on the page it leads to.

Only meaningful once these passdependsOn

CON-123Every entity allowed to send must be named in the consent

Notesnotes

Depends on CON-123: where no entity is named at all, that is CON-123's finding and this rule has no ordering to judge.

Rules you will hit next

Other consent flow rules at the same severity. A registration is judged as a whole, not rule by rule.

CON-123Every entity allowed to send must be named in the consentBlockingBLOCKING CON-008The live CTA and the declared message flow must say the same thingBlockingBLOCKING CON-010The three subscriber-management attributes must be declared trueBlockingBLOCKING CON-013Subscriber attributes must agree with the message bodies suppliedBlockingBLOCKING CON-023Evidence URLs must resolve without a loginBlockingBLOCKING CON-024The opt-in URL must serve a certificate that verifiesBlockingBLOCKING

All consent flow rules

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