The Moment a Callbot Dials, Calling-Hours Rules Dial Too

The FTC's Telemarketing Sales Rule (16 CFR 310.4) and the FCC's TCPA rule (47 CFR 64.1200) restrict solicitation calls to between 8:00 a.m. and 9:00 p.m. in the recipient's local time. The window applies the same way whether the channel is a text message or a voice call, and a TCPA violation carries civil liability consumers can bring themselves — a minimum of $500 per call, up to $1,500 for a willful violation. Build a dialer without a gate that enforces this window against the recipient's actual local time, rather than against the campaign's own schedule, and violations scale in lockstep with automation volume.

An Area Code Tells You Where a Number Was Born, Not Where It Lives Now

The most common mistake in calling-hours logic is treating the recipient's area code (NPA) as a stand-in for time zone. Twilio's Compliance Toolkit documentation states that its default behavior infers time zone from the phone number's area code, while recommending a ZIP code registered through the Contact API as the more accurate alternative. An area code only marks where a number was first issued, and that gap widens further in split-NPA regions where a single area code spans more than one time zone. Bake that area-code assumption into a campaign as a fixed value, and the moment a subscriber moves or ports their number, the dialer keeps calling straight into a violation.

State Rules Stack a Second Layer on Top of the Federal Floor

The federal window is a floor, not a ceiling — several states require a narrower one. Twilio's Compliance Toolkit changelog announced a release covering state-specific quiet-hours restrictions in ten states: Alabama, Connecticut, Florida, Louisiana, Maryland, Mississippi, Oklahoma, Tennessee, Texas, and Washington. Connecticut's blackout window runs 8:00 p.m. to 9:00 a.m., and Florida's runs 8:00 p.m. to 8:00 a.m. A gate that only clears the federal window is, by itself, a violation in any of these ten states.

From Design to Operations: A Calling-Hours Gate Checklist

Pin the target metrics in numbers before writing the gate. Set calling-hours determination accuracy — calls cleared against both federal and state rules — at 99.9% or higher, and cap the share of calls held or rescheduled due to a determination failure at 2% or less. Target 100% coverage for logging the basis of each determination, since without that record there is no way to show, after a lawsuit is filed, exactly why a given call was allowed to go out.

One failure path is the area-code limitation described above: in a split-NPA region, an area-code-only estimate lets calls through a window that is actually closed. The recovery is to maintain a separate list of split area codes, force a ZIP-code lookup for any number on that list, and fall back to the earlier of the two closing times as a conservative default when the lookup fails.

A second failure path is a stale state-override list. The ten-state list keeps growing rather than staying fixed, so hardcoding it into campaign configuration means a newly added state still only gets the federal window applied. The fix is to pull the state-override list into a configuration file separate from campaign logic, and expose that file's last-sync timestamp in the deploy pipeline.

Pre-deploy scenario tests need boundary timestamps built in: 7:59 a.m. and 8:00 a.m., 8:59 p.m. and 9:00 p.m. local time, run minute by minute across both edges of the window, plus dedicated cases for split-NPA numbers and state-override numbers.

Keep three fields on every outbound call log — local receive time, the time-zone source used for the determination, and pass/fail — and mask the recipient's number itself separately from call content. Those fields are what let you reconstruct, after an incident, exactly why a given call cleared the gate.

Review weekly the share of calls held or rescheduled, and how many of those traced back to a split-NPA miss or a stale state list. Any state crossing the 2% threshold moves to the front of the queue for mandatory ZIP-code lookups, and the state list itself should sync at least monthly, with its change history kept separate from campaign-logic changes.

Three Things to Check Right Now

Calling-hours compliance is two layers, not one — a federal window plus state overrides — and an area code alone can't guarantee the recipient's actual time zone. Pin determination accuracy at 99.9% and the held/rescheduled rate at 2% or under, keep split-NPA and state-override lists in configuration separate from campaign logic with a visible sync history, and violation counts stop scaling in lockstep with dialer volume.

References

Compliance Toolkit for Programmable Messaging — Twilio Docs

Compliance Toolkit now supports state-specific quiet hours in the United States — Twilio Changelog

Ask AI about this article

The assistant has read this article. Ask anything — it answers from the text and says so when something isn't in it.

Loading the chat…