The opt-in form must have a phone-number field
The requirementstatement
The opt-in form must collect a mobile number through a field of its own.
- 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 form phone input
- 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
- AWSBandwidthRingover
- When it appliesapplicabilityText
- Applies when consent was collected by web form, checkout, account settings, QR code and third party.
Why this rule existsrationale
A form with no number field cannot be where SMS consent is collected, whatever its consent text says — so the registration points at a surface that does not do what it claims. The usual cause is honest: the brand registered their newsletter page, where the only field is an email address, because that is where the SMS checkbox was added.
How to fix itremediation
Add a mobile-number input to the form the consent control sits on, and label it as a mobile number rather than a generic "phone". Done when a consumer can give you a number and their agreement in the same submission.
Common mistakespitfalls
- Collecting the number on a later step than the consent control splits the two, and a reviewer looking at the registered page sees consent with nothing to attach it to.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Bandwidth/DCA | 2139 | Yes |
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-041 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.