{
  "id": "OPS-052",
  "slug": "ops-052",
  "title": "Silence after a scope question revokes everything",
  "statement": "Where a scope-clarification message is sent and the consumer does not reply, the revocation must be treated as covering all robocalls and robotexts from the sender.",
  "rationale": "Asking which messages to stop is permitted, but it cannot be a way of keeping somebody subscribed by default. A consumer who said stop and then ignored a follow-up question has not narrowed anything — and a system that treats no reply as \"carry on with the rest\" has converted a revocation into a menu the consumer never answered.",
  "layer": "OPERATIONAL",
  "layerSlug": "operational",
  "object": "scope-clarification timeout handling",
  "severity": "HIGH",
  "detectability": [
    "UNDETECTABLE_PRE_SUBMISSION"
  ],
  "failureClass": "TERMINAL_EXTERNAL",
  "authorities": [
    "FCC"
  ],
  "applicabilityText": "Applies to every 10DLC registration.",
  "universal": true,
  "remediation": "Suppress everything at the moment the revocation arrives, and treat any reply to the scope question as a request to re-subscribe to a subset. Done when no reply leaves the consumer receiving nothing.",
  "example": "STOP → suppress all → \"You have been unsubscribed from all Acme Coffee texts. Reply ORDERS if you would still like order updates.\"",
  "pitfalls": [
    "Suppressing only after a timeout expires leaves a window in which the programme is still sending to somebody who revoked — suppress first, ask second."
  ],
  "notes": "Only reachable once a scope question has been sent, which is a design choice the registration does not record. OPS-051 is the registration-side twin: it checks that the declared confirmation only asks a scope question where the consent covered several categories.",
  "phase": "post",
  "automated": false,
  "attestation": {
    "question": "If a consumer sends STOP and never replies to your scope question, do they receive nothing?",
    "howToCheck": [
      "Confirm the handler suppresses everything the moment the revocation arrives, before the question is sent.",
      "Treat any reply to the scope question as a request to re-subscribe to a subset, not as permission to continue.",
      "Test it: send STOP, ignore the follow-up, and check nothing else arrives."
    ],
    "failureLooksLike": "Suppressing only after a timeout leaves a window in which the programme is still sending to someone who revoked, and a system that reads no reply as \"carry on with the rest\" has converted a revocation into a menu nobody answered."
  },
  "url": "https://ekas.io/rules/10dlc/operational/ops-052/",
  "markdown": "https://ekas.io/rules/10dlc/operational/ops-052.md",
  "registry": "https://ekas.io/rules/10dlc/",
  "updated": "2026-07-25",
  "licence": "CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/"
}