# CMP-124 — A multi-step consent flow must be captured at every step

> Where consent is collected across several screens, evidence must show each step rather than the final one.

- **Rule ID:** CMP-124
- **Layer:** Campaign (`CAMPAIGN`)
- **Checks:** `opt-in screenshots`
- **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 vision over a consent artifact (screenshot, scan, MMS media)
- **Fix type:** Supply evidence only you hold
- **Required by:** Twilio, LeadConnector, optinfix
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/campaign/cmp-124/

## Why this rule exists

In a multi-step flow the disclosure and the consent control are usually on different screens, so a screenshot of the step carrying the button proves nothing about what was disclosed before it. This is the flow shape where a compliant programme most often looks non-compliant — everything required was shown, and the evidence only covers the last screen of it.

## How to fix it

Capture every screen between arriving and consenting, in order, and combine them into one PDF. Done when the sequence shows the disclosure and the consent act without a gap a reviewer has to fill in.

## Example of a compliant value

```text
A three-page PDF: the product page with the offer, the form with the phone field and disclosure, the confirmation screen after submitting.
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `30917` | yes |