You schedule a promo for 9:00 AM. Feels responsible — nobody wants a text at midnight. You hit send. Your Boston customers get it at 9. Your Denver customers get it at 7. Your Los Angeles and Seattle customers get it at 6:00 AM, before their alarm goes off, and a chunk of them reply STOP or file a complaint before their coffee is ready.
The number on your dashboard said 9:00 AM. It was true for exactly one time zone.
Full disclosure: I work for Ready, an SMS platform. We handle quiet-hours enforcement automatically, which is why I have opinions about this. But the underlying problem is platform-agnostic, and if you run a national list you've almost certainly triggered it without noticing.
Quiet hours are measured where the phone is, not where you are
The TCPA restricts marketing calls and texts to between 8:00 AM and 9:00 PM in the recipient's local time. Some states are stricter — Florida and Oklahoma effectively narrow it to 8 AM–8 PM under their mini-TCPA statutes, and a few restrict Sundays and holidays.
The word that trips people up is recipient's. Your scheduling clock runs on your office time zone. The 9:00 AM you picked is 9:00 AM in your building. For a customer three time zones west, "9:00 AM Eastern" is 6:00 AM, squarely inside the prohibited window.
If your list is national — and most ecommerce lists are — a single fixed send time is guaranteed to hit someone during quiet hours the moment your customers span more than one zone. It's not a risk you might run into. It's arithmetic.
The math on a "responsible" 9 AM send
Say you're based in New York and you have a 40,000-contact list distributed roughly the way a US ecommerce audience usually is — call it 45% Eastern, 25% Central, 15% Mountain, 15% Pacific. You schedule 9:00 AM your time.
| Contact's zone | Local delivery time | Inside 8 AM–9 PM? | Share of list | Contacts |
|---|---|---|---|---|
| Eastern | 9:00 AM | Yes | 45% | 18,000 |
| Central | 8:00 AM | Yes (barely) | 25% | 10,000 |
| Mountain | 7:00 AM | No | 15% | 6,000 |
| Pacific | 6:00 AM | No | 15% | 6,000 |
That's 12,000 texts — nearly a third of the send — landing before 8:00 AM local. Every one of them is a potential quiet-hours violation.
Now flip it. To be safe on the West Coast you push the send to noon Eastern. Your Pacific customers get it at 9:00 AM, fine. But now your best-engaged Eastern buyers get a promo at lunch instead of with morning coffee, and if you have any Alaska or Hawaii contacts you've got a fresh mess in the other direction. There is no single wall-clock time that's both compliant and optimally timed for a national list. That's the trap.
Why "a third of the list gets it early" is expensive, not just awkward
Two costs stack here.
Complaints and unsubs. A 6 AM marketing text reads as intrusive even to people who genuinely opted in. Carriers watch complaint rates on your 10DLC campaign, and a spike can get your throughput throttled or your traffic filtered — which quietly tanks delivery on every future send, promo or not.
TCPA exposure. Quiet-hours violations are a named, well-litigated category. Statutory damages run $500 per text, up to $1,500 for willful violations. Send 12,000 early texts and, even at the floor, you're looking at theoretical exposure in the millions. Nobody gets sued for all 12,000 at once, but plaintiff's firms build cases on exactly this pattern because it's so easy to prove — the timestamp is right there in the delivery log.
If you want the full picture of how these obligations fit together, our ecommerce SMS compliance walkthrough covers consent, quiet hours, and 10DLC as one system rather than separate checkboxes.
The fix is per-contact timezone-aware scheduling
The healthcare version of this problem is identical — we wrote up the same trap in patient recall batches — and the fix is the same everywhere: stop scheduling by your clock and start scheduling by theirs.
There are two ways platforms do this:
- Timezone-shifted sending. You pick a local target time — say "9:00 AM in each recipient's zone" — and the platform staggers the actual send so Eastern goes out at 9 Eastern, Central at 9 Central, and so on. Every contact gets it at the same local moment, which is both compliant and better for engagement.
- Quiet-hours enforcement as a hard gate. Regardless of what time you schedule, the platform holds any message that would land outside the recipient's permitted window and releases it when the window opens. This is the safety net — it catches the contact whose timezone you didn't have, or the send you fired off manually at 11 PM without thinking.
You want both. Timezone-shifted sending optimizes; the quiet-hours gate protects you from your own mistakes.
How Ready handles this
Ready enforces quiet hours automatically. Sends that would land outside permitted local hours are held based on the recipient's area and released when the window opens — you don't configure a rule per campaign, and you can't accidentally blast someone at 6 AM because the platform won't let the message through until 8. Combined with automatic STOP handling (an opt-out propagates across every campaign, so a customer who bailed after one badly-timed text never gets another), it removes the two most common ways a national blast turns into a complaint spike.
That said — honesty first — enforcement is only as good as the location data behind it. If you're capturing area from the phone number's area code, that's a decent proxy but not perfect; people keep numbers when they move. Where you can, capture the customer's actual timezone or ZIP at opt-in and let that drive scheduling. The platform gives you the guardrail; clean data makes it tighter.
And to be clear about the limit: quiet-hours enforcement reduces your TCPA exposure. It doesn't eliminate it. Consent is still the foundation — if the underlying opt-in is bad, perfect timing doesn't save you. Compliance is ultimately the sender's responsibility, and timing is one layer of several.
A practical setup checklist
If you run a national ecommerce list, here's the order I'd fix things in:
- Capture timezone or ZIP at opt-in, not just the number. Area-code inference is your fallback, not your primary.
- Schedule by local target time, not office time. "9 AM their time" beats "9 AM my time" on both compliance and open rate.
- Turn on quiet-hours enforcement as a hard gate so nothing slips through when data is missing.
- Tighten the window for strict states. If Florida and Oklahoma are meaningful chunks of your list, cap at 8 PM local rather than 9.
- Scrub before you send. Quiet hours protect timing; a litigator and DNC scrub protects you from the handful of numbers that turn a timing slip into a lawsuit. At $0.005 per contact, scrubbing 40,000 numbers costs $200 — one willful violation costs up to $1,500 by itself.
- Watch your 10DLC campaign health so an early-morning complaint spike doesn't quietly throttle your delivery. Our 10DLC for ecommerce guide covers what carriers actually monitor.
The takeaway
A single wall-clock send time can't be compliant across a national list — the math forces a third of your contacts into someone's quiet hours no matter which hour you pick. The fix isn't discipline about when you hit send; it's letting the platform schedule against each recipient's local time and hold anything that falls outside their window.
If you'd rather not build that logic yourself, Ready enforces quiet hours automatically and handles opt-outs across campaigns — you can see how it fits with the rest of the compliance stack over on the product page, or just start with 2,500 free credits and check your own list's timezone spread before your next blast. Pull up your last send's delivery timestamps first. The 6 AM ones will tell you whether you have this problem.