# CON-DISC-FREQ — Consent disclosure must state message frequency

> The disclosure must tell the consumer how often messages will arrive.

- **Rule ID:** CON-DISC-FREQ
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `consent disclosure text`
- **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 crawled website or policy page; AI vision over a consent artifact (screenshot, scan, MMS media)
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** CTIA, TCR, Twilio, Bandwidth
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-disc-freq/

## Why this rule exists

Frequency is the expectation that determines whether your third message of the week reads as a service or as spam. Undisclosed frequency is a leading driver of opt-outs and complaints, and a high opt-out rate is itself a signal carriers use to throttle a campaign.

## How to fix it

Add a frequency statement to the disclosure. "Message frequency varies" is accepted everywhere and is the safe default if your volume is irregular; a concrete cap like "up to 4 messages per month" is stronger if you can honour it.

## Example of a compliant value

```text
Message frequency varies. Message and data rates may apply.
```

## Common mistakes

- Promising a numeric cap you exceed is worse than saying "varies" — the cap becomes a claim you are held to.