An explicit affirmative opt-in control must exist
The requirementstatement
Consent must be captured by a deliberate affirmative action — a checkbox, toggle, or signature — never inferred from form submission.
- 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 surface
- Where it liveslayer
- Consent flowCONSENT_FLOW
- How Ekas settles itdetectability
- AI · crawlCRAWLAI · visionVISION
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would. Needs the pixels: a screenshot of the opt-in surface, a scanned paper form, an MMS attachment.
- 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
- CTIATCRFCCTwilio
- When it appliesapplicabilityText
- Applies when consent was collected by web form, checkout, account settings, third party and point of sale.
Why this rule existsrationale
Express written consent requires an act that means "yes to messages" and nothing else. When consent is bundled into pressing Submit, there is no way to distinguish someone who wanted texts from someone who wanted an account, and no way to evidence the difference later.
How to fix itremediation
Add a dedicated checkbox the customer must tick, unchecked by default, with the consent disclosure printed beside it. Replace any "by submitting this form you agree to receive texts" wording with a real control.
A compliant exampleexample
☐ By checking this box, you agree to receive recurring automated marketing text messages from Acme Coffee at the number provided. Consent is not a condition of any purchase. Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe or HELP for help. See our Terms of Service and Privacy Policy.
Rules you will hit next
6 other rules read consent surface. 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-043A mandatory phone field needs its own separate, optional SMS opt-inBlockingBLOCKINGCON-108The disclosure must be on the same page as the phone-number fieldBlockingBLOCKINGCON-AGE-GATEAge-gated programs require real age verification at opt-inBlockingBLOCKINGCON-BOX-BUNDLEDMessaging consent must be separate from terms acceptanceBlockingBLOCKINGCON-BOX-UNCHECKEDThe consent control must be unchecked by defaultBlockingBLOCKINGCON-DISC-ADJACENTDisclosures must appear at the point of opt-in, not only in linked documentsBlockingBLOCKING
CON-BOX-PRESENT is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.