Email or voice consent does not become SMS consent
The requirementstatement
Consent collected for email or phone calls must not be treated as consent to text, and an email list must not be migrated to SMS without a fresh opt-in.
- 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 scope; list provenance
- 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
- BandwidthT-MobileTwilioCTIA
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Consent runs to a channel, and the consumer who gave an address for a newsletter made no decision about their phone. Migrating a list is the single most common way a careful brand acquires numbers it has no consent for, because the numbers were genuinely volunteered and the brand genuinely has a relationship — everything about it feels legitimate except the part that matters.
How to fix itremediation
Numbers whose only consent was for another channel cannot be messaged under any use case. Re-permission them first: email the list asking them to opt in to texts, and send only to those who complete the SMS opt-in. The email invitation is not the consent — the landing page they submit is.
Notesnotes
HARD_STOP because there is no field that fixes it: the defect is which numbers are on the list, not how the campaign is described. The remediation is a real path, but it happens before registration rather than inside it.
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-008The live CTA and the declared message flow must say the same thingBlockingBLOCKINGCON-010The three subscriber-management attributes must be declared trueBlockingBLOCKINGCON-013Subscriber attributes must agree with the message bodies suppliedBlockingBLOCKINGCON-023Evidence URLs must resolve without a loginBlockingBLOCKINGCON-024The opt-in URL must serve a certificate that verifiesBlockingBLOCKINGCON-027The opt-in URL must land on a page that carries the opt-inBlockingBLOCKING
CON-132 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.