# CON-IVR-CONFIRM — IVR opt-in must capture an unambiguous confirmation step

> An IVR flow must require a distinct keypress or spoken confirmation specifically for messaging consent.

- **Rule ID:** CON-IVR-CONFIRM
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `campaign.message_flow`
- **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:** TCR, FCC
- **Applies:** Applies when consent was collected by IVR.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-ivr-confirm/

## Why this rule exists

In an automated menu it is trivially easy for a caller to reach the end of a flow without having agreed to anything in particular. A dedicated confirmation step is what makes the resulting log entry mean "yes to texts" rather than "completed the call".

## How to fix it

Add a dedicated consent step with its own keypress, after the disclosure has been read, and log the keypress with a timestamp.

## Example of a compliant value

```text
"To agree to receive recurring automated text messages from Acme Coffee at this number — message frequency varies, message and data rates may apply, reply STOP to cancel — press 1 now. To continue without text messages, press 2."
```