Several states set a narrower quiet-hours window than the federal one

The requirementstatement

Where the recipient's state sets a narrower window than 8am–9pm, that window applies.

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: send time against the recipient state window
Where it liveslayer: OperationalOPERATIONAL
How Ekas settles itdetectability: External recordEXTERNAL_DATA; The fact that settles it lives in a register we cannot query, such as the IRS file, a postal database, or another provider’s tenant. Reported as a warning with the evidence to check, not as a pass.
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, WA, OR, CT, NY, NJ, VA)
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

The federal window is the widest one available, not the operative one: Florida, Oklahoma, Maryland, Washington and Oregon close at 8pm, and Connecticut does not open until 9am — the narrowest band in the country. A national send timed to the federal window is lawful for most recipients and a statutory-damages claim for the rest, and several of these statutes carry a private right of action specifically so that it is worth bringing.

How to fix itremediation

Either hold a per-state window table and reliable recipient location, or send only inside the intersection of every state window — 9am to 8pm local — which needs no state data at all. Done when no send can fall outside the narrowest applicable window.

A compliant exampleexample

National promotional window: 9:00am–8:00pm recipient local time, which clears every state rule at once.

Check this yourselfattestation

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

Can any send fall outside 9am–8pm in the recipient's local time?

1Choose between a per-state window table with reliable recipient location, and sending only inside the intersection of every state window — 9am to 8pm local, which needs no state data at all.
2Florida, Oklahoma, Maryland, Washington and Oregon close at 8pm; Connecticut does not open until 9am.

What wrong looks like: A national send timed to the federal 8am–9pm window is lawful for most recipients and a statutory-damages claim for the rest — and several of these statutes carry a private right of action precisely so it is worth bringing.

Notesnotes

Absorbs OPS-094 and OPS-095, which are two more rows of the same per-state table. Needs the recipient's state, which we do not hold. What the user has to choose is between building the table and adopting the intersection — the intersection costs an hour at each end of the day and removes the whole class of failure.

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-093 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.