# OPS-204 — Verbal consent records must substitute a call identifier for the IP address

> Where consent was verbal or via IVR, a call identifier must replace the IP-address field in the consent record.

- **Rule ID:** OPS-204
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `campaign.message_flow`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **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, FCC
- **Applies:** Applies when consent was collected by live verbal and IVR.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-204/

## Why this rule exists

The IP field is meaningless for phone consent, and leaving it empty produces a record that looks incomplete rather than method-appropriate. A call ID, recording ID, or agent identifier is the equivalent evidence and is what a reviewer expects for that method.

## How to fix it

Store a call ID, recording ID, or agent extension on verbal consent records in place of the IP address, and say so in the message flow.

## Example of a compliant value

```text
Verbal opt-ins store the call UCID, the agent ID, and the script version read, in place of an IP address.
```