Offline and keyword opt-in copy must carry the route to the policy
The requirementstatement
Verbal, IVR, keyword and email opt-in copy must state where the privacy policy can be found, or carry the disclosures inline.
- 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
- verbal script, IVR prompt, keyword CTA or opt-in email body
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- What the fix involvesfailureClass
- Produce a documentTERMINAL_ARTIFACT
- Needs a document that does not exist yet, such as a verbal script, a paper consent form, or QR landing copy. Ekas drafts it.
- Who requires itauthorities
- BandwidthAWS
- When it appliesapplicabilityText
- Applies when consent was collected by live verbal, IVR, text-to-join keyword and email.
Why this rule existsrationale
How to fix itremediation
Add one sentence to the script or the opt-in copy naming where the terms and privacy policy live, spoken as a typeable address. Done when someone who only heard or read the opt-in knows where to find the policy.
Common mistakespitfalls
- Naming the policy in the confirmation text is too late — the consumer has already consented. It has to be in the copy that asks.
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 | 7107 | Yes |
Notesnotes
Rules you will hit next
Other policy pages rules at the same severity. A registration is judged as a whole, not rule by rule.
POL-041 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.