SMS consent needs its own control and its own sentence
The requirementstatement
Messaging consent must not share a control or a sentence with email or phone-call consent.
- 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
- opt-in surface control set; 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
- TelnyxTwilioTextUsInfobipBirdSakariKlaviyo
- When it appliesapplicabilityText
- Applies when consent was collected by web form, checkout, account settings, third party and point of sale.
Why this rule existsrationale
How to fix itremediation
Split into two controls with two sentences: one for email, one for text. The SMS sentence carries the SMS disclosures; the email one does not need them. Done when a consumer can take the newsletter and decline the texts in one submission.
A compliant exampleexample
☐ Email me Acme Coffee news. ☐ Text me Acme Coffee offers. Msg frequency varies. Msg & data rates may apply. Reply STOP to unsubscribe, HELP for help.
Common mistakespitfalls
- Two checkboxes sharing one sentence above them is the same defect with extra steps — each control needs wording of its own that names its channel.
Notesnotes
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-134 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.