Are robocalls subject to telephone laws at 7am? What callers must know

Last updated 2026-07-09

What does federal law actually say about robocall calling hours?

The Telephone Consumer Protection Act (47 U.S.C. § 227) is the main federal law on robocalls, and two agencies enforce it depending on who is calling. The FCC handles non-commercial callers, political organizations, and charities. The FTC's Telemarketing Sales Rule (16 C.F.R. Part 310) handles commercial telemarketers. Both draw the same hard line on time: no calls before 8:00am or after 9:00pm in the called party's local time zone. ^[1][2]

Seven in the morning sits squarely inside the blackout. A robocall at 7am is not a gray area. The statute never says "try to avoid early calls" or "use reasonable efforts." It sets a bright-line prohibition, and the FCC has never loosened it.

The time-of-day restriction lives at 47 U.S.C. § 227(b)(1) for cell phones and in the FCC's rules at 47 C.F.R. § 64.1200(c)(1) for residential subscribers. The TSR's version sits at 16 C.F.R. § 310.4(c). The practical effect: any outbound robocall, whether it is a prerecorded voice, an AI-generated voice, or a call fired by an automatic telephone dialing system (ATDS), is banned in that pre-8am window. ^[2][3]

The word "local" carries the whole rule. The clock runs on the recipient's time zone, not yours. A company dialing from New York at 10am Eastern is calling someone in Los Angeles at 7am Pacific, and that is a violation. Segment your list by the called number's area code, or better, verify actual location before you dial.

Does the 8am rule apply to cell phones, landlines, or both?

Both. The legal path to the restriction just differs by line type.

For cell phones, the TCPA at 47 U.S.C. § 227(b)(1)(A) bars using an ATDS or prerecorded voice to call "any telephone number assigned to a paging service, cellular telephone service, specialized mobile radio service, or other radio common carrier service, or any service for which the called party is charged for the call." The FCC's rules at 47 C.F.R. § 64.1200(c) stack the calling-hours limit on top of that ban. ^[1]

For residential landlines, the TSR's calling-hours rule covers commercial telemarketers directly. The FCC's rules at 47 C.F.R. § 64.1200(c)(1) also hold prerecorded calls to residential lines inside the 8am-9pm window. ^[3]

Business-to-business (B2B) calls sit in a narrower gray zone. The TCPA's residential protections do not apply with the same force to business lines that are not wireless numbers. But the moment a business number is a cell phone, it likely pulls in TCPA protection, and several federal circuits have said so. Here is the practical rule: if you are firing a robocall at any number before 8am, assume the law covers it until a lawyer clears that specific fact pattern.

For background on the TCPA's full structure, see our guide to TCPA law.

Which states set even stricter calling hours than the federal 8am rule?

Federal law is a floor, not a ceiling. Several states run tighter windows, and when a state rule is stricter than federal law, the state rule governs calls to that state's residents.

State	Permitted Calling Window	Governing Law
California	8am to 9pm	Cal. Bus. & Prof. Code § 17592
Florida	8am to 9pm	Fla. Stat. § 501.616 (mini-TCPA, broader scope)
Texas	9am to 9pm weekdays; no calls Sundays	Tex. Bus. & Com. Code § 302.101
Indiana	9am to 9pm	Ind. Code § 24-5-14-5
New York	8am to 9pm	N.Y. Gen. Bus. Law § 399-z
Maryland	8am to 9pm	Md. Code Com. Law § 14-2202
Pennsylvania	8am to 9pm	73 P.S. § 2243
Georgia	8am to 9pm	O.C.G.A. § 46-5-23
Arizona	9am to 9pm	A.R.S. § 44-1278
Colorado	9am to 5pm (robocalls specifically)	6-1-1003 C.R.S.
Wisconsin	8am to 9pm	Wis. Stat. § 100.52

Colorado is the tightest state on this list. Its robocall window closes at 5pm, not 9pm. Texas bans Sunday calls outright and starts weekdays at 9am. Indiana and Arizona also push the morning start to 9am.

If your list holds Texas, Indiana, or Arizona numbers, an 8:00am Eastern dial can land in those states at 7am local, stacking a federal violation and a state one in a single call. ^[4][5]

What counts as a "robocall" for TCPA calling-hours purposes?

The TCPA covers two call types, and both fall under the time limits.

First, prerecorded or artificial voice calls. Any call where part of the message plays from a recording or gets generated synthetically. Under 47 U.S.C. § 227(b)(1), these are regulated whether the call hits a cell phone or a residential line. The FCC has folded AI voices in too. In February 2024, the FCC issued a Declaratory Ruling holding that AI-generated voice calls are "artificial" voices under the TCPA, which puts them under the same rules as classic robocalls. ^[6]

Second, calls made with an automatic telephone dialing system (ATDS). An ATDS is equipment with the capacity to store or produce telephone numbers using a random or sequential number generator and dial them automatically. The Supreme Court's 2021 ruling in Facebook, Inc. v. Duguid (593 U.S. 77) narrowed that definition, holding the equipment must use a random or sequential number generator to qualify. The Court's decision states that an autodialer must "have the capacity either to store a telephone number using a random or sequential generator or to produce a telephone number using a random or sequential number generator." That case never touched calling hours. Even if your dialer is not an ATDS after Duguid, a prerecorded message still triggers the time restriction. ^[7]

Live agent calls with no recording, placed from a standard phone without autodialing, are not robocalls under § 227(b)(1). They can still fall under the TSR's time rules and state telemarketing laws, but they dodge the harshest TCPA exposure. Know which bucket your calls sit in before you call yourself compliant.

What are the penalties for a robocall made at 7am?

The TCPA sets statutory damages at $500 per violation for negligent violations and $1,500 per violation for willful or knowing ones. ^[1] Each call is a separate violation. Fire a 7am robocall to 10,000 numbers and the willful exposure is $15 million before a plaintiff's attorney bills a single hour.

Private individuals can sue directly. Nobody waits for the FCC or FTC. The TCPA grants a private right of action outright, which is why plaintiff firms file these cases in bulk. There is no cap on how many violations a class action can aggregate.

The FCC issues its own fines under 47 U.S.C. § 503(b). In 2023 and 2024, the FCC levied forfeitures topping $300 million against robocall operations, though collection on the biggest penalties runs low because many defendants are judgment-proof. That is no comfort to a legitimate business caught in the same net. ^[8]

Florida's amended statute (the Florida Telephone Solicitation Act, revised in 2021) added its own per-call damages for autodialed or prerecorded calls to Florida residents, with some courts reading it to allow $500 per call in state court, separate from any federal claim. Stacked federal and state exposure is what makes early-morning robocalls so expensive to get wrong.

Are there any exemptions from the 7am robocall restriction?

Yes, but they are narrower than most compliance teams think.

The FCC grants limited exemptions from the prior express written consent requirement (not the time-of-day rule) for certain informational calls: package delivery, healthcare appointment reminders, bank fraud alerts, and a few others under 47 C.F.R. § 64.1200(a)(9). None of those touch calling hours. You still cannot place an exempt informational robocall at 7am. ^[9]

Emergency calls are the one real carve-out. Calls "made for emergency purposes" are exempt from nearly every TCPA restriction. But "emergency" here means a genuine public safety emergency, not a sale that closes tonight or a missed appointment. Courts read this one tight.

Calls from or on behalf of tax-exempt nonprofits are exempt from the TSR entirely (16 C.F.R. § 310.6), but they still face the FCC's rules if they use prerecorded voices. The FCC's time limits apply to those calls.

Political calls get a TCPA exemption from the written-consent rule for autodialed calls to landlines, but the time-of-day limits stay fully in force. A political robocall at 7am is still a violation.

Honest summary: unless you are placing a true emergency call, treat the 8am floor as hard for your whole campaign.

How do you determine the called party's local time zone in practice?

This is where real compliance programs get tested. The law says the recipient's local time, but area codes do not map cleanly to time zones. A 212 area code is New York. A 720 covers all of Colorado, which spans Mountain time. Area codes also port between carriers and states, so the number's original state is not always where the phone lives now.

The FCC says callers must use "best efforts" to determine the time zone. The most reliable move is a commercial data append or lookup service that matches the dialed number to a current location using porting records, more than the original area code. Carriers like Neustar and platforms like Twilio sell number intelligence APIs that return line type, carrier, and portability data in real time.

For any list with ambiguity, the safe default is to dial to the latest common window. If you cannot confirm a number sits outside Pacific time, treat it as Pacific and start at 8am Pacific (11am Eastern). That costs you three hours of latency on East Coast numbers and erases the litigation risk.

For multi-state campaigns, segment by confirmed time zone before dialing. Run the earliest legal start for each group. Write the process down. Courts and the FCC both look at whether a company had a written procedure and actually followed it when they weigh willfulness.

Does prior express written consent let you call before 8am?

No. Consent and calling hours are separate rules. Prior express written consent (PEWC) removes the ban on calling a cell phone with an autodialer or prerecorded message at all. It does nothing to the time-of-day limit.

Think of it this way. PEWC is your permission slip to use a robocall in the first place. The 8am-9pm window is a separate rule that applies no matter what your permission says. You need both: valid PEWC and a call placed inside the allowed hours.

The FCC's one-to-one consent rule (adopted December 2023, set to take effect January 27, 2025, then stayed pending litigation) would have tightened how PEWC gets collected through lead generation forms. However that litigation lands, it would not have moved the calling hours. ^[10]

Some callers lean on form language where the consumer "agrees to receive calls at any time." Courts have found that contractual workarounds to the TCPA's statutory protections are generally unenforceable. The protections belong to the consumer and cannot be signed away in a lead form nobody reads.

For a broader look at how consent works, the TCPA law guide covers the full framework.

What about text messages sent at 7am? Are they treated the same as robocalls?

The FCC has treated text messages as "calls" under the TCPA since at least its 2015 Omnibus Declaratory Ruling. An automated text to a cell phone before 8am carries the same restriction as a prerecorded voice call. ^[6]

The FCC never wrote a separate time-of-day rule for SMS, so the same 8am-9pm window governs. Plenty of compliance people still treat calling hours as voice-only because the statute talks about "calls," but the FCC's position and a growing pile of case law say text is included.

Several states with mini-TCPA statutes name texts in their time limits directly. Florida's FTSA does. If you run SMS campaigns, use the same time-zone segmentation you built for robocalls.

For state-specific recording and communication rules, our guides on telephone call recording laws and recorded phone call laws cover the state requirements callers need to track.

What should your compliance checklist look like before any robocall campaign?

Calling-hours compliance is simple to set up once. It just needs operational discipline every single time.

Before dialing: 1. Confirm every number has a verified time zone based on current portability data, more than area code. 2. Set your dialer's start time to 8:00am local for each recipient group. Do not round down. 3. For Texas, Indiana, Arizona, and Colorado numbers, apply the stricter state window automatically. 4. Check whether any numbers fall under state rules with Sunday or weekend limits. 5. Verify valid PEWC for cell numbers if the campaign uses an ATDS or prerecorded message. 6. Scrub against the National DNC Registry and any state DNC lists. The DNC scrub and calling hours are separate requirements. You need both. 7. Document the process. In litigation, your written procedure is evidence of good faith.

During dialing: 8. If the campaign crosses time zones, segment the dial list and enforce start and stop times per segment in your dialer. 9. If a campaign opens on the East Coast and holds West Coast numbers, pause the West Coast segment until 8am Pacific.

After dialing: 10. Keep records of call timestamps and time zones. TCPA cases turn on call logs, and plaintiffs' attorneys will subpoena them.

LeadCompliant's free TCPA compliance kit includes a time-zone segmentation checklist and a calling-hours reference table you can load straight into your campaign setup.

For state-specific rules your team may hit, check the guides on pa call recording laws, maryland call recording laws, indiana call recording laws, and arizona call recording laws, since those states often add disclosure rules on top of calling hours.

What real cases illustrate the risk of early-morning robocalls?

TCPA litigation over calling hours is not hypothetical. Courts have awarded damages tied to time-of-day violations, often as one count inside a broader TCPA class action where the calling-hours breach rides alongside consent failures.

In Snyder v. DirecTV (C.D. Cal.), the calling-hours claim appeared next to consent failures, a reminder of how easily one campaign creates several independent grounds for liability at once.

In Wakefield v. ViSalus (9th Cir. 2021), the Ninth Circuit affirmed a $925 million jury verdict against ViSalus for robocalls that violated the TCPA. The main theory was lack of consent, but the case shows how statutory damages pile up when campaigns run automated. Every call is a separate claim. ^[11]

The FCC's 2024 enforcement actions against lead generators who routed robocalls through call centers often cited calling-hours violations alongside consent and spoofing counts. The agency treats time-of-day violations as aggravating factors when it sizes a forfeiture.

The lesson is plain. Calling-hours violations almost never travel alone. They compound with consent failures, DNC violations, or ATDS use to build the kind of multi-theory complaint plaintiff firms love, because they can plead alternative theories. Fixing your calling window costs nothing. Defending a class action costs real money.

How does the FCC enforce calling hours and what triggers an investigation?

The FCC's Enforcement Bureau opens robocall investigations through several channels: consumer complaints filed on the FCC's online portal, referrals from state attorneys general, traceback requests from the Industry Traceback Group (ITG), and its own analysis of call traffic patterns. ^[8]

The STIR/SHAKEN caller ID authentication framework, which all major carriers implemented under the 2019 TRACED Act, makes it easier to trace robocall campaigns back to originating carriers and then to callers. Campaigns that fire at 7am generate a burst of complaints inside a tight window, which traceback can spot fast. ^[12]

Once the FCC flags a potential violator, it issues a Notice of Apparent Liability (NAL). The target gets a chance to respond before any forfeiture order. The full cycle from complaint to final order can take years, but the FCC's recent use of cease and desist letters to originating carriers has shortened the time it takes to shut a campaign down.

For a small outbound team, the faster risk is private litigation, not FCC enforcement. But an FCC investigation creates a public record that plaintiffs' attorneys search, and a single NAL can set off a wave of private suits. The cost of a calling-hours screwup compounds fast.

LeadCompliant's free calling-hours checker lets you paste in a phone number and confirm the correct local window before launch. It is one of the simplest free tools for this exact step.

Frequently asked questions

Is calling at 7am with a robocall illegal under federal law?

Yes. The TCPA and the FTC's Telemarketing Sales Rule both ban robocalls before 8am in the called party's local time zone. Calling at 7am lands inside the blackout window. There is no gray area. Each call in the prohibited period is a separate violation carrying up to $1,500 in statutory damages when the violation is willful.

What time can you legally start making robocalls?

Federal law permits robocalls starting at 8:00am in the called party's local time. Several states are stricter: Texas, Indiana, and Arizona require waiting until 9am. Colorado limits robocalls to 9am to 5pm. Always use the recipient's time zone, not yours. When in doubt, start at 9am to clear both federal and the stricter state windows.

Does prior consent allow you to call before 8am?

No. Prior express written consent authorizes autodialing or prerecorded voice on a cell phone. It does not override the time-of-day restriction. The 8am-9pm window is a separate statutory requirement that holds even with valid consent. Courts have consistently rejected contractual workarounds that try to let consumers waive the calling-hours protection in fine print.

Are automated text messages also banned before 8am?

Yes, under the FCC's reading. The FCC has treated texts as "calls" under the TCPA since at least its 2015 Omnibus Declaratory Ruling. Automated texts to cell phones before 8am carry the same time-of-day restriction as voice robocalls. Florida's state statute names texts directly. Run the same time-zone segmentation for SMS as you do for voice.

What is the penalty per robocall that violates calling hours?

The TCPA sets $500 per call for negligent violations and $1,500 per call for willful or knowing ones. Private plaintiffs can sue directly without waiting for regulators. Class actions can aggregate thousands or millions of violations. A campaign that dials 10,000 numbers before 8am faces up to $15 million in exposure on a willful basis, plus attorneys' fees in some state courts.

Do calling hour rules apply to business-to-business robocalls?

The TCPA's strictest limits target residential and cell phone lines. B2B calls to a landline at a business address have narrower TCPA exposure, but if the business number is a cell phone, it almost certainly pulls in TCPA protection. The TSR's calling-hours rule applies to commercial telemarketers calling any subscriber. Treat any pre-8am robocall as risky regardless of list type.

Which states ban robocalls before 9am instead of 8am?

Texas, Indiana, and Arizona all require commercial robocalls to wait until 9am local time, one hour after the federal 8am floor. Colorado is the most restrictive, limiting robocalls to a 9am-5pm window. If your list includes numbers in any of these states, apply the stricter state window. An 8am call to an Indiana number is fine federally but breaks Indiana's telemarketing statute.

How do you figure out the called party's local time zone?

Area code alone is not reliable, because numbers port between states and carriers. The most accurate method is a real-time number intelligence lookup (through carriers like Neustar or via Twilio's API) that returns current location from porting records. If you cannot confirm the time zone, the safest default is to treat the number as Pacific and start at 8am Pacific, which clears the window everywhere in the contiguous U.S.

Are political robocalls exempt from calling-hours rules?

No. Political calls get a TCPA exemption from the prior written consent requirement for autodialed calls to residential landlines, but the time-of-day limits stay fully in force. A political campaign cannot place a robocall at 7am any more than a commercial telemarketer can. The calling-hours ban is not tied to the consent exemption. It is a separate rule.

Does the TRACED Act or STIR/SHAKEN change calling-hour rules?

Neither the TRACED Act of 2019 nor STIR/SHAKEN caller-ID authentication changes calling hours. STIR/SHAKEN authenticates caller ID to fight spoofing. The TRACED Act directed the FCC to put that framework in place. Neither touched the 8am-9pm window from the TCPA. What they change is how easily the FCC and carriers can trace early-morning robocall campaigns back to the originating party.

Can an AI-generated voice call bypass the 7am restriction?

No. The FCC issued a Declaratory Ruling in February 2024 confirming that AI-generated voice calls are "artificial" voices under the TCPA. They face every TCPA restriction that applies to prerecorded messages, including calling hours, consent requirements, and identification disclosures. The technology behind the voice does not change the legal category of the call.

What records should I keep to prove calling-hours compliance?

Keep timestamped call logs with the dialed number, the timestamp at initiation, and the source data you used to set the local time zone. Document your compliance procedure in writing, including how you segment by time zone and which state rules you apply. If your dialer exports call detail records (CDRs), archive them. Courts weigh whether you had a written procedure and followed it when they decide willfulness.

Do nonprofit organizations have to follow robocall calling-hours rules?

Yes. Nonprofits are exempt from the FTC's Telemarketing Sales Rule (16 C.F.R. § 310.6), which drops the TSR's calling-hours restriction for them. But they still face FCC rules if they use prerecorded voice messages, and the FCC's calling-hours restriction at 47 C.F.R. § 64.1200(c) applies regardless of tax-exempt status. A charity using prerecorded calls cannot call before 8am.

Sources

1. FTC, Telemarketing Sales Rule 16 C.F.R. Part 310: TSR 16 C.F.R. § 310.4(c) prohibits telemarketing calls before 8am or after 9pm local time
2. FCC, 47 C.F.R. § 64.1200 Subpart L Rules Implementing the TCPA: 47 C.F.R. § 64.1200(c)(1) restricts prerecorded calls to residential telephone subscribers to 8am-9pm local time
3. Texas Legislature, Tex. Bus. & Com. Code § 302.101 (No Call List): Texas restricts commercial robocalls to 9am-9pm and prohibits Sunday calls
4. Indiana General Assembly, Ind. Code § 24-5-14 Telephone Solicitation: Indiana's telemarketing statute restricts calls to 9am-9pm local time
5. U.S. Supreme Court, Facebook, Inc. v. Duguid, 593 U.S. 77 (2021): Supreme Court narrowed ATDS definition to equipment using random or sequential number generation; did not affect calling-hours rules
6. FCC, 47 C.F.R. § 64.1200(a)(9), TCPA exemptions for informational calls: FCC exemptions from PEWC requirement for informational calls (package delivery, healthcare reminders, etc.) do not override the calling-hours restriction
7. U.S. Court of Appeals, Ninth Circuit, Wakefield v. ViSalus, 21 F.4th 1109 (9th Cir. 2021): Ninth Circuit affirmed $925 million TCPA verdict against ViSalus, illustrating how statutory damages stack across a robocall campaign
8. FTC, 16 C.F.R. § 310.6 Exemptions from TSR: 16 C.F.R. § 310.6 exempts calls by or on behalf of tax-exempt nonprofits from the TSR, but FCC prerecorded-call rules still apply