{
  "id": "CON-060",
  "slug": "con-060",
  "title": "The opt-in language must actually say SMS or text message",
  "statement": "The consent wording must name text messaging explicitly rather than referring generally to being contacted.",
  "rationale": "Consent runs to a channel. Agreeing to be \"contacted\" or to \"receive updates\" does not agree to texts, and the carriers reading that wording cannot tell whether the consumer expected a phone call, an email, or nothing at all. Twilio rejects it under a code whose whole description is that the opt-in flow does not explicitly mention SMS — it is a wording defect with a one-word fix that brands miss because they know what they meant.",
  "layer": "CONSENT_FLOW",
  "layerSlug": "consent-flow",
  "object": "consent disclosure text",
  "severity": "BLOCKING",
  "detectability": [
    "CRAWL"
  ],
  "failureClass": "TERMINAL_WEBSITE",
  "authorities": [
    "Twilio",
    "CTIA"
  ],
  "codes": [
    {
      "provider": "Twilio",
      "code": "30513",
      "remediable": true,
      "generation": "gen2"
    }
  ],
  "applicabilityText": "Applies to every 10DLC registration.",
  "universal": true,
  "remediation": "Put the words \"text messages\" or \"SMS\" into the consent sentence itself. Done when the sentence names the channel without relying on the page around it — a heading saying \"SMS signup\" above a box that says \"keep me updated\" does not carry it.",
  "example": "I agree to receive recurring automated marketing text messages (SMS) from Acme Coffee.",
  "pitfalls": [
    "An email opt-in reused for SMS is the usual source: the wording was written for a newsletter and the channel word was never added."
  ],
  "phase": "approval",
  "automated": true,
  "url": "https://ekas.io/rules/10dlc/consent-flow/con-060/",
  "markdown": "https://ekas.io/rules/10dlc/consent-flow/con-060.md",
  "registry": "https://ekas.io/rules/10dlc/",
  "updated": "2026-07-25",
  "licence": "CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/"
}