The terms should carry the standard boilerplate
The requirementstatement
The terms of service must include the standard boilerplate: severability, assignment, entire agreement, waiver, force majeure and notices.
- Severityseverity
- LowLOWBest practice. Worth fixing, rarely fatal on its own.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- terms of service 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
- Fix the policyTERMINAL_POLICY
- The fix lives in your privacy policy or SMS terms. Ekas can generate the missing clauses.
- Who requires itauthorities
- TCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Add the boilerplate block, and exclude messaging consent from the assignment clause explicitly. Done when all six are present and the assignment clause names the carve-out.
A compliant exampleexample
If any part of these terms is unenforceable the rest continues to apply. We may assign these terms; your text messaging consent is not assigned with them.
Rules you will hit next
6 other rules read terms of service body. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
POL-217 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.