Consent must not be claimed on behalf of unnamed partners

The requirementstatement

The opt-in language must not purport to grant consent to "our partners", "affiliates", "third parties", or a linked partner list.

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: TCRCTIAAWSTwilioAT&T
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

A consumer cannot consent to being messaged by a set of businesses they have not been told about, so this wording grants nothing while looking like it grants everything — and every carrier treats a number sent under it as having no consent behind it. It is standard boilerplate in lead-generation templates, which is how it reaches brands that have no intention of sharing anything.

How to fix itremediation

Delete the partner and affiliate wording from the consent sentence and name only the entities that will actually send. If a partner genuinely needs to message these consumers, they must collect their own consent under their own brand. Done when the sentence contains no open-ended category of recipient.

A compliant exampleexample

By checking this box you agree to receive recurring automated marketing texts from Acme Coffee. (No partner, affiliate, or third-party clause.)

Common mistakespitfalls

Linking a page that lists the partners does not cure it: the consumer would have to read a list to know who they are agreeing to, and reviewers reject the pattern rather than the length of the list.

Notesnotes

Distinct from CON-NO-TRANSFER, which is about where the consent CAME FROM. This rule is about a consent the brand did collect itself, worded to extend to senders it cannot bind. A brand can pass that rule and fail this one on the same page.

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-123Every entity allowed to send must be named in the consentBlockingBLOCKING 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-125 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.