STOP and HELP instructions must be legible — bold is not required
The requirementstatement
The STOP and HELP instructions must be legible in the rendered terms; bold typeface is no longer required.
- 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
- SMS terms typography as rendered
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- AI · visionVISION
- Needs the pixels: a screenshot of the opt-in surface, a scanned paper form, an MMS attachment.
- 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
- CTIA
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Leave the formatting alone if the instructions are readable. Where they are set in small print or the same weight as a wall of text, give them their own line rather than bolding them. Done when a reader can find the STOP instruction at a glance.
A compliant exampleexample
A short paragraph of its own: "To stop receiving messages, reply STOP to any message from us."
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-198 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.