{
  "id": "CON-038",
  "slug": "con-038",
  "title": "Verbally-collected informational campaigns need the mockup and the messages",
  "statement": "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.",
  "rationale": "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.",
  "layer": "CONSENT_FLOW",
  "layerSlug": "consent-flow",
  "object": "consent artifact + campaign.sample_messages",
  "severity": "HIGH",
  "detectability": [
    "AI_FORM"
  ],
  "failureClass": "TERMINAL_EVIDENCE",
  "authorities": [
    "AWS"
  ],
  "applicability": {
    "consentMethods": [
      "verbal_live",
      "verbal_ivr"
    ],
    "excludeUseCases": [
      "MARKETING",
      "MIXED",
      "SWEEPSTAKE"
    ]
  },
  "applicabilityText": "Applies when consent was collected by live verbal and IVR, and the use case is NOT MARKETING, MIXED and SWEEPSTAKE.",
  "universal": false,
  "remediation": "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": "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.\"",
  "pitfalls": [
    "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.",
  "phase": "approval",
  "automated": true,
  "url": "https://ekas.io/rules/10dlc/consent-flow/con-038/",
  "markdown": "https://ekas.io/rules/10dlc/consent-flow/con-038.md",
  "registry": "https://ekas.io/rules/10dlc/",
  "updated": "2026-07-25",
  "licence": "CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/"
}