Some opt-in must be described somewhere
The requirementstatement
The description or the message flow must describe some form of opt-in, however briefly.
- 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.description + 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
- Bandwidth
- When it appliesapplicabilityText
- Applies when the use case is NOT M2M.
Why this rule existsrationale
This is the floor beneath every other consent rule: a submission that never mentions how anyone joined the list is indistinguishable from one where nobody did. It is a different failure from a thin description — the elements are not merely incomplete, the subject is absent — and it is fixed by writing a sentence rather than by improving one.
How to fix itremediation
Write one sentence saying where consumers agree to receive the messages, then expand it into a full flow. Done when a reader can answer "how did these people end up on this list?" from the submission alone.
A compliant exampleexample
Customers opt in at checkout on acmecoffee.com by ticking a box to receive offers by text.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Bandwidth | 2100 | Yes |
Notesnotes
The presence floor beneath CMP-059's quality bar. Kept separate because they fail and are fixed differently: CMP-059 grades a described mechanism against a standard, while this one asks whether a mechanism was described at all, and a submission failing this one fails CMP-059 for a reason that would mislead.
Rules you will hit next
2 other rules read campaign.description + 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-045The programme must be application-to-person, not personal messagingBlockingBLOCKINGOPS-QUIET-HOURS-DISCLOSEDQuiet-hours handling should be disclosed for promotional programmesMediumMEDIUMCMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-017Every mandatory campaign attribute must be explicitly setBlockingBLOCKINGCMP-024Registration fields must be written in EnglishBlockingBLOCKINGCMP-028Opt-in evidence must be a JPG, PNG or PDF under 500 KBBlockingBLOCKING
CMP-089 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.