# CON-059 — The consent control label must name the programme, not just contact

> The label on the consent control must say what the consumer is subscribing to — a bare "Text me" or "Contact me" is not specific enough.

- **Rule ID:** CON-059
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `consent checkbox label 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 submitted form
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** Telnyx, Bandwidth, Twilio
- **Applies:** Applies when consent was collected by web form, checkout, account settings, third party and point of sale.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-059/

## Why this rule exists

The label is the only sentence many consumers read before ticking, so it is the whole of what they agreed to. "We may contact you" agrees to nothing in particular, which means the brand cannot later show that recurring marketing was within it — and Bandwidth reads the same defect as a failure to name the specific message programme.

## How to fix it

Rewrite the label to name the brand and what the messages are about. Done when the label alone, with the rest of the page covered up, tells a stranger who will text them and why.

## Example of a compliant value

```text
☐ Text me Acme Coffee offers and rewards updates.
```

## Common mistakes

- "I agree to receive SMS messages" names the channel but not the programme, and Bandwidth rejects it for the same reason as "Contact me".

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Telnyx | `611` | yes |
| Twilio (gen2) | `30513` | yes |