Quiet hours sound simple until your list spans more than one time zone. Then a single send can be perfectly legal for half your recipients and a violation for the other half, at the exact same moment. Any campaign larger than a single locality needs to get this right.
The problem in one sentence
Quiet-hours rules are measured by the recipient's local time, not the sender's. So a blast you fire at 9:05pm from your office is fine for recipients in your zone and potentially a violation for anyone an hour ahead, where it's already past the cutoff. Fire it in the morning and you have the mirror problem to the west.
Where this bites
It bites statewide programs in the handful of states that span two zones, and it bites hard in any multi-state effort, a federal committee, a PAC, an advocacy push, where recipients are scattered across all four continental zones plus Alaska and Hawaii. The wider your geography, the narrower the window that's safe everywhere at once, and the easier it is to clip an edge without noticing.
How to handle it
Send by recipient local time, not a single clock. The right way to run a multi-zone program is to let the system stagger or gate the send so each recipient is contacted within their own permitted window, not to pick one moment and hope. That means your platform needs to know each number's location and enforce quiet hours per recipient, automatically. Trying to manage this by hand, "I'll send at a time that works for most of them", is how violations happen.
The safe-window discipline
When in doubt, aim for the hours that are permitted across every zone in your list, mid-day and early evening are your friends, and let the system hold anything that would land in a restricted window somewhere. A little conservatism on timing costs you nothing and removes an entire category of risk. For GOTV sends with real deadlines, plan the send schedule around the zones in advance rather than scrambling on the day.
Frequently asked questions
Are quiet hours based on my time or the recipient's?
The recipient's local time. A send that's fine in your zone can violate quiet hours for a recipient an hour ahead at the same moment, which is why multi-zone programs need per-recipient timing.
How do I text a multi-state list safely?
Let your platform send by each recipient's local time, staggering or gating so everyone is contacted within their own permitted window. Don't pick one clock time and hope it works for everyone.
What's the safe approach when I'm unsure?
Aim for hours permitted across every zone on your list, mid-day and early evening, and let the system hold anything that would land in a restricted window somewhere. Conservatism on timing costs nothing.
Timing is a compliance surface. See quiet hours by state.
Keep reading: The complete 72-hour GOTV plan and the mini-TCPA wave campaigns must watch.