Consent must not be purchased, shared, or transferred
The requirementstatement
Only the business that collected the consent may message the consumer; purchased lists and shared opt-ins are prohibited.
- 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
- campaign.message_flow
- Where it liveslayer
- Consent flowCONSENT_FLOW
- 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
- Hard stopHARD_STOP
- Not remediable. Resubmitting will not help, and anyone offering to fix it is selling you a rejection.
- Who requires itauthorities
- CTIAFCCTCRT-MobileTwilio
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Consent is non-transferable and non-assignable — it names a sender, and it does not survive being sold, shared with affiliates, or inherited by a sister brand. This is the rule behind the affiliate-marketing prohibition and behind most of the enforcement actions that produced 10DLC in the first place, which is why it is a hard stop rather than a fixable finding.
How to fix itremediation
A purchased, rented, affiliate-sourced or partner-shared list cannot be registered under any use case. The only remedy is to collect fresh consent directly, under this brand, before messaging those numbers.
Rules you will hit next
6 other rules read campaign.message_flow. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
CMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-059Message flow must describe the mechanism end to endBlockingBLOCKINGCMP-060Every opt-in method in use must be listed in the message flowBlockingBLOCKINGCMP-061Each declared method needs its own complete workflow paragraphBlockingBLOCKINGCMP-072Message flow must state the message typesBlockingBLOCKINGCMP-073Message flow must state message frequencyBlockingBLOCKING
CON-NO-TRANSFER is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.