The policy on the site and the policy attached to the registration must agree
The requirementstatement
Where a policy document is uploaded with the registration and a policy also exists on the site, the two must not conflict.
- 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
- crawled policy body vs uploaded policy document
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- 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 policyTERMINAL_POLICY
- The fix lives in your privacy policy or SMS terms. Ekas can generate the missing clauses.
- Who requires itauthorities
- AWS
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Publish the uploaded version on the site so the two are the same document, and upload the published page rather than a separately maintained file. Done when the attached document and the live page carry identical messaging clauses.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twiliogen1 | 30908 | 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-026 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.