# CON-KEYWORD-CONFIRM — Keyword opt-in requires a compliant confirmation reply

> The auto-reply sent after a keyword opt-in must carry the brand, frequency, rates, STOP and HELP.

- **Rule ID:** CON-KEYWORD-CONFIRM
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `campaign.optin_message`
- **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 field — a better value in the form clears it
- **Required by:** CTIA, TCR, Bandwidth, AWS
- **Applies:** Applies when consent was collected by text-to-join keyword.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-keyword-confirm/

## Why this rule exists

The confirmation message is the consumer’s receipt: it is where they learn what they just joined and how to leave. CTIA treats it as a required disclosure surface in its own right, and it is the one element of a keyword program you control completely.

## How to fix it

Write the opt-in confirmation to include all five elements within the 320-character limit.

## Example of a compliant value

```text
Acme Coffee: you're subscribed to offers. Msg frequency varies. Msg & data rates may apply. Reply HELP for help, STOP to cancel.
```