# CMP-041 — The description must say how often the messages come

> The campaign description must disclose the messaging frequency.

- **Rule ID:** CMP-041
- **Layer:** Campaign (`CAMPAIGN`)
- **Checks:** `campaign.description`
- **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 judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** Bandwidth
- **Applies:** Applies to every 10DLC registration.
- **In force from:** 2024-11-06
- **Canonical URL:** https://ekas.io/rules/10dlc/campaign/cmp-041/

## Why this rule exists

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 it

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.

## Example of a compliant value

```text
Acme Coffee sends up to 4 promotional messages per month to customers who opted in at checkout.
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Bandwidth | `6004` | yes |

## Notes

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.