# CON-163 — Keyword consent is bounded by what the advertisement promised

> Consent given by texting a keyword extends only to the programme advertised alongside that keyword.

- **Rule ID:** CON-163
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `keyword advertisement copy vs campaign content`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the submitted form
- **Fix type:** Produce a document that does not exist yet
- **Required by:** Klaviyo, CTIA
- **Applies:** Applies when consent was collected by text-to-join keyword.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-163/

## Why this rule exists

With text-to-join, the advertisement is the whole disclosure — the consumer decided before the first message existed. So a keyword advertised for shipping alerts collects consent for shipping alerts, and the promotional programme it actually enrols people into was never disclosed to anybody who joined.

## How to fix it

Make the advertised copy describe everything the keyword enrols the consumer into, or split the programmes and advertise a keyword for each. Done when the samples contain nothing a reader of the advertisement would not have expected.

## Example of a compliant value

```text
Text JOIN to 55512 for Acme Coffee offers and rewards updates. Msg frequency varies. Msg & data rates may apply. Reply STOP to cancel, HELP for help.
```

## Common mistakes

- Running one keyword across several campaigns is the usual cause, and it fails here even when each campaign is individually compliant.