AI Calling Compliance · Updated 16 July 2026
TCPA Quiet Hours for AI Calls: The 8am–9pm Local-Time Rule (2026)
TCPA quiet hours ban telephone solicitations before 8:00 a.m. and after 9:00 p.m. in the time zone where the person being called is located — not where the dialer, the agent, or the company is. The rule is 47 C.F.R. § 64.1200(c)(1), issued under the Telephone Consumer Protection Act, 47 U.S.C. § 227.
It applies to AI voice calls exactly as it applies to human ones. The FCC’s Declaratory Ruling FCC 24-17(adopted 2 February 2024, released 8 February 2024) confirmed that AI-generated voices are “artificial” voices under the TCPA — but quiet hours never turned on who or what was speaking. They turn on the call being a solicitation. An AI voice agent dialing at 7:00 a.m. recipient-local is in the same position as a human doing it.
Statutory damages are $500 per violation, trebled to $1,500 for a willful or knowing violation (47 U.S.C. § 227(c)(5)) — assessed per call, which is what makes automated dialing the expensive place to get this wrong. Several U.S. states are stricter than the federal window: Florida, Oklahoma, and Washington close at 8:00 p.m., and Connecticut does not open until 9:00 a.m. The operational requirement reduces to one sentence: resolve each recipient’s local time before you dial, and apply the strictest window that applies to them.
What the rule actually says
The operative text of 47 C.F.R. § 64.1200(c)(1) is short: no person or entity shall initiate any telephone solicitation to a residential telephone subscriber “before the hour of 8 a.m. or after 9 p.m. (local time at the called party’s location).” The parenthetical is the entire compliance problem. Everything else about a calling operation — the dialer’s location, the agent’s shift, the campaign schedule — is measured in a time zone the rule does not care about.
Three details carry more weight than their length suggests:
- The window is a clock, not a courtesy. 8:00 p.m. in Florida is a closed window even if the recipient is demonstrably awake and even if the call would have been welcome.
- Texts are calls. The FCC treats an SMS message as a “call” for TCPA purposes, which is why the 2025 wave of quiet-hours class actions is overwhelmingly about marketing texts rather than voice.
- Email is not covered. Commercial email is governed by the CAN-SPAM Act, which imposes no time-of-day restriction at all. Gating an email channel on quiet hours is a misreading of the rule, not extra caution.
Why the FCC’s 2024 AI ruling did not move the clock
On 2 February 2024 the FCC unanimously adopted Declaratory Ruling FCC 24-17, released 8 February 2024, confirming that the TCPA’s restrictions on an “artificial or prerecorded voice” encompass current AI technologies that generate human voices — including voice cloning that mimics a specific real person. The consequence is that an AI-voiced call needs the prior express consent of the called party under 47 U.S.C. § 227(b)(1)(A), plus caller-identification disclosures and opt-out mechanisms.
The distinction that gets missed: FCC 24-17 governs subsection (b) — the consent regime for artificial and prerecorded voices. Quiet hours live in subsection (c) — the telephone-solicitation regime. They are different prongs of the same statute with different triggers, different exemptions, and different private rights of action.
So the 2024 ruling did not extend quiet hours to AI calls. Quiet hours already covered them, because § 64.1200(c)(1) asks whether the call is a solicitation, never whether a human, a recording, or a neural network is producing the audio. What FCC 24-17 changed is that an AI voice agent now carries both obligations simultaneously: it needs consent under (b) because the voice is artificial, and it needs the calling window under (c) because the call is a solicitation. Satisfying one says nothing about the other.
How the recipient’s time zone is determined
The rule says “the called party’s location.” It does not say “area code.” That gap is where compliance engineering actually happens, because no dialer knows where anyone is standing.
Area code (the NPA, the first three digits) is the usual proxy, and it is a decent one for landlines. It degrades badly for mobile numbers for two reasons. Local number portability lets a subscriber keep a number after moving across the country, so a 212 number can sit in Los Angeles indefinitely. And some area codes straddle time zones outright — a single NPA can cover two zones, meaning the area code alone cannot resolve the hour even when the subscriber never moved.
The industry asked the FCC to bless the proxy. On 3 March 2025 the Ecommerce Innovation Alliance petitioned for a declaratory ruling that callers may rely on a number’s NPA-NXX to determine its location, and that prior express written consent permits calls during quiet hours. The FCC sought comment in Public Notice DA 25-216 on 11 March 2025, with comments due 10 April 2025 and replies 25 April 2025. As of July 2026 the petition is still pending — the safe-harbor it asks for does not exist yet.
Absent that safe harbor, the defensible engineering position is a fallback chain that prefers better evidence over worse and never silently guesses: an explicit time zone the CRM already knows, then the area code, then a workspace-level default, then an organization-level default. The failure mode to design against is a fallback to UTC, which is not a location — it is the absence of one, and it will happily authorize a 3:00 a.m. call.
States that are stricter than 8am–9pm
The federal window is a floor, not a ceiling. A number of states impose a narrower telephone-solicitation window, and the strictest applicable rule governs each individual recipient — determined by theirjurisdiction, not the caller’s. Published counts of how many states are stricter disagree, which is itself a reason to resolve the question per contact rather than per campaign. These are the windows Veera applies today:
| Jurisdiction | Calling window (local) | Governing rule |
|---|---|---|
| Federal baseline | 8:00 a.m. – 9:00 p.m. | 47 C.F.R. § 64.1200(c)(1) |
| Florida | 8:00 a.m. – 8:00 p.m. | Fla. Stat. § 501.616(6)(a) |
| Oklahoma | 8:00 a.m. – 8:00 p.m. | Okla. Stat. tit. 15 § 775C.1 et seq. |
| Washington | 8:00 a.m. – 8:00 p.m. | RCW 80.36.390 |
| Connecticut | 9:00 a.m. – 8:00 p.m. | Conn. Gen. Stat. § 42-288a |
Veera’s table currently encodes ten states with windows stricter than federal. Florida, Oklahoma, and Washington are the three whose statute text Veera has read directly; the remaining seven (Alabama, Connecticut, Louisiana, Massachusetts, Maryland, Mississippi, Wyoming) are applied conservatively from secondary sources pending primary verification — over-restricting on an unverified entry costs dialing time, while omitting a real restriction costs statutory damages. Connecticut is the one that breaks the pattern people expect — it is the openinghour that moves, to 9:00 a.m., so a campaign tuned to “8am is always safe” is wrong there every morning.
One honest limitation worth stating plainly: several states also restrict solicitation by day— Louisiana’s Sunday rule and Alabama’s holiday rule among them. A time-of-day window has no day dimension and cannot express those. Veera encodes the hours, not the day and holiday bans, and those remain the operator’s responsibility.
Penalties and the 2025–2026 litigation wave
The private right of action at 47 U.S.C. § 227(c)(5) lets a person who receives more than one violating call in a twelve-month period sue for actual monetary loss or $500 per violation, whichever is greater. A court may increase the award to up to $1,500 per violation where the violation was willful or knowing.
Per-violation arithmetic is the whole story. A campaign that dials 10,000 numbers with a broken time-zone assumption does not commit one violation worth $500. It commits up to 10,000 of them, and at the trebled rate that is $15 million in exposure from a single scheduling bug. This structure is why quiet-hours claims are filed as class actions, and why the count of exposed records — not the severity of any one call — drives the number.
Filings surged from late 2024 through 2025. TCPA class actions rose from 239 in the first quarter of 2024 to 507 in the first quarter of 2025 — a 112% year-over-year increase — and quiet-hours theories were the single largest driver, with one Florida firm alone filing well over 100 near-identical complaints since November 2024. The plaintiff’s theory is mechanical: pull the message logs, mark every one that landed outside 8:00 a.m. to 9:00 p.m. in the recipient’s zone, and multiply.
Defendants got their strongest answer yet on 30 December 2025. In King v. Bon Charge, No. 25-cv-00105-SB (D. Del. 30 December 2025, as amended 30 April 2026), Judge Stephanos Bibas — a Third Circuit judge sitting by designation — held that a consumer who texted a keyword to subscribe to marketing in exchange for a discount code had thereby given “prior express invitation or permission.” Under 47 C.F.R. § 64.1200(f)(15) that removes the messages from the definition of “telephone solicitation” entirely, and quiet hours only ever applied to solicitations — so the claim failed. The court also noted that the Do-Not-Call rules impose a heightened, signed-writing consent standard that the quiet-hours provision conspicuously does not.
That decision was possible in the form it took because of a third one. On 20 June 2025 the Supreme Court decided McLaughlin Chiropractic Associates, Inc. v. McKesson Corp., No. 23-1226, holding 6–3 (Kavanaugh, J.) that the Hobbs Act does not bind district courts in civil enforcement proceedings to the FCC’s interpretation of the TCPA. A district court must now independently determine the statute’s best reading, giving the agency’s view only appropriate respect. The practical consequence for quiet hours is uncomfortable in both directions: a favorable FCC ruling on the pending petition would no longer settle the question by itself, because courts are free to read § 64.1200(c)(1) for themselves — and so are courts inclined to read it against you.
Read the Bon Charge holding for what it is: one district court, persuasive but not binding, on a question the FCC has been sitting on since March 2025, in a post-McLaughlin landscape where no single authority is going to resolve it cleanly. Building a calling operation on the premise that consent cancels quiet hours means betting the damages model on an open legal question. Staying inside the window costs a few hours of dialing time and does not require winning anything.
How Veera enforces the calling window
Veera’s AI voice calling is live, and the quiet-hours check runs on every call it places. It is not a campaign setting, not a toggle, and not skippable — a call outside the recipient’s window is rejected before the number is dialed, and the operator is told why.
Four properties do the work:
- 1.The recipient’s zone, resolved by a four-rung chain. An explicit time zone from the connected CRM, then the phone number’s area code, then the client workspace default, then the organization default. The chain never terminates in UTC. Every send records which rung produced the answer, so the decision is auditable after the fact rather than reconstructed.
- 2.Ambiguity resolves to the intersection, not a guess. An area code straddling two zones is evaluated against both, and the call goes out only if the hour is legal in each. A valid US number whose area code is unrecognized gets that treatment twice over: the zone falls back to an Eastern-plus-Pacific intersection, and the jurisdiction, being unresolvable, fails closed to the strictest window Veera encodes — 9:00 a.m. to 8:00 p.m. Composed, the two leave a send window of noon to 8:00 p.m. Eastern, which is inside the permitted hours in every contiguous-US zone.
- 3.State windows layer over the federal default. The window is selected from the contact’s jurisdiction and folded to the strictest applicable — latest opening hour, earliest closing hour. An 8:30 p.m. call to a Florida number is rejected even though federal law alone would permit it. An unresolvable jurisdiction fails closed to the strictest window in the table rather than defaulting to the permissive federal one.
- 4.Daylight saving is computed, not approximated. Offsets are derived per instant from the IANA zone database rather than stored as fixed numbers, so the window tracks the recipient’s actual wall clock across DST transitions instead of drifting by an hour twice a year.
Scope, stated honestly. The window math covers Veera’s phone channels; voice calling is the channel that is live today, while SMS and WhatsApp outreach are still being activated and email outreach is building. In-call WhatsApp document delivery — sending a brochure or quote during a live call — is the one send path already running alongside voice. Email is deliberately not gated on quiet hours, because CAN-SPAM imposes no time-of-day rule and applying one would be wrong rather than cautious. Veera also honors CAN-SPAM one-click unsubscribe with suppression checked before every send, and honors GDPR Article 17 erasure requests. None of that is a certification, and this page is not legal advice: quiet hours are one requirement among several, and the enforcement described here is a control, not a legal opinion about your program.
Veera syncs into the CRM an agency already runs — GoHighLevel or HubSpot — rather than replacing it. The call, its outcome, and the timezone decision behind it are recorded on the contact record in Veera, which is what makes the window auditable after the fact. Pushing that call activity into the connected CRM automatically is built and activating — not usable today. Veera is free to start.
Frequently asked questions
What are TCPA quiet hours?
TCPA quiet hours are the hours during which telephone solicitations are prohibited: before 8:00 a.m. and after 9:00 p.m., measured in local time at the called party’s location. The rule is 47 C.F.R. § 64.1200(c)(1), issued under the Telephone Consumer Protection Act, 47 U.S.C. § 227. The permitted window is therefore 8:00 a.m. to 9:00 p.m. recipient-local, and several U.S. states narrow it further — Florida, Oklahoma, and Washington all close at 8:00 p.m.
Do TCPA quiet hours apply to AI voice calls?
Yes. Quiet hours attach to the call being a telephone solicitation, not to who or what is speaking, so they have always covered automated and AI-placed calls. The FCC’s Declaratory Ruling FCC 24-17, adopted 2 February 2024 and released 8 February 2024, confirmed that AI-generated voices are “artificial” voices under 47 U.S.C. § 227(b)(1)(A) and therefore require prior express consent. That ruling tightened the consent analysis for AI calls; it did not create, move, or relax the 8:00 a.m. to 9:00 p.m. clock.
Which time zone counts — the caller’s or the recipient’s?
The recipient’s. 47 C.F.R. § 64.1200(c)(1) fixes the window to “local time at the called party’s location,” so the dialer’s time zone, the agent’s time zone, and the company’s headquarters time zone are all irrelevant. A platform in New York dialing 8:30 a.m. Eastern is calling a California recipient at 5:30 a.m. Pacific, which is a violation regardless of what the caller’s clock says.
What are the penalties for calling outside TCPA quiet hours?
Statutory damages are $500 per violation, which a court may treble to $1,500 per violation for a willful or knowing violation, under the private right of action at 47 U.S.C. § 227(c)(5). Damages accrue per call rather than per campaign, which is why quiet-hours claims are pleaded as class actions: a single mistimed automated batch multiplies the same error across every number in it.
Does prior express consent exempt a call from quiet hours?
It is contested and unresolved at the federal level. Quiet hours apply only to a “telephone solicitation,” which 47 C.F.R. § 64.1200(f)(15) defines to exclude calls made with the recipient’s prior express invitation or permission, so consent arguably removes a call from the rule entirely. In King v. Bon Charge, No. 25-cv-00105-SB (D. Del. 30 December 2025, as amended 30 April 2026), Judge Stephanos Bibas held that a consumer who knowingly gave her number to receive marketing had given that permission, defeating her quiet-hours claim. That is one district court decision and is not binding nationally. The Ecommerce Innovation Alliance petitioned the FCC on 3 March 2025 to rule that prior express written consent waives quiet hours; the FCC sought comment in Public Notice DA 25-216 on 11 March 2025, and the petition remains pending. An FCC ruling would also no longer settle the question by itself: in McLaughlin Chiropractic Associates, Inc. v. McKesson Corp., No. 23-1226 (U.S. 20 June 2025), the Supreme Court held 6–3 that district courts must independently determine the best reading of the statute rather than defer to the FCC’s interpretation. Until it is resolved, calling inside the window is the only position that does not depend on winning an open legal question.
Does Veera enforce TCPA quiet hours automatically?
Yes, on every call, and the check cannot be turned off per campaign. Veera resolves the recipient’s local time before dialing using a four-step chain — an explicit time zone from the connected CRM, then the phone number’s area code, then the client workspace time zone, then the organization time zone — and never falls back to UTC. It then applies the strictest window that governs that recipient, federal or state, and rejects the call if the local time falls outside it. Where the jurisdiction cannot be resolved, the check fails closed to the strictest window Veera knows rather than defaulting to the permissive federal one.
This page is part of Veera’s AI calling compliance guide, a reference for the rules that govern automated outreach. Legal citations are to 47 U.S.C. § 227, 47 C.F.R. § 64.1200, FCC Declaratory Ruling FCC 24-17 (8 February 2024), FCC Public Notice DA 25-216 (11 March 2025), McLaughlin Chiropractic Associates, Inc. v. McKesson Corp., No. 23-1226 (U.S. 20 June 2025), and King v. Bon Charge, No. 25-cv-00105-SB (D. Del. 30 December 2025, as amended 30 April 2026); state windows are cited to their governing statutes in the table above; reviewed 16 July 2026. This page describes the calling window Veera enforces and the rules it is built against. It is not legal advice, and it is not a substitute for counsel who knows your program. See also: What is an AI Business Aide? and State of Outbound Business AI 2026.