A multi-step consent flow must be captured at every step
The requirementstatement
Where consent is collected across several screens, evidence must show each step rather than the final one.
- 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
- opt-in screenshots
- Where it liveslayer
- CampaignCAMPAIGN
- How Ekas settles itdetectability
- AI · visionVISION
- Needs the pixels: a screenshot of the opt-in surface, a scanned paper form, an MMS attachment.
- 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
- TwilioLeadConnectoroptinfix
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
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 itremediation
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.
A compliant exampleexample
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 codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twilio | 30917 | Yes |
Rules you will hit next
Other campaign rules at the same severity. A registration is judged as a whole, not rule by rule.
CMP-016Contact email and phone must contain no spacesHighHIGHCMP-023Declared embedded links must come with a sample URLHighHIGHCMP-041The description must say how often the messages comeHighHIGHCMP-042A programme that asks for money must say soHighHIGHCMP-048Emergency framing requires the emergency use caseHighHIGHCMP-051A first-party lender must use the phrase the reviewer looks forHighHIGH
CMP-124 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.