# OPS-USECASE-SCOPE — The campaign must not describe content it is not registered to send

> The description must not mention message categories outside the declared use case.

- **Rule ID:** OPS-USECASE-SCOPE
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `campaign.description + campaign.usecase`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **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:** TCR, Twilio, T-Mobile
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-usecase-scope/

## Why this rule exists

Live traffic must match the registered use case, and the description is where a mismatch is visible before it becomes a filtering problem. A description promising "and occasional special offers" under a transactional use case has pre-announced the violation.

## How to fix it

Remove out-of-scope categories from the description, or change the use case to MIXED and collect promotional-grade consent to cover them.

## Example of a compliant value

```text
ACCOUNT_NOTIFICATION description should describe only account and order messaging, with no promotional aside.
```