There is a per-recipient daily ceiling even without a state rule

The requirementstatement

No more than ten messages should reach one recipient in any 24-hour period without two-way engagement or explicit high-frequency consent.

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 24-hour send count
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: Telnyx
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Providers apply this as an acceptable-use limit regardless of state law, and crossing it reads as a malfunction rather than a campaign — which is usually what it is. The classic cause is a loop: an automation that fires on a status change, and a status that flaps.

How to fix itremediation

Cap per-recipient daily volume across all automations and alarm when the cap is hit, since hitting it usually means something is looping. Done when a runaway automation is stopped by the cap rather than by a complaint.

A compliant exampleexample

Per-recipient limit 10 per 24h across every campaign; breach pauses the automation and pages the owner.

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

Does your per-recipient daily cap span every campaign in the account, or sit inside one?

1Check where the counter lives. Per-campaign caps are the common implementation and they do not catch a loop.
2Cap per-recipient daily volume across all automations at ten, and alarm when it is hit — hitting it usually means something is looping.

What wrong looks like: An automation fires on a status change and the status flaps. Crossing the ceiling reads as a malfunction rather than a campaign, which is usually exactly what it is.

Notesnotes

A counter across the whole account. What the user has to check is that the cap spans campaigns rather than sitting inside one — per-campaign caps are the common implementation and they do not catch the loop.

Rules you will hit next

Other operational rules at the same severity. A registration is judged as a whole, not rule by rule.

OPS-034A programme in another language still owes the English keywordHighHIGH OPS-035The mandatory keywords must work over MMS tooHighHIGH OPS-044Suppression is brand-wide, not per numberHighHIGH OPS-047A state may give you less time than the federal limitHighHIGH OPS-052Silence after a scope question revokes everythingHighHIGH OPS-053A STOP answering a scope question must not be answered with anotherHighHIGH

All operational rules

OPS-098 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.