# OPS-OPTOUT-CONF-ONLY — Opt-out confirmation must be the only message sent after revocation

> The campaign must declare a single opt-out confirmation and nothing further after a consumer revokes.

- **Rule ID:** OPS-OPTOUT-CONF-ONLY
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `campaign.optout_message`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** FCC, CTIA, TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-optout-conf-only/

## Why this rule exists

One final confirmation is permitted; anything after it is messaging someone who has revoked consent, which is both the clearest TCPA violation available and a carrier fee event. Declaring a confirmation is fine — declaring a follow-up sequence is a self-reported violation.

## How to fix it

Configure exactly one opt-out confirmation, keep it non-promotional, and make sure no other automation can fire at a revoked number afterwards.

## Example of a compliant value

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