# OPS-051 — Only ask which messages to stop when there is more than one kind

> A scope-clarification question may appear in the opt-out confirmation only where the consumer consented to several distinct message categories.

- **Rule ID:** OPS-051
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `campaign.optout_message + campaign.sub_use_cases`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** FCC
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-051/

## Why this rule exists

Asking "which messages would you like to stop?" of somebody who receives one kind reads as an obstacle, and the FCC treats a revocation as complete unless the consumer chose to narrow it — so the question buys nothing and delays the suppression. Where a consumer genuinely consented to two or three categories it is legitimate and useful, which is why the rule is about the mismatch rather than about the question.

## How to fix it

Where the campaign sends one category of message, make the opt-out confirmation unconditional and final. Keep a scope question only where the consent covered separately-described categories, and treat no reply to it as a full revocation. Done when the confirmation matches the number of things the consumer agreed to.

## Example of a compliant value

```text
Single-category campaign: "Acme Coffee: you have been unsubscribed and will receive no further messages. Reply HELP for help."
```

## Common mistakes

- A scope question that keeps sending until the consumer answers it inverts the rule — silence is revocation of everything, not permission to continue.