Opt-Outs and Quiet Hours, Done Right
Updated June 17, 2026
Opt-out management means STOP requests are honored instantly, permanently, and automatically — with a timestamped record proving it. Quiet hours mean no texts before 8am or after 9pm in the recipient's local time zone. Both are TCPA and carrier requirements, both fail silently when left to humans, and both are why serious SMS runs on a system that enforces them rather than a person who has to remember.
Opt-outs and quiet hours are the two compliance items most likely to bite you, precisely because they're boring and easy to assume you've handled. A missed STOP and a 7am text in the wrong time zone don't feel like crises when they happen — they feel like nothing, until a complaint or a claim arrives.
The good news is that both are mechanical, not judgment calls. Get the system right once and they take care of themselves. Get them wrong and you're relying on a human to never slip, at volume, which never holds.
Opt-outs: instant, permanent, provable
When someone texts STOP (and common variants), the messaging has to halt immediately and stay halted — not after the next scheduled send, not once someone gets around to it. The opt-out must persist across campaigns too; a person who opted out of one shouldn't resurface on the next list. And you need a timestamped record of the opt-out, because honoring a request only protects you if you can show you honored it.
The failure mode is always the same: opt-outs handled by a human get missed. Someone replies STOP at midnight, the next drip touch is already scheduled, and it fires before anyone processes the request. Automatic suppression at the sending layer is the only version of opt-out handling that survives real volume.
Quiet hours: their time zone, not yours
The general standard is no marketing texts before 8am or after 9pm in the recipient's local time zone. The word that trips people up is 'their' — you need each recipient's time zone, not your own, which means a send scheduled at a perfectly reasonable 9am for you can be a violation at 6am for someone two zones west.
This is why time-zone-aware send windows matter more than a global schedule. A single national campaign sent at one clock time will violate quiet hours for a chunk of the list unless the system staggers sends by each recipient's local time. Scheduling by your own clock is one of the most common and most avoidable SMS violations.
| Rule | Requirement | Common failure | Reliable fix |
|---|---|---|---|
| Opt-out | Halt instantly + permanently on STOP | STOP missed before next scheduled send | Automatic suppression at send layer |
| Opt-out record | Prove you honored it | No timestamped log kept | Auto-logged opt-out with timestamp |
| Quiet hours | No texts 9pm–8am local | Scheduled by sender's time zone | Time-zone-aware send windows |
| Cross-campaign | Opt-out persists across lists | Opted-out lead reappears on new list | Global suppression list |
The two silent-failure rules and how to enforce them
Making both automatic
Compliance that depends on a person remembering fails the first busy week. Opt-outs honored by hand get missed, quiet hours respected manually get violated when someone schedules in the wrong zone, and opt-out records kept in a spreadsheet get lost. Each rule has to be a property of the system, enforced whether or not anyone is paying attention.
That's the design principle behind running SMS on managed infrastructure. BILT processes STOP automatically and permanently, suppresses opted-out contacts across every campaign, logs the opt-out with a timestamp, and staggers sends to each recipient's local time so quiet hours hold by default. Compliance you can't forget is the only kind that survives contact with real volume.
Frequently asked
What has to happen when someone texts STOP?
Messaging must stop immediately and permanently, the opt-out must persist across all your campaigns, and you should keep a timestamped record that you honored it. Relying on a human to process STOP is how violations happen — by the time someone sees it, the next scheduled text has often already fired. Automatic suppression is the only reliable approach.
What are the SMS quiet hours?
Generally no marketing texts before 8am or after 9pm in the recipient's local time zone. The critical detail is that it's their time zone, not yours, so your system needs each recipient's location to schedule compliantly. A campaign sent at one clock time nationwide will violate quiet hours for part of the list unless sends are staggered by local time.
Do opt-outs carry across different campaigns?
They should. Someone who opts out of one campaign shouldn't reappear on the next list — a persistent, global suppression list is the safe practice. Treating opt-outs as per-campaign is a common way opted-out contacts get re-texted, which both annoys recipients and exposes you to the per-message penalties under the TCPA.
Why automate opt-outs and quiet hours instead of handling them manually?
Because both fail silently when a human is responsible. A missed STOP or a wrong-time-zone send doesn't announce itself — it surfaces as a complaint or a claim later. Making each rule a property of the sending system means it holds at volume regardless of who's watching, which is the only version that survives a real campaign.
The takeaway
Opt-outs and quiet hours are the two SMS rules most likely to bite, precisely because they fail silently. Honor STOP instantly, permanently, across all campaigns, with a timestamped record; send only between 8am and 9pm in each recipient's local time. Both are mechanical, not judgment calls — make them automatic in the system, because compliance that depends on remembering doesn't survive volume.