An offline opt-in still needs a findable business behind it
The requirementstatement
A brand collecting consent entirely offline must still have a verifiable online presence a reviewer can find.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- brand website vs offline consent method
- 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
- TCRTwilioBandwidth
- When it appliesapplicabilityText
- Applies when consent was collected by paper form, point of sale, live verbal, IVR and employer / HR.
Why this rule existsrationale
How to fix itremediation
Supply a website that names the business, describes what it does, and carries the SMS terms and privacy policy. Where the business genuinely has no site, a complete and consistent listing — a verified profile with the same name, address and phone as the brand record — is what a reviewer will look for instead. Done when the campaign can be corroborated without the opt-in surface.
Common mistakespitfalls
- A social profile alone rarely satisfies this, because the policy pages have nowhere to live on 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-017 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.