Declared frequency must be consistent everywhere it appears
The requirementstatement
The message frequency stated in the consent disclosure, the SMS terms, and the campaign description must agree.
- 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 + terms + campaign.description
- Where it liveslayer
- OperationalOPERATIONAL
- 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
- CTIATCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
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.
A compliant exampleexample
All three read: "Message frequency varies."
Rules you will hit next
Other operational rules at the same severity. A registration is judged as a whole, not rule by rule.
OPS-FREQ-COHERENT is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.