TCPA Calling Hours by State

Every calling-hours table on the internet has the same defect, and this one would too if it did not say so at the top: it tells you the rule for a state, and you do not know what state your prospect is in.

You know their area code. Area codes stopped predicting location when number portability arrived. A 313 number can ring in Phoenix. Your dialer suppresses calls based on a geography it inferred, and the inference is wrong often enough to matter.

So read the table, then read the section after it, because the second one is where compliance actually lives.

The federal rule, precisely

47 C.F.R. § 64.1200(c)(1) prohibits telephone solicitations to a residential subscriber before 8:00 a.m. or after 9:00 p.m. local time at the called party’s location. The rule text is on eCFR.

Three things about it that get misread:

”Local time at the called party’s location” — not your time, not the time in the state that issued the number. The recipient’s actual location, right now.

It applies to solicitations. Calls to an existing customer about an in-force policy are a different analysis. But “servicing” a customer while mentioning a new product is a solicitation, and the line is thinner than agents assume.

Federal is the floor, not the ceiling. Where a state is stricter, the state rule governs. Twenty-three of the fifty-one jurisdictions below are stricter than federal on at least one dimension.

All 51 jurisdictions

Voice calls, telemarketing. “Federal” in the window column means the jurisdiction has no state-specific calling-hours statute or rule, so § 64.1200(c)(1) supplies the window by default — that is twelve states, and it is a fact worth knowing because it means the answer is simply the federal rule rather than something you failed to find.

This table is a starting point for a conversation with counsel, not a compliance control. It covers the voice telemarketing window and the Sunday position only. It does not cover holiday bans, per-call disclosure timers, state licensing, do-not-call registration, call caps or SMS, each of which varies independently and several of which carry their own private right of action. See state mini-TCPA laws.

The exceptions worth knowing by name

Rhode Island — 9am to 6pm. The narrowest window in the country by a wide margin, and Sundays are banned. A nine-hour weekday window is a different business model, not a scheduling tweak.

Kentucky — 10am start. The latest start in the country.

Texas — Sunday is a noon start, not a ban. This one is routinely miscoded as a Sunday ban in commercial suppression lists. It is a restricted window, and treating it as a ban costs you every Sunday afternoon in your largest final expense market.

Illinois — two windows. The live-call window and the autodialer window differ. Suppression built on the permissive one is non-compliant for autodialed traffic, and this is the kind of distinction a single “state window” field cannot represent.

Alabama, Louisiana, Maine, Mississippi, Rhode Island, South Dakota, Utah — Sunday banned. Several also ban state holidays, and the operative holiday list is the state’s holidays, not the federal set. A dialer suppressing only federal holidays will place calls on banned days.

Pennsylvania changes on 19 October 2026. Diary it now.

Seven Sunday bans and one restricted Sunday. If your dialer has a single “Sunday: on/off” setting, it cannot express Texas correctly, and Texas is where a lot of final expense volume lives.

The timezone problem, which is the real one

Three distinct failures, in increasing order of how often they bite.

1. Multi-timezone states. Florida, Texas, Tennessee, Kentucky, Indiana, Michigan, Kansas, Nebraska, North Dakota, South Dakota, Oregon and Idaho are split across two zones. A state-level rule cannot tell you which one applies. Panhandle Florida is Central; Miami is Eastern. Calling “Florida at 8:15am Eastern” is 7:15am in Pensacola, and Florida ends at 8pm.

2. Portability. A number’s area code tells you where it was issued. People move and keep their numbers. Final expense prospects skew older and skew toward long tenure with the same number, which helps — but a meaningful fraction of any list is geographically misfiled, and the dialer has no way to know which.

3. DST desync. Arizona does not observe daylight saving. Neither does Hawaii, nor most of the US territories. For roughly eight months a year Arizona matches Pacific, and for four it matches Mountain. Suppression logic hardcoded to a UTC offset is wrong for a third of the year.

What actually protects you

Confirm location on the call. “Am I reaching you in Michigan?” is one sentence, takes two seconds, and it converts an inference into a record. Log the answer as a field. This is the single highest-value compliance practice in this entire section, and it costs nothing.

Set your operating window to the intersection, not the union. Running 9am–8pm local everywhere puts you inside every state window except Rhode Island and Kentucky’s start. You lose some dial hours. You lose fewer than you lose to one demand letter.

Suppress Sunday entirely unless you have per-state logic you have actually tested. Seven bans plus one restricted window is not a setting you want to get approximately right.

Use the recipient’s confirmed timezone, not the area code, once you have it. Before you have it, use the stricter of the two possibilities.

Log the timestamp of every call in UTC plus the recipient’s determined local time and how you determined it. Four years later, that log is either your defence or the plaintiff’s exhibit. Which one depends on whether it exists.

Related

Do bought leads count as TCPA consent — the consent question, which is separate from and prior to the timing question. State mini-TCPA laws — where private rights of action live. A2P 10DLC — the parallel regime for texts, which has its own timing considerations. TCPA demand letter — what to do when one arrives.

Nothing on this page is legal advice, and we are not a law firm. This section carries no product links, by policy, enforced by the build.