# CON-VERBAL-RECORD — Verbal consent must describe how assent is recorded

> The flow must state how the consumer’s spoken agreement is captured and retained — recording, transcript, IVR log, or timestamped CRM entry.

- **Rule ID:** CON-VERBAL-RECORD
- **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:** Fix the field — a better value in the form clears it
- **Required by:** FCC, CTIA, TCR
- **Applies:** Applies when consent was collected by live verbal and IVR.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-verbal-record/

## Why this rule exists

Spoken consent evaporates unless it is written down. If a complaint arrives eighteen months later, the retained record is the only thing standing between you and an unprovable claim, and both the FCC and CTIA expect the record to exist.

## How to fix it

Add a sentence to the message flow describing capture and retention. Name the system of record and what is stored against the customer.

## Example of a compliant value

```text
Calls are recorded, and the agent logs the consent timestamp, the script version read, and the number consented against the customer record in our CRM. Records are retained for at least 4 years.
```

## Common mistakes

- Two-party consent states constrain call recording — where you cannot record, log the timestamp and script version instead.