{
  "id": "POL-193",
  "slug": "pol-193",
  "title": "The programme described in the terms must match the registered use case",
  "statement": "The programme description in the SMS terms must relate to the use case the campaign is registered under.",
  "rationale": "The terms are the public description of the programme and the use case is the private one, so a disagreement means one of them is wrong about what will be sent — and the reviewer resolves it by refusing the campaign. It happens most often when a terms page written for the whole business is attached to a narrower campaign.",
  "layer": "POLICY_PAGE",
  "layerSlug": "policy-page",
  "object": "SMS terms body vs campaign.usecase",
  "severity": "BLOCKING",
  "detectability": [
    "AI_FORM"
  ],
  "failureClass": "TERMINAL_POLICY",
  "artifact": "sms_terms",
  "authorities": [
    "AWS",
    "Twilio",
    "TCR"
  ],
  "codes": [
    {
      "provider": "Twilio",
      "code": "30893",
      "remediable": true,
      "generation": "gen1"
    }
  ],
  "applicabilityText": "Applies to every 10DLC registration.",
  "universal": true,
  "remediation": "Make the terms describe the categories the campaign is registered for, or register the use case the terms describe. Done when the two describe one programme.",
  "example": "Use case MARKETING · terms describe promotional offers and rewards updates — the same programme.",
  "phase": "approval",
  "automated": true,
  "url": "https://ekas.io/rules/10dlc/policy-page/pol-193/",
  "markdown": "https://ekas.io/rules/10dlc/policy-page/pol-193.md",
  "registry": "https://ekas.io/rules/10dlc/",
  "updated": "2026-07-25",
  "licence": "CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/"
}