SMS terms must state message frequency and that rates may apply
The requirementstatement
The SMS terms section must disclose message frequency and that message and data rates may apply.
- 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
- terms body
- 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
- CTIATCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Add both statements to the SMS terms section, and make the frequency claim match what you tell people at the opt-in — a reviewer comparing the two will notice if one says "varies" and the other promises four a month.
A compliant exampleexample
Message frequency varies. Message and data rates may apply.
Rules you will hit next
5 other rules read terms 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-176 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.