Every page that collects a number needs consent language

The requirementstatement

SMS opt-in language and a consent control must appear on every page of the site that collects a mobile number, not only the page named in the registration.

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: all pages containing a 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: TelnyxCommioBird
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Numbers reach the sending list from every form on the site — contact, booking, quote, donation, callback — and the ones collected on unlabelled forms carry no consent at all. Reviewers crawl for phone inputs rather than trusting the registered URL, which makes this the single highest-yield finding in the corpus, and the one brands are most surprised by: they fixed the signup page and never thought of the contact form.

How to fix itremediation

Inventory every form on the site that takes a phone number, and add the consent control and disclosure to each one — or remove the phone field from the forms that do not need it, which is usually the cheaper fix. Done when a site-wide search for phone inputs returns nothing without a consent block beside it.

Common mistakespitfalls

Forms embedded from a booking or scheduling vendor are the ones most often missed, because nobody thinks of them as pages on the site.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Telnyx	803	Yes

Notesnotes

Needs a whole-site crawl for phone inputs. The current crawler fetches the registered page only, so this rule will return UNCLEAR in production until that lands — recorded here rather than omitted, because the requirement is real and the gap is the crawler's.

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-049Secondary collection pages owe the full disclosure, not a token lineBlockingBLOCKING CON-008The live CTA and the declared message flow must say the same thingBlockingBLOCKING CON-010The three subscriber-management attributes must be declared trueBlockingBLOCKING CON-013Subscriber attributes must agree with the message bodies suppliedBlockingBLOCKING CON-023Evidence URLs must resolve without a loginBlockingBLOCKING CON-024The opt-in URL must serve a certificate that verifiesBlockingBLOCKING

All consent flow rules

CON-048 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.