Verbally-collected informational campaigns need the mockup and the messages

The requirementstatement

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.

Severityseverity: HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: consent artifact + campaign.sample_messages
Where it liveslayer: Consent flowCONSENT_FLOW
How Ekas settles itdetectability: AI · formAI_FORM; A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
What the fix involvesfailureClass: Supply evidenceTERMINAL_EVIDENCE; Needs proof only you hold: a screenshot, a recording, a scan of the form people signed.
Who requires itauthorities: AWS
When it appliesapplicabilityText: Applies when consent was collected by live verbal and IVR, and the use case is NOT MARKETING, MIXED and SWEEPSTAKE.

Why this rule existsrationale

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 itremediation

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.

A compliant exampleexample

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 mistakespitfalls

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.

Notesnotes

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.

Rules you will hit next

Other consent flow rules at the same severity. A registration is judged as a whole, not rule by rule.

CON-017An offline opt-in still needs a findable business behind itHighHIGH CON-033Opt-in evidence must be the live surface, not a mockup of itHighHIGH CON-042The phone field must be optional on a general-purpose formHighHIGH CON-044A required phone field must carry an SMS disclaimer beside itHighHIGH CON-064A kiosk or terminal must not pre-fill the consumer's numberHighHIGH CON-071The decline path must be as usable as the accept pathHighHIGH

All consent flow rules

CON-038 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.