Calling-hours violations are among the most common TCPA mistakes, and they are rarely deliberate. A rep in Atlanta starts dialing at 8:15 AM. The list includes a Seattle prospect, so the call lands at 5:15 AM. The rule allows 8 AM to 9 PM in the recipient's local time, not the caller's, and a handful of states shorten that window further, ban Sundays, or cap how many times you can call.

This post covers the federal rule, the states that are stricter, how to decide which time zone a number belongs to, and how to build a calling block that stays inside the window without rechecking the clock before every dial. It is a practical summary, not legal advice. State laws change, and several were amended in the last few years, so confirm the current statute with counsel before you set policy.

The federal rule: 8 AM to 9 PM, recipient's local time

Under the TCPA rules (47 CFR 64.1200(c)(1)), you may not make a telephone solicitation before 8 AM or after 9 PM, measured at the called party's location. Three details matter:

  • It's the recipient's clock. Your office time zone is irrelevant.
  • It covers solicitations. Calls to people who have an established business relationship with you, or who gave prior express invitation or permission, are treated differently under the federal definition. Many state laws define the term more broadly, so don't rely on that exemption without checking the state.
  • The exposure is per call. The TCPA's private right of action for these rules generally applies once an entity makes more than one violating call to the same person within 12 months. Damages are up to $500 per violation and up to $1,500 if a court finds the violation willful. One early dial is a mistake. A daily 8:00 AM Eastern start against a national list repeats that mistake hundreds of times.

States with stricter windows

The table lists commonly cited state rules for telephone solicitations. It is a starting point for your own review, not a complete legal survey. Several of these laws also include exemptions, registration requirements or consent rules that this table leaves out.

StatePermitted hours (recipient local)Other limits often cited
Federal baseline8 AM to 9 PMNone
Florida8 AM to 8 PMMax 3 calls per 24 hours on the same subject
Oklahoma8 AM to 8 PMMax 3 calls per 24 hours on the same subject
Maryland8 AM to 8 PMMax 3 calls per 24 hours on the same subject
Washington8 AM to 8 PMNone
Massachusetts8 AM to 8 PMNone
Connecticut9 AM to 8 PMNone
Texas9 AM to 9 PM Mon to SatSunday noon to 9 PM
Pennsylvania8 AM to 9 PM Mon to SatSunday 1:30 PM to 9 PM
Kentucky10 AM to 9 PMNone
Louisiana8 AM to 8 PMNo Sundays or state holidays
Mississippi8 AM to 8 PMNo Sundays
Utah8 AM to 9 PMNo Sundays or legal holidays
Rhode Island9 AM to 6 PM weekdays10 AM to 5 PM Saturday; no Sundays or holidays

The table shows that "8 to 9" is only the ceiling. Some states end at 8 PM, some start at 9 or 10 AM, and some ban Sundays entirely. The 3-calls-in-24-hours caps in Florida, Oklahoma and Maryland also affect multi-touch cadences, where reps often double-dial a hot lead on the same day.

Which number decides "local time"

The rule refers to the recipient's location, but your dialer only sees a phone number. The area code is a weak indicator:

  • Mobile numbers move with their owners. A 212 number might belong to someone who has lived in Denver for six years.
  • Ported numbers keep their original area code after the carrier changes.
  • Your CRM may hold a mailing address that conflicts with the area code.

The safest approach is to check both signals and apply the stricter window. If the area code says Eastern and the address says Pacific, call only when it is legal in both places, which in practice means following the later start and the earlier end. If you have no address, use the area code, but don't assume it is accurate.

The same logic applies to state rules. If the number has a Florida area code and the address is in Georgia, the conservative choice is to apply Florida's 8 PM cutoff and three-call cap.

The time zone traps

These are the cases that most often break a hand-built schedule:

  1. Split states. The Florida panhandle west of the Apalachicola River is on Central time. El Paso is on Mountain, not Central. Indiana, Kentucky, Tennessee, Michigan, Kansas, Nebraska, the Dakotas, Oregon and Idaho all span two zones. A state-level lookup is not precise enough for these.
  2. Arizona. Most of the state does not observe daylight saving time, so in summer it matches Pacific and in winter it matches Mountain. The Navajo Nation does observe DST.
  3. Hawaii and Alaska. At 11 AM Eastern, it is 6 AM in Hawaii during US daylight time and 5 AM during standard time. Put these numbers in their own block.
  4. The DST switch weekends. A schedule that hard-codes UTC offsets will be wrong by an hour for a few weeks each year. Use a proper time zone database, not fixed offsets.
  5. Holidays. Louisiana, Utah and Rhode Island exclude holidays. Your calling calendar needs these dates entered, or reps will dial on them.

Building the guardrail into a dialer campaign

The simplest approach is to pick one conservative default that covers most states, then add exceptions only where they are needed.

A worked default (example, not legal advice): call 9 AM to 8 PM recipient local, Monday to Saturday, no Sundays, no federal holidays. Based on the table above, that default satisfies every state listed except:

  • Kentucky (start at 10 AM)
  • Rhode Island (end at 6 PM weekdays, 10 AM to 5 PM Saturday, no holidays)
  • Louisiana and Utah (add state holidays)

It also keeps you under Texas's later start and Connecticut's 8 PM end. Handle the three-call cap separately, as a per-contact counter, because it is not a clock rule.

How much shared time that leaves. For the contiguous US, 9 AM Pacific is noon Eastern, and 8 PM Eastern is the Eastern cutoff. So every contiguous time zone is open from noon to 8 PM Eastern, which is 8 shared hours. Before noon Eastern, call only Eastern and Central contacts. After 8 PM Eastern, only Mountain and Pacific contacts are still callable. Most teams build their calling blocks around those boundaries.

The operational steps:

  1. Tag every contact with a resolved time zone and state at import, using address first and area code second, and store both.
  2. Split lists into blocks by zone: Eastern morning, everyone midday, West Coast evening, and Hawaii/Alaska in a separate block.
  3. Encode state exceptions (Kentucky, Rhode Island, holiday states) as filters on those blocks.
  4. Count attempts per contact per 24 hours for Florida, Oklahoma and Maryland numbers, and stop at three.
  5. Log the local time of each call. If a call is challenged, a record showing the recipient's local time is much more useful than one showing only your office's time.

Scheduling calls this way does not raise your call costs. On the Ready Dialer, calls are billed at $0.025/min for answered time only, with each started minute billed as a full minute. For example, a rep who dials 60 numbers in an hour, gets 15 answers averaging 4 minutes, and hears 45 ring-outs or busy signals pays 15 × 4 × $0.025 = $1.50. The 45 unanswered calls cost nothing. (A call answered by voicemail counts as answered and is billed.) Moving those 60 dials into the correct local window leaves the bill unchanged.

Calls vs texts: the same clock, different enforcement

Plaintiffs have also brought quiet-hours claims over text messages, so the calling-hours window should be treated as applying to SMS too.

For texts, Ready enforces quiet hours in the platform, but only these windows: it holds a send outside 8 AM to 9 PM in the recipient's local time, sends to Florida and Oklahoma area codes outside 8 AM to 8 PM, and sends to Connecticut area codes outside 9 AM to 8 PM. A held send goes out later, and you are charged only when it actually sends. Ready does not hold texts to the other states in the table above, such as Kentucky, Rhode Island or Maryland, so schedule texts to those numbers inside their window yourself. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.

The Ready Dialer works differently. It is click-to-call from the dial pad, in the dashboard or inside GoHighLevel, with consented recording, transcripts, inbound calls that ring the open pad, and a Missed call card in the Inbox thread for each call you miss. It does no auto dialing, so a person starts every call. The dialer refuses a call outside calling hours in the contact's local time, using the same windows as texts: 8 AM to 9 PM, Florida and Oklahoma area codes 8 AM to 8 PM, and Connecticut area codes 9 AM to 8 PM. It also refuses a fourth call within 24 hours to the same person in Florida, Maryland or Oklahoma. It does not apply the other state windows in the table above, so the time zone tagging and block scheduling above are still your enforcement for those states.

If you are comparing dialer types and how they affect compliance, our notes on multi-line and triple-line dialers for cold calling cover the separate auto-dialing rules.

Where calling hours sit next to DNC and consent

Calling hours are one of several checks a call has to pass. A call made at 2 PM local can still violate the TCPA if the number is on the National DNC Registry, on your internal do-not-call list, or belongs to someone who never agreed to be contacted the way you are contacting them. Those are three separate lists that compliance teams often confuse.

A reasonable order of checks before a list reaches reps:

  • Scrub for DNC and known litigators. Ready's standalone TCPA & DNC Litigator Scrub costs $0.005 per contact, and you pay only for the contacts you scrub. Here's how litigator scrubbing works.
  • Confirm the basis for contact. For texting, that means consent, and the plain-English overview of SMS laws covers what is required.
  • Resolve time zone and state, then assign the contact to a calling block.

None of these steps eliminates TCPA risk, and compliance remains the sender's responsibility. Each one removes a common cause of claims.

The takeaway

The federal window is 8 AM to 9 PM in the recipient's local time. Several states are stricter: 8 PM cutoffs, later starts, Sunday and holiday bans, and three-call daily caps. A 9 AM to 8 PM, Monday-to-Saturday default with a few state exceptions covers most of the country, and from noon to 8 PM Eastern every contiguous zone is open. Tag each contact's zone at import, schedule calls in blocks, and log local call times.

If you want text quiet hours enforced automatically and a click-to-call pad in the same inbox, you can start with Ready. The first 20 one-to-one texts are free, and the Dialer is $0.025/min for answered time only.