# CON-DISC-STOP — Consent disclosure must explain how to opt out

> The disclosure must tell the consumer they can reply STOP to stop receiving messages.

- **Rule ID:** CON-DISC-STOP
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `consent disclosure text`
- **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:** AI judgement over the crawled website or policy page; AI vision over a consent artifact (screenshot, scan, MMS media)
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** CTIA, TCR, Twilio, FCC, T-Mobile
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-disc-stop/

## Why this rule exists

A consumer who does not know how to leave complains to their carrier instead, and carrier complaints are what trigger number blocking and violation fees. Telling them the exit at the moment they enter is both a legal requirement and the cheapest protection you have against a spam report.

## How to fix it

Add "Reply STOP to unsubscribe." to the consent disclosure. Name the keyword — a general promise that they can unsubscribe any time does not tell them how.

## Example of a compliant value

```text
Reply STOP to unsubscribe, HELP for help.
```