# CON-DISC-PURPOSE — Consent disclosure must state the message type or purpose

> The consumer must be told what kind of messages they are agreeing to receive.

- **Rule ID:** CON-DISC-PURPOSE
- **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, AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-disc-purpose/

## Why this rule exists

Consent is scoped to what was disclosed. A consumer who opted in for order updates and then receives promotions did not consent to those promotions, and their complaint is well-founded — this is the single most common source of consumer-initiated spam reports, which are what drive carrier filtering against your numbers.

## How to fix it

Name the message category explicitly and make it match your declared use case — "marketing and promotional messages", "appointment reminders", "order and delivery updates". If you send more than one category, say so, and consider whether they need separate opt-ins.

## Example of a compliant value

```text
By checking this box, you agree to receive recurring automated marketing text messages from Acme Coffee at the number provided. Consent is not a condition of any purchase. Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe or HELP for help. See our Terms of Service and Privacy Policy.
```

## Common mistakes

- Declaring MARKETING as the use case while the disclosure only mentions "account updates" fails both this rule and the use-case consistency check.