A state may cap monthly volume and demand the logs

JSONMarkdown

The requirementstatement

Where a state sets monthly solicitation volume caps and log-production duties, both must be met.

Severityseverity
MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
When it bitesphase
After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
What is checkedobject
monthly solicitation volume and log production
Where it liveslayer
OperationalOPERATIONAL
How Ekas settles itdetectability
Human checkHUMAN
Only someone holding the document or making the call can settle it. Ekas tells you exactly what to look at.
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 (TN)
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Tennessee caps monthly solicitations and requires call logs produced every six months, which is an obligation with a filing deadline rather than a technical control — and a programme that has never produced the logs cannot produce them retrospectively if it did not retain the fields. The volume cap is low enough that a single national campaign can exceed it in one send.

How to fix itremediation

Count solicitations per state per month, and retain per-message logs in a form you can hand over. Done when you could produce six months of logs for one state on request without an engineering project.

Check this yourselfattestation

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

Could you produce six months of per-message logs for one state on request, without an engineering project?

  1. 1Establish whether you solicit into a state with volume caps and log-production duties — Tennessee is the named one.
  2. 2Count solicitations per state per month.
  3. 3Check your message logs carry the fields the production requires, and retain them in a form you can hand over.

What wrong looks like: The volume cap is low enough that a single national campaign can exceed it in one send, and logs cannot be produced retrospectively if the fields were never retained.

Notesnotes

A state filing obligation. What the user has to establish is whether they solicit into the state at all, and if so, that their message logs carry the fields the production requires — OPS-216 covers the log content.

Rules you will hit next

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

OPS-032A help request containing a stop-word is not an opt-outMediumMEDIUMOPS-042Somebody has to own revocations that arrive in conversationMediumMEDIUMOPS-050The opt-out confirmation is worth sending inside five minutesMediumMEDIUMOPS-051Only ask which messages to stop when there is more than one kindMediumMEDIUMOPS-057Log the sends you did not makeMediumMEDIUMOPS-062An opted-out consumer must be able to come backMediumMEDIUM

All operational rules

OPS-099 is one of 139 operational 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