# CON-VERBAL-SCRIPT — Verbal opt-in requires the documented script

> A campaign collecting consent by phone must supply the exact script read to the consumer.

- **Rule ID:** CON-VERBAL-SCRIPT
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `campaign.message_flow + consent artifact`
- **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:** Produce a document that does not exist yet
- **Required by:** TCR, FCC, Aerialink
- **Applies:** Applies when consent was collected by live verbal and IVR.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-verbal-script/

## Why this rule exists

A verbal opt-in leaves no artifact unless you make one — there is no page to crawl and no box to screenshot. The script IS the consent surface, so it is the only thing a reviewer can inspect to decide whether what your agents say actually obtains consent.

## How to fix it

Attach the verbatim script your agents read, not a summary of it. We can generate a compliant script covering all eight required elements, which you can adapt and hand to your team.

## Common mistakes

- "Agents ask for permission to text" describes a policy, not a script — a reviewer cannot audit it.