TCPA calling hours run from 8 a.m. to 9 p.m. in the called party's local time. The rule sits at 47 CFR § 64.1200(c)(1), which bars a telephone solicitation to a residential subscriber "before the hour of 8 a.m. or after 9 p.m." local time at the called party's location.
The trap is in the last four words, and it is a dialler configuration problem before it is a legal one.
Local time means theirs, not yours
A campaign dialling from Austin at 8:15 a.m. Central is calling California at 6:15 a.m. Pacific. That is a violation on every Pacific number in the list, generated by a dialler that was configured correctly for the office it sits in.
The area code is not a reliable proxy either. Numbers are portable, and a 212 number may belong to someone living in Denver. Diallers that window on area code alone are approximating the rule, not following it — which is usually fine until the one call that is not.
What the window applies to
The restriction covers telephone solicitations — calls made to encourage the purchase of goods or services. It does not cover every call.
Calls to someone with an established business relationship, calls the recipient gave prior express invitation for, and calls that are not solicitations at all — service updates, appointment reminders, delivery notifications, collections on an existing debt — sit outside this particular provision.
That is a narrower carve-out than it sounds. Whether a "courtesy check-in" is a solicitation depends on what it actually does, not what the campaign is called internally. And other parts of the TCPA still apply even when the calling-hours rule does not.
State rules are stricter, and they stack
Federal calling hours are a floor. Several states impose narrower windows and additional restrictions — a compliant 8 a.m. federal call can still violate state law.
The practical consequence is that a national campaign cannot run one window. It has to window per jurisdiction, which means resolving each number to a location and applying the strictest applicable rule, not the federal one.
Doing it in the dialler rather than the policy
Calling hours fail in configuration, not intention. Three things carry most of the risk:
Resolve location per number, not per area code. Where you have address data, use it. Where you do not, treat a ported number as an unknown rather than an assumption.
Window on the recipient's clock, and mind daylight saving. Two dates a year, a correct window becomes wrong for an hour in some states and not others.
Cover the retry queue. Compliant campaigns commonly breach on retries — a call queued at 8:45 p.m. that dials at 9:04 p.m. because the queue backed up. The window has to be checked at dial time, not at queue time.
The calling hours checker resolves the permitted window for a number. See also TCPA compliance for the wider set of obligations — consent, identification, and the do-not-call requirements this page does not cover.
This is not legal advice
This describes one provision. TCPA exposure is statutory and per-call, and the surrounding rules — consent, revocation, DNC registries, state law — are where most liability actually sits. Take advice on your programme rather than relying on a summary of a single subsection.
Frequently asked questions
What are the TCPA calling hours? 8 a.m. to 9 p.m. in the called party's local time, under 47 CFR § 64.1200(c)(1).
Whose time zone applies? The person being called. The caller's location and the dialler's location are irrelevant.
Do calling hours apply to appointment reminders? The provision covers telephone solicitations. A genuine reminder to an existing customer is generally not one, but other TCPA rules may still apply.
Can state law be stricter than 8 a.m. to 9 p.m.? Yes. Several states set narrower windows, and the stricter rule governs for that jurisdiction.
Does the window apply to the retry queue? Yes — compliance is judged at the moment the call is placed, so a retry that fires at 9:04 p.m. breaches even if it was queued inside the window.
