# CON-080 — The disclosure must name the programme the consumer is joining

> The point-of-consent disclosure must carry a programme or product description — what this particular messaging programme is.

- **Rule ID:** CON-080
- **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, T-Mobile, TCR, AWS, Bandwidth, Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-080/

## Why this rule exists

CTIA lists the programme description first among the call-to-action elements because it is what the consumer will recognise later: the name in the confirmation text, in the HELP reply, and on the unsubscribe page. Without it a consumer who joined three programmes from one brand cannot tell which one is texting them, and the opt-out they send lands against the wrong list.

## How to fix it

Name the programme in the consent sentence and use that same name in the opt-in confirmation, the HELP reply and the terms. Where the programme has no name, describe the product instead — "coffee subscription updates" is a description; "updates" is not. Done when the same words appear at the point of consent and in the first message that arrives.

## Example of a compliant value

```text
☐ Join Acme Coffee Rewards: text me offers and rewards balance updates.
```

## Common mistakes

- Naming the programme only in the page heading leaves the consent sentence generic, and the sentence is what a reviewer quotes.

## Notes

Distinct from CON-DISC-PURPOSE, which asks for the message CATEGORY (marketing, reminders, order updates). This asks which programme — CTIA MPBP §5.1.1(1) treats them as separate elements, and a disclosure can name a category without naming a programme.