The description must say how often the messages come
The requirementstatement
The campaign description must disclose the messaging frequency.
- 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
- campaign.description
- 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 to every 10DLC registration.
- In forceeffectiveFrom / effectiveTo
- From 2024-11-06
Why this rule existsrationale
Frequency is what a reviewer compares against the declared volume and against the frequency promised at opt-in, and a description that omits it leaves both comparisons unmade. It is also the disclosure a consumer relies on most directly: the difference between four messages a month and four a week is the difference between a programme they keep and one they report.
How to fix itremediation
Add the frequency claim you make at the opt-in, in the same words. Done when the description, the CTA and the disclosure on your form all say the same thing about how often messages arrive.
A compliant exampleexample
Acme Coffee sends up to 4 promotional messages per month to customers who opted in at checkout.
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 | 6004 | Yes |
Notesnotes
Kept separate from CMP-073, which requires the same disclosure in the message-flow field: both fields carry it on the same registration, so satisfying one does not discharge the other. Effective from the Bandwidth vetting change of 2024-11-06.
Rules you will hit next
6 other rules read campaign.description. 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-035The description must describe this programme, not messaging in generalBlockingBLOCKINGCMP-037The description must name the business that sends the messagesBlockingBLOCKINGCMP-DESC-LENCampaign description must be 40–4096 charactersBlockingBLOCKINGMSG-DESC-QUALITYCampaign description must explain who, what, and how they opted inBlockingBLOCKINGCMP-042A programme that asks for money must say soHighHIGHCMP-051A first-party lender must use the phrase the reviewer looks forHighHIGH
CMP-041 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.