Consent disclosure must state message frequency
The requirementstatement
The disclosure must tell the consumer how often messages will arrive.
- 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
- consent disclosure text
- Where it liveslayer
- Consent flowCONSENT_FLOW
- How Ekas settles itdetectability
- AI · crawlCRAWLAI · visionVISION
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would. Needs the pixels: a screenshot of the opt-in surface, a scanned paper form, an MMS attachment.
- What the fix involvesfailureClass
- Fix the websiteTERMINAL_WEBSITE
- The fix lives on your site. No amount of rewording the form clears it.
- Who requires itauthorities
- CTIATCRTwilioBandwidth
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
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 itremediation
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.
A compliant exampleexample
Message frequency varies. Message and data rates may apply.
Common mistakespitfalls
- Promising a numeric cap you exceed is worse than saying "varies" — the cap becomes a claim you are held to.
Rules you will hit next
6 other rules read consent disclosure text. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
CON-060The opt-in language must actually say SMS or text messageBlockingBLOCKINGCON-080The disclosure must name the programme the consumer is joiningBlockingBLOCKINGCON-123Every entity allowed to send must be named in the consentBlockingBLOCKINGCON-125Consent must not be claimed on behalf of unnamed partnersBlockingBLOCKINGCON-DISC-BRANDConsent disclosure must identify the sending brand by nameBlockingBLOCKINGCON-DISC-NOT-CONDITIONPromotional consent must state it is not a condition of purchaseBlockingBLOCKING
CON-DISC-FREQ is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.