# OPS-099 — A state may cap monthly volume and demand the logs

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

- **Rule ID:** OPS-099
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `monthly solicitation volume and log production`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **When it bites:** Falls due after approval, once you are live and sending
- **How it is detected:** Human check — only someone holding the document can settle it
- **Fix type:** Wait on an external system or a required interval
- **Required by:** state law (TN)
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-099/

## Why this rule exists

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 it

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 yourself

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

1. Establish whether you solicit into a state with volume caps and log-production duties — Tennessee is the named one.
2. Count solicitations per state per month.
3. Check 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.

## Notes

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.