Message flow must state who opts in and when
The requirementstatement
The message-flow / CTA field must state who is opting in and at what moment.
- Severityseverity
- BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- campaign.message_flow
- Where it liveslayer
- CampaignCAMPAIGN
- 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
- Fix the fieldRETRY_FIELD
- A better value in the form fixes it. Ekas can rewrite it and re-check.
- Who requires itauthorities
- TCRTwilioBandwidthAWS
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Which customers, at which point in their journey, is what determines whether the consent scope matches the messages sent. A flow that never says who is subscribing cannot be checked against the samples, and it is the field where list-purchase and scraped-number programmes give themselves away.
How to fix itremediation
Name the audience and the moment: which customers, at which step. Done when the flow makes clear that only people who took the action are on the list. Put it in campaign.message_flow itself — this field is graded on its own text, not on what a reviewer would find by opening your site.
A compliant exampleexample
Customers opt in during checkout, after entering delivery details and before placing the order; only customers who tick the box are subscribed.
Rules you will hit next
6 other rules read campaign.message_flow. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
CMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-059Message flow must describe the mechanism end to endBlockingBLOCKINGCMP-060Every opt-in method in use must be listed in the message flowBlockingBLOCKINGCMP-061Each declared method needs its own complete workflow paragraphBlockingBLOCKINGCMP-072Message flow must state the message typesBlockingBLOCKINGCMP-073Message flow must state message frequencyBlockingBLOCKING
CMP-084 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.