Some states cap how often you may raise the same subject
The requirementstatement
Where the recipient's state sets one, a per-subject frequency cap — commonly three messages per 24 hours on the same subject matter — must be enforced.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
- What is checkedobject
- per-recipient send count by subject, 24-hour window
- Where it liveslayer
- OperationalOPERATIONAL
- How Ekas settles itdetectability
- Post-submissionUNDETECTABLE_PRE_SUBMISSION
- The subject does not exist yet at submission time: a reply window, an expiring PIN, a queue position. Reported with its deadline.
- What the fix involvesfailureClass
- Wait on someone elseTERMINAL_EXTERNAL
- Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
- Who requires itauthorities
- state law (FL, OK, MD, NJ, OR)
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Count sends per recipient per subject across every automation rather than per campaign, and cap at three in 24 hours for the states that set one — or universally, which is simpler and rarely costs anything. Done when three automations about one product cannot all fire on the same day.
Check this yourselfattestation
No tool can settle this one for you. Here is the check, and what wrong looks like.
Could three automations about one product all fire to the same person on the same day?
- 1Build a subject taxonomy first — without one there is nothing to count against, and per-campaign counters will report compliance while the cap is broken.
- 2Count sends per recipient per subject across every automation, and cap at three in 24 hours universally rather than per state.
What wrong looks like: A cart reminder, a discount on the same item and a low-stock alert are three messages about one thing, sent by three automations that each believe they are within their own limit.
Notesnotes
Rules you will hit next
Other operational rules at the same severity. A registration is judged as a whole, not rule by rule.
OPS-097 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.