Last updated 2026-07-09

TL;DR
Under 47 U.S.C. § 227 and FCC rules, you cannot make telemarketing calls or send marketing texts before 8:00 AM or after 9:00 PM in the called party's local time zone. Several states set tighter windows. Each violation costs $500 to $1,500. Time zone detection at the moment of contact, not batch scheduling, is the only safe way to run it.
What are TCPA quiet hours and where do they come from?
TCPA quiet hours are the federal time window outside of which you cannot legally make telemarketing calls or send marketing texts to people in the United States. The rule sits in 47 C.F.R. § 64.1200(c)(1), which implements the Telephone Consumer Protection Act at 47 U.S.C. § 227 [1][6]. The window is simple: 8:00 AM to 9:00 PM, local time at the called party's location. Everything outside that is off limits.
The FCC set these hours with the original TCPA rules in 1992. They have not changed at the federal level since. That makes quiet hours one of the few stable corners of a law that shifts every couple of years.
The phrase that trips people up is "local time." The rule does not care what time it is at your call center. It cares what time it is where the phone rings. A 7:45 AM call from an Eastern office to someone in California breaks the rule, even though it's 10:45 AM where your agent sits. The recipient's time zone controls. Always.
The statute treats calls to residential landlines and calls using an automatic telephone dialing system (ATDS) or prerecorded voice to any number, cell phones included, as covered contact [6]. So for any outbound team running a dialer, an autodialer, or an SMS platform, quiet hours apply to every attempt no matter the technology behind it.
What exact times does TCPA prohibit calls and texts?
The federal rule at 47 C.F.R. § 64.1200(c)(1) bans telephone solicitations before 8:00 AM or after 9:00 PM, local time at the called party's location [1]. Here's the whole thing in one table.
| Time at recipient's location | Federal TCPA status |
|---|---|
| Before 8:00 AM | Prohibited |
| 8:00 AM to 9:00 PM | Permitted (subject to other rules) |
| After 9:00 PM | Prohibited |
| Exactly 9:00 PM | Permitted (the ban starts after 9 PM) |
The 8:00 AM start is inclusive. A call at 8:00:00 AM is fine. A call at 7:59:59 AM is a violation. Same logic on the back end: 9:00 PM is still inside the window, 9:01 PM is not.
Text messages sent through an ATDS get treated the same as calls. The FCC has said so since its 2003 order and reaffirmed it in later rulings [2]. So the 8 AM to 9 PM window covers outbound marketing texts too. The CTIA, which sets carrier-level standards for messaging, recommends a tighter 8:00 AM to 8:00 PM window in its best practices, partly because carriers filter traffic that looks like it's ignoring quiet hours [3].
Two things people forget. These windows apply to your outbound contact, not to a consumer texting you back at midnight. And they apply on holidays and weekends. There is no carveout for "it's Saturday morning and everybody's up anyway."
Which states have stricter quiet hours than federal TCPA?
This is where outbound teams get burned. Federal law is a floor, not a ceiling. States set tighter windows, and the state rule often decides your real exposure because a plaintiff can stack a state claim on top of the federal one [4].
| State | Call time restriction | Source |
|---|---|---|
| California | 8:00 AM to 9:00 PM (matches federal, plus CCPA and CPUC constraints) | Cal. Bus. & Prof. Code § 17592 |
| Florida | 8:00 AM to 9:00 PM for state DNC; FTSA adds rules for texts | Fla. Stat. § 501.059 |
| New York | 8:00 AM to 9:00 PM for general solicitation | N.Y. Gen. Bus. Law § 399-z |
| Texas | 9:00 AM to 9:00 PM | Tex. Bus. & Com. Code § 302.101 |
| Indiana | 9:00 AM to 9:00 PM | Ind. Code § 24-4.7 |
| Colorado | 9:00 AM to 9:00 PM | Colo. Rev. Stat. § 6-1-303 |
| Wisconsin | 8:00 AM to 9:00 PM | Wis. Stat. § 100.52 |
| Massachusetts | 8:00 AM to 8:00 PM | Mass. Gen. Laws ch. 159C |
| Maryland | 8:00 AM to 9:00 PM (no calls Sunday before 1:00 PM) | Md. Code Ann., Com. Law § 14-3201 |
State telemarketing statutes across all 50 states are a patchwork, and plenty of them carry private rights of action with statutory damages that match TCPA. Texas and Indiana both cut off the morning at 9:00 AM, so an 8:15 AM call that's legal under federal law is illegal there [9]. Massachusetts closes at 8:00 PM [10]. Call nationally and one window covers you: 9:00 AM to 8:00 PM, recipient local time. That satisfies the strictest combination of current state rules [4].
The NCSL telemarketing law tracker is a decent starting point for the full picture, though it can trail amendments by months. Verify against the actual statute before you rely on it.
How do you determine the called party's local time zone?
The FCC rule says local time at the "called party's location." It does not tell you how to figure that out. The burden falls on you, the caller, to get it right [1]. This is the part nobody enjoys, because it's operationally annoying.
The standard method uses the area code and NPA-NXX (the first six digits of the number) to look up the associated time zone through a number portability service or a real-time API. Most commercial dialers and SMS platforms build this in. If yours doesn't, that's a gap to close before you send the next batch.
Then there's number portability. Someone can carry a 212 (New York) area code and live in Phoenix. An area-code-only lookup returns Eastern time, but the recipient is on Mountain time, and Arizona skips daylight saving time, which adds another wrinkle. The safer play is a real-time carrier lookup that returns line type and ported state alongside the geography, then apply the most conservative reading when the data is fuzzy.
For SMS, some platforms capture the opt-in timestamp and IP address at consent, which gives you a cleaner location signal. Worth doing if your platform supports it.
Nobody has perfectly clean data here. The FCC's guidance is that callers should make "good faith" efforts to determine local time, and enforcement has hit cases where callers made no effort or ignored obvious geographic signals [2]. But "good faith" is a shaky defense when a plaintiff's lawyer holds a 6:47 AM call record in front of a jury.
Does the quiet hours rule apply to text messages too?
Yes. Text messages sent through an ATDS to a cell phone fall under the TCPA, quiet hours included [2]. Since 2003 the FCC has held that an SMS blast sent through an automated platform is a "call" under 47 U.S.C. § 227. A marketing text fired at 9:30 PM recipient time is a violation the same as a 9:30 PM voice call.
Outbound SMS teams sometimes treat quiet hours as a call-center problem. It isn't. And texts carry a timestamp right there on the recipient's screen, which makes them easier for a plaintiff to document than a voicemail nobody saved.
The CTIA Messaging Principles and Best Practices document recommends SMS programs stick to an 8:00 AM to 8:00 PM local window, tighter than the federal floor [3]. Carriers use those guidelines to make filtering calls. If your traffic keeps going out late at night, your short code or 10DLC campaign can get flagged or suspended, separate from any legal claim.
For how SMS compliance works end to end, consent rules alongside timing, see our guide to text message marketing.
What is the penalty for calling or texting during quiet hours?
The TCPA sets $500 per violation for negligent violations and up to $1,500 per violation for willful or knowing ones [6]. Every call and every text is its own violation. A batch of 10,000 marketing texts sent at 9:15 PM to recipients in a single state is potentially 10,000 violations. That's $5 million at the $500 floor, $15 million if a court finds it willful.
Those numbers are why quiet hours cases settle instead of going to trial. Courts certify quiet hours violations as class actions because every class member got the same contact at the same moment, which proves the violation across the whole class in one shot. Major TCPA settlements run into the tens of millions.
For a sense of real dollars, look at the UnitedHealthcare matter where the company agreed to pay $2.5 million to resolve alleged TCPA violations, covered at unitedhealthcare to pay $2.5m for alleged TCPA violations, or the Truist Bank settlement at truist bank tcpa class action settlement. Neither turned on quiet hours specifically, but both show the settlement range for systemic TCPA failures.
One more thing. Courts have split on whether a quiet hours violation needs proof of actual harm. Most circuits hold that a single unwanted call or text is enough for Article III standing. That makes it easy for a plaintiff to get through the courthouse door.
Does prior express consent let you call outside quiet hours?
No. This is one of the most common misreads in outbound compliance. Prior express written consent (PEWC) gives you permission to use an ATDS or prerecorded voice to reach a consumer. It does not touch the time restrictions. Consent and quiet hours are two separate requirements, and you have to meet both.
The FCC has never ruled that consent waives quiet hours, and no federal circuit has upheld a consent-based defense to a quiet hours violation in clean, controlling precedent. If your legal team says a signed consent form lets you call at 6 AM, get a second opinion.
There's a thin argument that a consumer who gives specific written instructions to call at odd hours has consented to those hours, but that's speculative and untested. In practice, a real outbound operation has no reason to call before 8 AM or after 9 PM anyway. Answer rates are worse. Agent performance is worse. The legal risk is out of proportion to any upside. Stay in the window.
For consent rules generally, what PEWC actually requires and how to capture it, the FCC's 2012 order (FCC 12-21) and the agency's consumer guidance are the primary references [2].
What about calls that are not telemarketing, like collections or appointment reminders?
The quiet hours rule at 47 C.F.R. § 64.1200(c)(1) technically covers "telephone solicitations," which the FCC defines as calls that encourage buying goods or services [1]. Purely informational contact (debt collection calls to someone who owes you, appointment reminders, two-factor codes, delivery notifications) has historically been treated differently.
But the line between informational and promotional is blurry, and the FCC and the courts have moved it more than once. A collection call that pitches a new payment-plan product can turn into a solicitation. An appointment reminder that mentions a related service can too. The 2021 Facebook v. Duguid decision narrowed what counts as an ATDS, which changed some call types, but left the quiet hours rule alone [5].
Healthcare calls carry a HIPAA overlay that can add timing and content restrictions on top of the TCPA.
Here's the practical read. Even if your calls are purely informational and technically exempt, ringing someone at 5:30 AM or 10:30 PM generates complaints. Complaints draw FCC attention. FCC attention finds other gaps. The quiet hours window is a sensible operating norm even for calls that might be legally exempt.
How do robocall quiet hours work differently from live-agent calls?
For quiet hours, the agent type doesn't change the rule. An ATDS, a prerecorded voice call (robocall), or a live agent making a telephone solicitation to a residential line all sit under the same 8 AM to 9 PM local restriction [1].
Technology type matters elsewhere in the TCPA. Robocalls and ATDS calls to cell phones need prior express consent regardless of time. Live agent calls to cell phones, with no prerecorded voice and no ATDS, land in a different category after Facebook v. Duguid narrowed the ATDS definition [5]. But the time restriction attaches to the solicitation, not to the machine delivering it.
Where the distinction shows up is enforcement. The FCC goes harder after large robocall operations that break quiet hours because the volume is higher and the evidence is cleaner. One platform blasting 2 million prerecorded messages at 9:15 PM leaves a clear pattern. A live agent team working late shifts carries the same legal risk but is harder to catch at scale.
To understand your robocall exposure more broadly, our piece on how to stop robocalls covers the consumer side, which is useful context for what regulators and plaintiffs actually respond to.
What does a compliant quiet hours process actually look like?
A defensible quiet hours process is not complicated. Every step matters, though. Here's what one looks like in practice.
First, configure your dialer or SMS platform to suppress any outbound contact outside the 8 AM to 9 PM window in the recipient's local time, calculated in real time at the moment of contact, not at batch scheduling. Schedule a batch at 7 PM Eastern that fires immediately, and it's fine for Eastern recipients but wrong for Pacific ones if the batch runs long. The filter has to run at send time.
Second, use a real-time number lookup to set each recipient's time zone from NPA-NXX data and ported line status. Make it part of your pre-contact data hygiene, refreshed within 30 days for your list. Several providers offer it, usually for fractions of a cent per lookup.
Third, build in a buffer. Don't start calls at exactly 8:00:00 AM. A system clock error, a daylight saving misconfiguration, or a queue delay can push a contact into the banned window. Start at 8:05 AM, stop at 8:55 PM. That adds almost no friction and cuts your edge-case risk.
Fourth, audit your logs. Pull a weekly sample of outbound records and confirm nothing went out outside the window. If your platform can't give you contact timestamps with recipient-level time zone data, fix that. LeadCompliant's free TCPA compliance tools include a time zone checker that helps you validate a setup before a new campaign goes live.
Fifth, document everything. In a TCPA dispute, your ability to produce timestamped logs with recipient-level time zone math is the difference between a quick dismissal and a long discovery fight.
For SMS specifically, check whether your 10DLC campaign registration carries time-of-day restrictions. Some campaign types have carrier limits stricter than federal law.
What if a contact's time zone is unknown or the data is ambiguous?
You have a few options, none of them clean. The conservative answer is to hold off until you have reliable time zone data. If you buy leads and 15% arrive with no reliable geographic data, that's a data quality problem with your source, not a compliance loophole to engineer around.
The practical answer most teams use is to apply the most restrictive window to any fuzzy record. Can't tell if someone's on Pacific or Mountain time? Treat them as Pacific, the earlier zone. Can't pin down their state at all? Use 9:00 AM to 8:00 PM, which satisfies the strictest state-level restrictions in play as of 2025.
Don't use the caller's local time as a fallback. That approach has produced violations in FCC enforcement and it's exactly the "no effort made" situation that supports a willfulness finding.
One more wrinkle: U.S. territories carry their own time offsets (Puerto Rico, the U.S. Virgin Islands, Guam, American Samoa, the Northern Mariana Islands) where federal TCPA applies but continental area code assumptions break. If your lists include territory area codes, set your lookup up for them.
The Credit One litigation shows what happens when basic data hygiene fails at scale. For how that case developed, see credit one tcpa settlement and the related joseph snyder credit one tcpa filing.
How does the FCC enforce quiet hours violations?
FCC enforcement runs through two channels: the agency's own enforcement bureau, which issues citations and fines under its authority over carriers and telemarketers, and the private right of action the TCPA hands directly to consumers [6][11].
The enforcement bureau focuses on high-volume, systematic violations, robocalls above all. The agency issues a Notice of Apparent Liability (NAL), the target gets a chance to respond, then the FCC can issue a forfeiture order. Fines can reach $10,000 per violation per day for continuing violations under 47 U.S.C. § 503(b), though the amounts the agency actually assesses get negotiated and often land well below the stated maximum [11].
The private right of action is where most quiet hours cases actually happen. A consumer who gets a call at 9:15 PM can file in federal district court or state court without filing an FCC complaint first. Class certification comes easy for quiet hours cases because everyone got the same call at the same time and the call logs prove it. Plaintiff attorneys work these on contingency, and a timestamp is hard to argue with.
State attorneys general can bring their own actions under state telemarketing laws that mirror or incorporate the quiet hours rule. Those have grown more common over the past few years, especially in California, Texas, and Florida.
For a current read on enforcement trends, tcpa news tracks developments in the space.
Frequently asked questions
Can I text someone at 9:00 PM exactly under TCPA?
Yes. The federal ban is on contact made after 9 PM local time. A text delivered at exactly 9:00 PM is inside the permitted window. But delivery timestamps drift by seconds depending on carrier routing and platform queuing, so most compliance teams set an 8:55 PM cutoff to dodge any edge-case dispute. The CTIA's messaging guidelines recommend cutting off at 8:00 PM anyway, which removes the issue entirely.
Do TCPA quiet hours apply on weekends and holidays?
Yes. The 8:00 AM to 9:00 PM local rule under 47 C.F.R. § 64.1200(c)(1) has no exception for weekends, federal holidays, or any other day. Some state laws add Sunday restrictions on top. Maryland, for one, bans calls before 1:00 PM on Sundays. Check each state where you call for day-specific rules beyond the federal window.
What time zone applies if the area code and the recipient's actual location don't match?
The recipient's actual location controls. The FCC rule says local time at the called party's location, not the time zone tied to the area code. Number portability makes area codes unreliable geographic signals. Use a real-time NPA-NXX lookup combined with ported line data for the best available estimate. When the data is ambiguous, apply the most restrictive zone (earliest start, earliest end).
Does TCPA quiet hours apply to B2B calls?
The federal quiet hours rule covers telephone solicitations to residential lines. Calls to business numbers for B2B purposes sit outside the strict residential TCPA framework in most cases. But many sales calls hit cell phones that are personal devices used for work, and those can fall under TCPA rules on ATDS usage regardless of purpose. State telemarketing laws sometimes reach B2B calls, so check the rules in your target markets.
What if a customer asks me to call them early in the morning or late at night?
This is legally untested. If a consumer explicitly asks for a call at a specific time outside the standard window, there's an argument they've consented to it. But no FCC order or circuit court ruling has confirmed that a consumer's time preference overrides quiet hours. If a customer insists on a very early or very late callback, the safe move is to note it in your CRM and offer to call first thing inside the permitted window.
Can I send automated appointment reminders or transactional texts outside quiet hours?
Maybe, if they're genuinely non-promotional. Purely informational texts (appointment reminders with no marketing, delivery updates, account alerts) have historically escaped treatment as telephone solicitations subject to quiet hours. But add any promotional element and the quiet hours rule kicks in. Courts and the FCC have found mixed-content messages to be solicitations, so strip marketing language from anything you want treated as informational.
How does Florida's Mini-TCPA (FTSA) affect quiet hours for texts?
Florida's Telephone Solicitation Act (Fla. Stat. § 501.059), amended in 2021, covers calls and texts using auto-dialers and sets its own restrictions on Florida residents. Its call window matches federal law at 8:00 AM to 9:00 PM, but the FTSA's auto-dialer definition is broader than the post-Duguid federal standard, so more platforms get caught. Check current FTSA amendments, because Florida keeps changing this statute.
What is the earliest I can legally call or text someone for marketing under TCPA?
8:00 AM local time at the recipient's location is the federal floor under 47 C.F.R. § 64.1200(c)(1). Several states push it to 9:00 AM (Texas, Indiana, Colorado). Call nationally and want one rule for everywhere? Start no earlier than 9:00 AM recipient local time. That clears both the federal rule and every current state restriction in the strictest tier.
How do I prove compliance with quiet hours if I'm sued?
You need contact logs showing the timestamp of every call or text at the recipient level, plus documentation of how you determined each recipient's time zone. Ideally your platform logs the NPA-NXX lookup result, the assigned time zone, and the local send time alongside the UTC timestamp. Without that, you're arguing against a plaintiff's phone records (which show a 9:15 PM message) with nothing but your word about your system config.
Are there TCPA quiet hours exceptions for emergency calls?
Yes. The TCPA and its rules have always excluded calls made for emergency purposes from the general telemarketing restrictions, quiet hours included. The exemption is narrow: it covers genuine emergency notifications, not marketing dressed up with an emergency angle. An insurer texting a hurricane alert to policyholders at 11 PM is likely exempt. The same insurer sending a policy renewal offer at 11 PM is not.
Does the Albertsons or Safeway TCPA settlement involve quiet hours?
The Albertsons and Safeway TCPA settlement (covered at the albertsons safeway tcpa settlement page) involved allegations of marketing texts sent without proper consent, a common pattern in retail loyalty and rewards programs. Quiet hours were not the central claim, but the case shows how SMS marketing across large retail chains generates class-action exposure fast when compliance doesn't scale with the marketing operation.
Is there a safe harbor if my platform sent a message outside quiet hours due to a technical error?
No statutory safe harbor exists for technical errors under the TCPA. The FCC recognizes that carriers and platforms sometimes fail technically, but that hasn't produced a defined safe harbor for callers. Courts weigh whether a violation was willful when setting damages, so a documented technical error plus evidence of a compliant system design can influence whether you pay $500 or $1,500 per violation. It does not erase liability. Fix the issue and document when and how it happened.
What is the latest my sales team can legally call prospects?
9:00 PM local time at the prospect's location under federal TCPA rules. Some states close earlier: Massachusetts at 8:00 PM. Most compliance teams set a practical cutoff of 8:45 PM or 8:50 PM as separate queue windows per zone so no call slips past 9:00 PM anywhere. Running a single national queue? The safe cutoff is 8:00 PM Pacific, which keeps every time zone inside the window.
Sources
- FCC, 47 C.F.R. § 64.1200 (Code of Federal Regulations, Subpart L, Restrictions on Telemarketing): Federal regulation prohibiting telephone solicitations before 8 AM or after 9 PM local time at the called party's location, per 47 CFR 64.1200(c)(1)
- NCSL, Telemarketing and Do Not Call Laws by State: State telemarketing laws that set stricter call time windows than federal TCPA, including Massachusetts 8 PM cutoff and Texas/Indiana 9 AM start
- Supreme Court of the United States, Facebook, Inc. v. Duguid, 592 U.S. 395 (2021): Supreme Court narrowed the definition of ATDS under TCPA; did not affect the quiet hours provision at 47 C.F.R. 64.1200(c)(1)
- U.S. Congress, Telephone Consumer Protection Act, 47 U.S.C. § 227: Statutory text of 47 U.S.C. 227, the Telephone Consumer Protection Act, providing $500 to $1,500 per violation penalties
- Federal Trade Commission, Telemarketing Sales Rule and Do Not Call information: FTC guidance on telemarketing call-time restrictions and enforcement parallel to the FCC's TCPA rules
- Florida Legislature, Florida Telephone Solicitation Act, Fla. Stat. § 501.059: Florida's FTSA time window for solicitation calls and texts matching federal 8 AM to 9 PM rule with broader auto-dialer definition
- Texas Legislature, Tex. Bus. & Com. Code § 302.101, Texas telemarketing hours restriction: Texas state law restricts telemarketing calls to 9:00 AM to 9:00 PM local time, stricter than federal TCPA on the morning end
- Massachusetts General Laws, ch. 159C, Telephone Solicitation Law: Massachusetts restricts telemarketing calls to 8:00 AM to 8:00 PM, an earlier evening cutoff than the federal TCPA rule
- Maryland Code, Com. Law § 14-3201, Maryland Telephone Consumer Protection Act: Maryland telemarketing restriction including prohibition on calls before 1:00 PM on Sundays