# CON-038 — Verbally-collected informational campaigns need the mockup and the messages

> An informational campaign collecting consent by phone must supply both a mockup of the opt-in workflow and the message content that will be sent under it.

- **Rule ID:** CON-038
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `consent artifact + campaign.sample_messages`
- **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:** Supply evidence only you hold
- **Required by:** AWS
- **Applies:** Applies when consent was collected by live verbal and IVR, and the use case is NOT MARKETING, MIXED and SWEEPSTAKE.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-038/

## Why this rule exists

With no page to crawl and no marketing copy to read, a reviewer assessing a phone opt-in has only two things: how the ask is made and what arrives afterwards. AWS asks for both together because either alone is unfalsifiable — a reasonable script proves nothing if the messages turn out to be promotional, and reasonable messages prove nothing if nobody agreed to them.

## How to fix it

Attach the workflow mockup — the script page, call flow, or agent screen, whichever the consumer's consent actually passes through — and populate the sample messages with the real notifications you intend to send. Done when the two read as one story: the script promises a category of message and the samples are that category.

## Example of a compliant value

```text
Attached: the agent screen showing the consent step and the script read from it. Samples: "Acme Coffee: your service appointment is confirmed for Tue 9am. Reply STOP to opt out, HELP for help."
```

## Common mistakes

- Samples that are more promotional than the script promised fail the use-case check as well — the script is what scopes the consent, so it is the samples that have to move.

## Notes

The catalog conditions this on an informational use case; the registry has no "informational" flag, so it is expressed as an exclusion of the promotional use cases. AWS states it for verbal collection only, which the consent-method tag carries.