# OPS-FREQ-COHERENT — Declared frequency must be consistent everywhere it appears

> The message frequency stated in the consent disclosure, the SMS terms, and the campaign description must agree.

- **Rule ID:** OPS-FREQ-COHERENT
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `consent disclosure + terms + 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:** CTIA, TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-freq-coherent/

## Why this rule exists

Frequency appears in at least three places, and each is written at a different time by a different person. A disclosure promising "up to 4 per month" beside terms saying "frequency varies" beside a description mentioning daily deals gives a reviewer three different programmes to choose between, and they choose the one that fails.

## How to fix it

Pick one frequency statement and use it verbatim in all three places. "Message frequency varies" is the safest when volume is irregular, because a numeric cap becomes a promise you are held to.

## Example of a compliant value

```text
All three read: "Message frequency varies."
```