Message flow must state message frequency

JSONMarkdown

The requirementstatement

The message-flow / CTA field must state the message frequency.

Severityseverity
BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
campaign.message_flow
Where it liveslayer
CampaignCAMPAIGN
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
TCRTwilioBandwidthAWS
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Frequency is one of the required disclosures at the point of consent, so its absence from the flow text tells a reviewer either that it was never disclosed or that the flow is incomplete. Both readings cost the submission, and the second one costs it twice because the reviewer then doubts the rest of the description.

How to fix itremediation

Add the frequency claim you make at the opt-in, word for word. Done when the flow and the disclosure on your form say the same thing — a reviewer comparing them will notice if one says "varies" and the other promises four a month. Put it in campaign.message_flow itself — this field is graded on its own text, not on what a reviewer would find by opening your site.

A compliant exampleexample

Message frequency varies, up to 4 messages per month.

Rules you will hit next

6 other rules read campaign.message_flow. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

CMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-059Message flow must describe the mechanism end to endBlockingBLOCKINGCMP-060Every opt-in method in use must be listed in the message flowBlockingBLOCKINGCMP-061Each declared method needs its own complete workflow paragraphBlockingBLOCKINGCMP-072Message flow must state the message typesBlockingBLOCKINGCMP-074Message flow must state that rates may applyBlockingBLOCKING

All campaign rules

CMP-073 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works