FTC telemarketing sales rule calling time: the 8am, 9pm local time rule explained

The FTC's Telemarketing Sales Rule bans calls before 8am or after 9pm in the called party's local time. Here's exactly how it works and what it costs to get wrong.

LeadCompliant Team
24 min read
In This Article

Last updated 2026-07-09

Office desk phone and clock at 7:45 am beside a window, calling hours compliance
Office desk phone and clock at 7:45 am beside a window, calling hours compliance

TL;DR

The FTC's Telemarketing Sales Rule (16 CFR Part 310) bans telemarketing calls before 8:00 a.m. or after 9:00 p.m. in the called party's local time. The burden sits on the caller, not the recipient. FTC civil penalties reach $51,744 per call. The TCPA sets the same window and lets private plaintiffs sue for $500 to $1,500 per call. Some states are stricter.

What does the FTC Telemarketing Sales Rule say about calling hours?

The rule bans telemarketing calls before 8:00 a.m. or after 9:00 p.m. in the called party's local time, and the clock runs on where the phone rings, not where your dialer sits. 16 CFR § 310.4(c) calls it an abusive telemarketing act to make outbound calls to a residence "at any time other than between 8:00 a.m. and 9:00 p.m. local time at the called person's location." [1]

That's the whole sentence. No carve-out for B2B. No grace period for "a few minutes early." No exception for callers who didn't know the time zone.

The Telemarketing Sales Rule (TSR) came from the Federal Trade Commission under the Telemarketing and Consumer Fraud and Abuse Prevention Act, 15 U.S.C. §§ 6101 to 6108. [2] The FTC has enforced the rule since 1995. The calling-hours language has stayed essentially the same through every major amendment, including the 2003 update that built the National Do Not Call Registry. [3]

The TCPA, enforced by the FCC under 47 U.S.C. § 227, has an identical 8:00 a.m. to 9:00 p.m. local-time restriction for residential calls. [4] So you're inside two separate federal frameworks that happen to land on the same window. Break one and you usually break both.

Does "local time" mean the caller's time zone or the recipient's?

The recipient's. Always. This is the mistake that generates the most complaints, and teams make it constantly.

Say your sales floor is in Phoenix (Mountain Standard Time, no daylight saving) and you're calling New York (Eastern). New York's clock governs. In summer that's a two-hour gap. A 7:30 a.m. call from Phoenix lands at 9:30 a.m. in New York, fine. But a 7:30 a.m. call to Los Angeles, also Pacific, lands at 7:30 a.m. there. Thirty minutes before the window opens. That's a violation.

The burden of figuring out local time sits entirely with the caller. The FTC has never accepted "we didn't know the time zone" as a defense. If your dialer can't resolve the time zone for a number, the safe move is to hold the call until 8:00 a.m. in the most conservative plausible zone for that area code, or better, run a number-lookup that maps the number to a real location before you dial. [5]

Area codes alone are not reliable. Number portability means a 212 (New York) number can belong to someone who moved to California a decade ago. Carrier-grade CNAM and geolocation lookups give you a far better read on where the phone actually is. This is one place where a fraction of a cent per call on data hygiene saves you from five-figure penalties.

What are the penalties for calling outside the 8am, 9pm window?

The FTC can seek up to $51,744 per violation under the current penalty schedule, adjusted for inflation under the Federal Civil Penalties Inflation Adjustment Act. [6] That figure applies to violations after January 10, 2023. Earlier violations carry slightly lower maximums.

The FCC, working the TCPA side of the same call, has its own numbers. The TCPA lets private plaintiffs sue for $500 per violation or actual damages, whichever is greater, and courts can treble that to $1,500 per call for willful or knowing violations. [4] There is no cap per campaign. That's why one blast to 50,000 numbers outside the window can produce tens of millions in exposure before a trial even starts.

State attorneys general pile on separately. Florida's Telephonic Sales Law mirrors the 8-to-9 window and lets the AG chase additional per-call penalties on top of federal enforcement. [7]

Here's the practical reality. The FTC rarely chases a single bad call. Enforcement actions run on pattern evidence, usually complaints to the DNC Registry or the FTC's complaint portal, showing thousands of out-of-window calls over weeks or months. Private TCPA litigation moves faster. Plaintiffs' lawyers don't need a pattern, because the TCPA hands them a private right of action on a single call.

Key numbers in the FTC/TCPA calling-hours rule Thresholds, penalties, and limits every outbound team needs to know 13 Permitted calling window (h… per day) 52k Max FTC civil penalty per violation ($) 1,500 TCPA statutory damages per willful call ($) 24 Required record retention (… TSR) Source: FTC (16 CFR § 310), FCC (47 U.S.C. § 227), 2023–2025

Is there any exception to the 8am, 9pm rule if someone gives consent to be called?

There's no clean, reliable consent exception, and you should treat this as contested ground. The text of 16 CFR § 310.4(c) is flat: calls outside the window are prohibited. The FTC has not published guidance carving out a written-consent exception for hours.

The TCPA framework reads a little differently. The FCC's rules at 47 CFR § 64.1200 set the same 8-to-9 window for residential calls, and the FCC has historically treated prior express invitation or permission as overriding certain restrictions. But the FCC has not clearly said express consent overrides the time-of-day rule the way it overrides the Do Not Call rule. [4]

The safe operational answer: don't rely on consent to call outside the window unless your legal counsel has reviewed a specific, documented consent form that names hours and you've got written sign-off. Some plaintiff-side attorneys argue that even clear written consent to after-hours calls doesn't cure a TSR violation, because the prohibition targets the seller's conduct, not the consumer's right to waive it. Courts haven't universally accepted that argument. It has survived motions to dismiss.

If a consumer genuinely asks you to call at 7:00 a.m., document the request, keep the recording or written record, and still get legal sign-off. The documentation won't guarantee a win. It moves the needle on willfulness.

How does the 8am, 9pm rule apply to mobile phones vs. landlines?

Apply the 8-to-9 window to every consumer mobile number and every residential landline. The TSR's calling-hours rule references calls to a "person's residence." [1] Mobile numbers complicate that, because a cell number isn't inherently residential, and the TSR predates smartphones as the main consumer contact point.

In practice, the FTC treats mobile numbers used for personal, residential purposes as covered by the TSR's residential protections. Reach a consumer on their cell for telemarketing, and the window applies.

The TCPA is clearer. Under 47 U.S.C. § 227(b)(1)(A), automated or prerecorded calls to mobile phones need prior express consent regardless of time of day, and the 8-to-9 window applies to prerecorded messages to residential lines under § 227(b)(1)(B). The FCC reads these provisions to cover mobile numbers called for residential or personal purposes. [4]

B2B calls to a person's direct business mobile shift the analysis, but not entirely in your favor. Most B2B calls fall outside TSR scope. The TCPA's cell-phone provisions have no clean B2B exemption, though. If you autodial a cell number, even a business cell, the TCPA still applies.

So: window on for every consumer mobile and residential landline. For true B2B calls to business direct lines, the TSR hours rule likely doesn't apply, but state-law restrictions still can.

What states have stricter calling hours than the federal 8am, 9pm rule?

Several states tighten the window or add restrictions on top of the federal floor. Federal law sets the minimum. States can always be stricter.

StateCalling windowKey statute
California8:00 a.m., 9:00 p.m. (matches federal)Cal. Bus. & Prof. Code § 17592
Florida8:00 a.m., 9:00 p.m. (matches federal)Fla. Stat. § 501.059
New York8:00 a.m., 9:00 p.m. (matches federal)N.Y. Gen. Bus. Law § 399-z
Indiana9:00 a.m., 9:00 p.m. (one hour later start)Ind. Code § 24-4.7
Oklahoma9:00 a.m., 8:00 p.m. (later start, earlier close)Okla. Stat. tit. 15 § 775A

This table reflects the law as of publication and is not exhaustive. State telemarketing statutes change. Oklahoma's tighter window means a call that's legal in New York at 8:30 a.m. Eastern (7:30 a.m. Central) is illegal in Oklahoma. [10]

The compliance rule is simple. Apply the most restrictive window that applies. If you call nationally, 9:00 a.m. local time in the called party's location is the safest universal start, because it clears both the federal 8:00 a.m. floor and the strictest state starts. On the evening end, an 8:00 p.m. local stop satisfies Oklahoma. [9]

Some states also restrict Sunday and holiday calling. Check the specific statute for every state where you have real call volume. Third-party summaries help, but statutes move, so verify against the primary source before you rely on any of them.

How does time zone complexity work across US territories and unusual time zones?

"Local time" reaches every US territory and every state with an odd clock arrangement, and those edge cases are where compliant-looking campaigns quietly break the rule. The continental US has four standard zones: Eastern, Central, Mountain, Pacific.

Hawaii sits at UTC-10 year-round and skips daylight saving. Alaska is UTC-9 standard, UTC-8 in daylight saving. Puerto Rico is UTC-4 all year with no daylight saving. The US Virgin Islands are UTC-4. Guam is UTC+10. [8]

The TSR and TCPA both cover calls to people in US territories. Call a Puerto Rico number at 9:30 a.m. Eastern and it's also 9:30 a.m. in Puerto Rico year-round, because Puerto Rico never shifts its clocks. That works. But call Hawaii at 8:00 a.m. Pacific and it's 6:00 a.m. in Honolulu. Two full hours inside the ban.

Arizona is another trap. Most of Arizona stays on Mountain Standard Time all year, no daylight saving, but the Navajo Nation inside Arizona does observe daylight saving. In summer, a Navajo Nation number and a Phoenix number, both carrying 928 area codes, sit in different effective time zones.

The only reliable fix is number-level geolocation, not area-code guessing. If your dialing platform can't resolve time zone down to the number, you're flying on instruments that aren't accurate enough.

What should your dialing system actually do to stay compliant with calling hours?

Compliance has to live inside the dialing workflow, not on a policy poster in the break room. Four things do the real work.

First, your CRM or dialer needs time-zone data at the contact level, not the campaign level. Every record should carry a resolved time zone based on geolocation of the number (deeper than the area-code prefix), refreshed each time you update contact data. Predictive and progressive dialers should suppress any number where the current local time is before 8:00 a.m. or after 9:00 p.m. That suppression has to be automatic. Not a manual step an agent might skip.

Second, build in a buffer. Stop dialing at exactly 9:00 p.m. and call-setup latency can push the answer to 9:01 or later. Most compliance teams use 8:55 p.m. as the hard stop for a given zone. On the morning side, starting at 8:05 a.m. instead of 8:00 a.m. costs almost nothing and protects you from clock drift.

Third, log everything. Record the timestamp of every attempt, the time zone applied, and the data source that determined it. In an FTC or FCC action, that log is your first line of defense. "We had a system that auto-blocked out-of-window calls" is a defensible position. "We told agents to watch the clock" is not.

LeadCompliant's free time-zone checker and compliance kit include a calling-hours suppression checklist that walks through the exact settings to audit. Useful if you're configuring a new dialer or checking an old one.

Fourth, audit your vendor contracts. Use a third-party call center or BPO and the TSR makes both the seller and the telemarketer liable. Your contract should require the vendor to keep calling-hours compliance and indemnify you if they don't, but indemnification only matters if they can pay. Verify their practices before you sign, not after the first complaint.

How does the FTC actually find out about calling-hours violations?

Mostly from consumers. The FTC runs the National Do Not Call Registry complaint system, and its complaint form lets people report calls outside the permitted hours. [3] The FTC also operates ReportFraud.ftc.gov for broader telemarketing complaints. The FCC keeps its own complaint portal.

The FTC's data analytics team flags companies with high complaint volume, especially ones showing temporal patterns like a spike in early-morning gripes. Generate 500 DNC complaints in a month, 200 of them saying "called me before 8 a.m.," and you've handed FTC staff exactly the pattern they use to open an investigation.

State AGs collect complaints through their own consumer protection offices. Florida, Texas, and Indiana all run active telemarketing enforcement units that coordinate with the FTC.

Private plaintiffs under the TCPA don't need the FTC to move. A single consumer can sue in federal district court, and class actions consolidate thousands of individual claims. The TCPA's $500-per-violation floor makes those cases attractive to plaintiffs' counsel even when any one person's harm is tiny. Out-of-window calls are easy to document, because call logs carry timestamps.

One enforcement path teams forget: the TSR's third-party liability rule. If an entity "assists and facilitates" a telemarketer it knows, or consciously avoids knowing, is violating the TSR, the FTC can reach the assisting party. Data brokers, dialing vendors, and list sellers can face liability if they had reason to know their customer was calling out of window.

Does the 8am, 9pm rule apply to ringless voicemail and text messages?

Treat both as subject to the 8-to-9 window. Ringless voicemail (RVM) is still contested at the regulatory level as of mid-2025. The FCC hasn't issued a final declaratory ruling that definitively classifies RVM as a "call" under the TCPA, though petitions are pending and the FCC's posture has drifted toward treating RVM as covered. [4] The TSR applies to "outbound telephone calls," and the FTC hasn't published formal guidance classifying RVM either way. So assume the window applies, because the enforcement risk of guessing wrong is severe.

SMS is a different analysis. The TCPA covers texts sent to mobile phones with an autodialer, and the FCC and courts have consistently held that a text is a "call" under the TCPA. The 8-to-9 restriction clearly applies to prerecorded voice messages; whether it strictly applies to texts under the same provision is less settled. Most compliance attorneys apply the window to commercial SMS anyway, for two reasons. Some state laws cover texts and restrict hours outright. And a text that wakes someone at 6:30 a.m. produces the same complaint whether or not the statute technically demanded the restriction.

For a full breakdown of SMS-specific rules, see the broader cold calling compliance framework and the FCC's TCPA resources.

How does the FTC Telemarketing Sales Rule interact with the TCPA on calling hours?

Both rules ban the same window (before 8:00 a.m. or after 9:00 p.m. local time at the called party's location), but they come from different statutes, sit with different agencies, and create different liability.

The TSR is an FTC rule under 15 U.S.C. § 6102. Enforcement runs through the FTC and state AGs. There's no private right of action under the TSR itself, so consumers can't personally sue you under it the way they can under the TCPA. The FTC has to bring enforcement, or a state AG has to act.

The TCPA is a federal statute (47 U.S.C. § 227) enforced by the FCC, state AGs, and private plaintiffs. That private right of action is what makes TCPA litigation so common. Any consumer whose phone rang before 8:00 a.m. or after 9:00 p.m. can sue, no regulator required.

The practical split: FTC enforcement tends to follow a pattern of many violations and lands as injunctions plus civil penalties. TCPA litigation can spring from a single call and produces statutory damages paid straight to the plaintiff. The expensive class actions you read about in telemarketing news are TCPA cases, not TSR actions, precisely because of that private right.

One thing people miss: you can comply with the TSR and still violate the TCPA, and the reverse. Calling a cell with an autodialer before 8:00 a.m. breaks both. Running a predictive dialer on a cell number without consent breaks the TCPA even at 2:00 p.m. The two frameworks overlap. They don't map cleanly onto each other.

For a deeper look at what cold calling involves under both frameworks, and for script-level guidance, the cold calling scripts resource covers how to structure calls that stay inside legal lines.

What records do you need to keep to prove calling-hours compliance?

Keep dialer logs for at least four years and TSR-required records for 24 months. The TSR at 16 CFR § 310.5 requires sellers and telemarketers to keep records for 24 months from the date each record is created. [1] Those records include advertising and promotional materials, the names and last known addresses of prize or premium recipients, the basis for any earnings claims, and records of verifiable authorizations.

For calling hours specifically, the TSR doesn't mandate a set "time-zone log" format, but the FTC expects you to show you had a system capable of complying. In practice that means your dialer logs, which most predictive dialer software generates automatically, showing call timestamp, dialed number, and disposition, retained at least 24 months. If your dialer applies time-zone suppression, keep the configuration records too.

The TCPA sets no retention period for call records, but plaintiff-side discovery routinely reaches back four years. The TCPA's statute of limitations is four years under 28 U.S.C. § 1658. [12] So four years of dialer logs is the defensible standard.

For consent records (relevant if you're claiming prior express consent against other TCPA claims), the FCC and courts expect the actual record: date, time, method of consent, the specific number consented to, and the exact disclosure language shown. Store these so you can search by phone number fast. Can't produce a consent record within 48 hours of a litigation hold, and discovery goes badly.

If you use a cold call script that varies by campaign, keep versioned copies tied to the dates each version ran.

Frequently asked questions

Can I call at exactly 8:00 a.m. or does the window start after 8:00 a.m.?

The TSR says "between 8:00 a.m. and 9:00 p.m.," which in standard legal reading includes the endpoints. A call placed at 8:00:00 a.m. local time is permitted. In practice, most compliance teams start at 8:05 a.m. to absorb clock drift and call-setup time. Nobody has been prosecuted over a call that connected at exactly 8:00 a.m., but shaving the margin to zero is needless risk.

Does the 8am, 9pm rule apply to B2B telemarketing calls?

The TSR's calling-hours restriction is specific to calls to a "person's residence." Most B2B calls to business lines fall outside TSR scope. But the TCPA still applies to autodialed calls to mobile phones even in business contexts, and some states extend calling-hour restrictions beyond residential lines. For calls to a businessperson's personal cell phone, apply the window regardless.

What if my dialer uses area codes to determine time zone and the area code is wrong?

Area-code time zone resolution isn't reliable, because of number portability. A number can carry a New York area code but belong to someone living in California, and carriers transfer numbers across states. For compliance, use number-level geolocation services rather than area-code prefix tables. If your current system only has area-code resolution, that's a gap worth fixing before your next campaign.

If a consumer calls me back outside the 8 to 9 window, can I return that call outside the window?

A consumer-initiated call back to you isn't a telemarketing call and isn't restricted by the TSR. The restriction is on "outbound telephone calls," meaning calls the seller or telemarketer starts. If a consumer leaves a voicemail at 7:00 a.m. asking you to call back, your outbound return call is still subject to the window. Wait until 8:00 a.m. local time to dial out.

Does the calling-hours rule apply to prerecorded robocalls the same way as live agent calls?

Yes, and the TCPA adds a restriction: prerecorded messages to residential lines are prohibited outside the 8-to-9 window under 47 CFR § 64.1200. Prerecorded telemarketing calls also require prior express written consent, layering on top of the time restriction. An illegal prerecorded call outside the window carries both the time-restriction violation and a separate consent violation.

Can an employee make a call outside the 8 to 9 window if they forgot about the rule?

"I forgot" is not a defense under the TSR or TCPA. Both impose strict liability for certain violations. Willfulness raises TCPA damages (up to $1,500 per call from $500), but the baseline violation exists regardless of intent. The caller and the company are both potentially liable. Employee training records and system-level controls that block out-of-window dialing are your best protection.

Do the FTC calling-hours rules apply to nonprofit or political calls?

The TSR generally exempts nonprofit organizations and certain political calls from its telemarketing provisions, including calling hours, because the TSR's definition of "telemarketing" excludes calls by nonprofits. The TCPA's calling-hours provisions and cell phone restrictions apply more broadly, though. Political and nonprofit callers are still subject to state laws, which often set their own hours restrictions. Don't assume nonprofit status is a free pass.

How do I handle calling hours for customers in the same area code but different time zones?

Don't rely on area codes. Use a number intelligence service that geolocates the number to a specific city or ZIP code, then maps that to current local time including daylight saving status. Several carriers and data providers offer real-time time-zone lookup APIs that cost fractions of a cent per query. For high-volume outbound, that cost is negligible against per-call penalty exposure.

What is the FTC's position on calling hours for calls made by AI or automated systems?

The FTC hasn't issued separate AI-specific guidance on calling hours as of mid-2025. The TSR and TCPA apply based on what the call does and who receives it, not on whether a human or a system placed it. An AI-placed call to a residence before 8:00 a.m. is the same TSR and TCPA violation as a human-placed one. For more on automated outreach, the FCC's 2024 AI voice guidance is worth reading alongside the TSR text.

What is the civil penalty per call for TSR calling-hours violations in 2024 to 2025?

The FTC's current maximum civil penalty is $51,744 per violation for violations after January 10, 2023. The FTC adjusts penalties periodically under the Federal Civil Penalties Inflation Adjustment Act. Each out-of-window call is a separate violation, so a campaign with 10,000 early-morning calls could theoretically face over $500 million in maximum exposure, though actual settlements land lower.

Does the 8am, 9pm rule apply to calls made to numbers on a company's existing customer list?

Yes. The calling-hours restriction applies regardless of the caller-recipient relationship. An existing business relationship (EBR) affects Do Not Call obligations but does not override the time-of-day restriction. A call to a current customer's home at 7:30 a.m. is still a violation. EBR status and consent to prior calls create no exception to the hours rule.

What is an "outbound telephone call" under the TSR, and does that definition affect calling hours?

The TSR at 16 CFR § 310.2 defines an "outbound telephone call" as a call initiated by a telemarketer to induce a purchase of goods or services or to solicit a charitable contribution. Inbound calls, where the consumer dials you in response to an ad, aren't outbound calls and generally aren't restricted by the calling-hours provision. Careful, though: an inbound call can turn "outbound" in character if you immediately transfer the caller to a different solicitation.

How should I train my sales team on the 8am, 9pm local time rule?

Training should cover three things: what the rule says (no calls before 8:00 a.m. or after 9:00 p.m. at the called party's location), why area codes alone can't determine local time, and what to do when the system flags a number as out of window (don't call, reschedule for the next permitted window). Annual training plus signed acknowledgments creates a paper trail that shows the company takes compliance seriously.

Sources

  1. FTC, 16 CFR Part 310 – Telemarketing Sales Rule: 16 CFR § 310.4(c) prohibits outbound telephone calls to a residence at any time other than between 8:00 a.m. and 9:00 p.m. local time at the called person's location; § 310.5 requires 24-month record retention
  2. Congress, Telemarketing and Consumer Fraud and Abuse Prevention Act, 15 U.S.C. §§ 6101–6108: The FTC's authority to issue the TSR derives from 15 U.S.C. § 6102
  3. FTC, National Do Not Call Registry: The FTC operates the National Do Not Call Registry complaint system, which captures calling-hours complaints used in enforcement
  4. FTC, Complying with the Telemarketing Sales Rule (business guidance): The caller bears the burden of determining the called party's local time; the FTC provides business guidance on TSR compliance
  5. FTC, Civil penalty inflation adjustments under the Federal Civil Penalties Inflation Adjustment Act: The maximum FTC civil penalty is $51,744 per violation for violations occurring after January 10, 2023, adjusted periodically for inflation
  6. Florida Legislature, Fla. Stat. § 501.059 – Telephone solicitation: Florida's Telephonic Sales Law sets calling hours and allows AG enforcement on top of federal penalties
  7. NIST, Time and Frequency Division – official federal time reference: Hawaii is UTC-10 year-round; Alaska is UTC-9 standard, UTC-8 daylight saving; Puerto Rico and US Virgin Islands are UTC-4 year-round with no daylight saving
  8. Indiana General Assembly, Ind. Code § 24-4.7 – Indiana Telephone Solicitation of Consumers Law: Indiana restricts telemarketing calls to 9:00 a.m. to 9:00 p.m., one hour later than the federal start time
  9. Oklahoma Legislature, Okla. Stat. tit. 15 § 775A – Oklahoma Telephone Solicitation Act: Oklahoma restricts telemarketing calls to 9:00 a.m. to 8:00 p.m., tighter than the federal window on both ends
  10. Congress, 28 U.S.C. § 1658 – Limitations on civil actions: The general four-year federal statute of limitations under 28 U.S.C. § 1658 governs TCPA claims, driving the practical call-record retention period

Disclaimer: LeadCompliant is a compliance review tool, not a law firm. We do not provide legal advice. Consult with a TCPA attorney for legal guidance on specific compliance questions. Compliance scores, audits, and risk assessments are informational only.

LeadCompliant Team

LeadCompliant provides expert guidance and tools to help you succeed. Our content is reviewed for accuracy and kept up to date.

Related Articles

Related Glossary Terms

LeadCompliant
Build My Kit