FTC Telemarketing Sales Rule 8 a.m. to 9 p.m. local time: what it means for your team

Last updated 2026-07-09

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

The rule is short and blunt. 16 CFR § 310.4(c) makes it an abusive telemarketing act for a seller or telemarketer to place outbound calls "to a person's residence at any time other than between 8:00 a.m. and 9:00 p.m. local time at the called party's location." ^[1]

That's the whole rule. No wiggle room for daylight saving transitions, no exception for high-ticket sales, no carve-out because the prospect handed you their number at a trade show. Dial a residence outside that window and you've violated the TSR.

The FCC's Telephone Consumer Protection Act regulations at 47 CFR § 64.1200(c)(1) carry the identical restriction for calls made using an automatic telephone dialing system or a prerecorded voice to residential lines. ^[2] So you're looking at two separate federal frameworks, both landing on the same hours. Miss the window and you potentially face exposure under both.

One thing people miss: the rule says "local time at the called party's location." Your dialer sitting in Phoenix does not get to run on Arizona time when calling a number with a New York area code. If the number rings in Albany, you use Eastern time, full stop.

Who does the FTC's calling-hours rule actually cover?

The TSR's time restriction applies to "sellers" and "telemarketers" as defined in 16 CFR § 310.2. A seller is any person who provides goods or services in exchange for consideration in a telemarketing transaction. A telemarketer is any person who initiates outbound calls or takes inbound calls in a telemarketing context. ^[1]

Here's the plain version. If you run an outbound sales floor that calls consumers to sell anything, you're covered. That includes third-party lead generation callers who dial on a seller's behalf.

Some call types sit outside the TSR entirely: calls to existing business customers where the seller has an established business relationship, purely business-to-business calls, calls by political organizations, and calls from nonprofits soliciting charitable contributions. But those exemptions apply to the TSR's full scope. Even if your call type is partially exempt, calling at 6 a.m. is a bad idea that invites regulatory attention.

The TCPA's calling-hours rule is narrower in one sense: it applies specifically to calls using an ATDS or prerecorded voice to residential lines, and separately to calls to cell phones. ^[2] Manual calls to cell phones sit in a grayer zone under the TCPA, though many state laws fill that gap. For your practical compliance posture, treat the 8-to-9 window as a floor for all consumer outbound calls, whatever the call type.

How do you determine the local time at the called party's location?

This is where teams actually trip. The standard is the time zone where the phone sits or, more practically, where the number is registered. For landlines, the area code and exchange prefix (the NXX block) map to a specific geographic rate center, and that rate center has a time zone. Mobile numbers get murkier because people keep their numbers when they move.

The FTC and FCC have not issued formal guidance on exactly how you must determine location for mobile numbers. The working industry approach is a real-time time zone lookup against the number's area code as a starting assumption, then a conservative buffer on top. If your data is old or you can't confirm where the number holder lives now, calling at 8:15 a.m. Eastern when the area code is 213 (Los Angeles) beats calling at 8:05 a.m. Eastern and betting the person never moved.

Several data providers sell NPA-NXX time zone databases you can wire into the dialer. This is a cheap fix. It's a standard feature in most modern predictive dialers. If your dialer doesn't do it, close that gap before the next campaign.

For cold calling operations with nationwide reach, the safest floor is simple: never dial before 8 a.m. Pacific and never after 9 p.m. Eastern. That covers the whole continental U.S. without any time zone math at the campaign level. You give up some early-morning East Coast hours, but you kill the risk.

What is the penalty for calling outside 8 a.m. to 9 p.m. under the TSR?

The FTC can seek civil penalties up to $51,744 per violation under Section 5(m)(1)(A) of the FTC Act, as adjusted for inflation. ^[3] Each individual call outside the permitted hours is a separate violation. If your dialer fires 200 calls at 7:45 a.m. before someone catches the time zone error, the arithmetic gets ugly fast.

In practice, the FTC goes after companies with patterns of violations rather than one-off errors. The agency uses administrative complaints, federal court actions, and consent decrees. FTC actions against robocall operations have included tens of millions of dollars in disgorgement alongside civil penalties, though calling-hours violations are usually one element among many. ^[4]

The TCPA creates private rights of action too. Under 47 U.S.C. § 227(b)(3), a consumer can sue for $500 per violation, or up to $1,500 if the violation was willful or knowing. ^[5] State attorneys general can bring suits on behalf of residents as well. That's why calling-hours compliance isn't a regulatory checkbox. It's litigation risk sitting in your dialer queue.

A cold call that goes out at 7:58 a.m. local time can put you on the hook for a TSR violation and a private TCPA lawsuit at the same time. That combination is what makes this worth real attention.

Violation type	Max penalty per call	Who enforces it
TSR calling-hours violation	$51,744	FTC (civil)
TCPA automated/prerecorded call to residential	$500, $1,500	Private plaintiff, state AG
TCPA willful violation	$1,500	Private plaintiff
State-level calling hours (e.g., Florida, California)	Varies; FL up to $1,500/call	State AG, private

Does the TCPA have the same 8 a.m. to 9 p.m. rule as the FTC's TSR?

Yes, with some nuance. The FCC's TCPA regulations at 47 CFR § 64.1200(c)(1) prohibit telephone solicitations to residential subscribers before 8 a.m. or after 9 p.m. local time at the called party's location. ^[2] The FCC defines "telephone solicitation" to include calls made to encourage the purchase of goods or services.

The TCPA's rule targets telephone solicitations to residential lines and automated calls broadly. The TSR targets telemarketing calls to residences. In most real-world outbound sales scenarios, both rules fire at once. You rarely get to pick which framework is inconvenient.

One practical difference: the TCPA creates that private right of action. A consumer who gets a robocall at 7:55 a.m. doesn't need the FTC to act. They can hire a plaintiff's attorney and sue your company directly. The TSR has no private cause of action (the FTC enforces it), but many states have folded TSR-style provisions into consumer protection laws that do allow private suits.

The FCC's 8 a.m. to 9 p.m. local time rule and the FTC's TSR calling-time restriction run parallel. Build one compliance system to satisfy both, because you face exposure under both.

Are there any exceptions to the 8 a.m. to 9 p.m. rule?

There is one meaningful exception in the TSR: express written permission from the called party to be contacted outside those hours. If a consumer specifically consents to calls before 8 a.m. or after 9 p.m., the restriction doesn't apply to those calls. ^[1]

This is real but narrow. The consent has to be clear, voluntary, and documented. You can't bury it in a terms-of-service checkbox nobody reads. And collecting that kind of explicit after-hours consent is complicated enough that most teams shouldn't bother. The risk of getting the documentation wrong outweighs a few extra calling hours.

There's no business-necessity exception. There's no exception for return calls where the consumer called you first (though some courts have found that calling back promptly at a consumer's request changes the analysis under common law). There's no exception for urgency or expiring offers.

Federal preemption deserves a line here. The TCPA expressly does not preempt state laws that protect consumers more. ^[5] Florida, California, and Indiana all have their own calling-hours restrictions, and some are stricter than 8-to-9. California's automatic dialing statute at Cal. Business and Professions Code § 17538.41 is one example. If you operate nationally, map state-specific rules on top of the federal floor, not instead of it.

How should your dialer or CRM be configured to comply with calling hours?

This is the operational piece most compliance guides skip. Let's be direct about what has to happen.

First, your dialer needs to know the time zone of the number it's about to call before the call fires, not after. That means a time zone field populated at import or a real-time lookup at dial time. Most enterprise dialers (Five9, Genesys, NICE, Aspect) do this natively. Many lighter sales engagement platforms do not. Check yours.

Second, build the 8-to-9 restriction as a hard block, not a soft warning. Soft warnings get clicked through. A hard block stops the call from firing when the current time at the destination falls outside the window. That requires the system to calculate destination-local time for each record at dial time, not batch-stamp records at import.

Third, build in a buffer. Most compliance-conscious teams I've seen run 8:05 a.m. to 8:55 p.m. local time, not right to the edges. Clock drift, system latency, and time zone database errors can shove a call a few minutes either way. A five-minute buffer costs almost nothing in volume and cuts your edge-case risk hard.

Fourth, log everything. When a call gets blocked by your time-zone rule, record that block with a timestamp and the destination time zone used. In litigation or an FTC investigation, showing that your system actively stopped out-of-hours calls is evidence of good faith.

LeadCompliant's free TCPA tools include a time zone compliance checker you can run against numbers before they hit your dialer. It's not a substitute for dialer-level controls, but it's handy for validating data imports.

For teams building out cold calling scripts or running AI cold calling platforms, confirm your vendor's compliance settings include time-zone-aware call blocking, more than a manual off switch.

Do these calling-hour rules apply to text messages and SMS?

The TSR as written covers telephone calls, not SMS. But the TCPA reaches text messages, and the FCC has confirmed that texts fall under the TCPA's prohibition on contacting wireless subscribers using an ATDS without consent. ^[6]

For TCPA-covered texts, the FCC's 8 a.m. to 9 p.m. restriction attaches to "telephone solicitations." The FCC's 2015 Declaratory Ruling confirmed that texts sent via an ATDS carry the same consent requirements as calls. Whether the time restriction applies to texts in exactly the way it does to voice calls hasn't been nailed down in a single binding rule, but multiple court decisions have applied the calling-hours framework to marketing texts.

The practical advice: apply the same 8-to-9 window to outbound marketing texts as to voice calls. No court has rewarded a company for arguing that 6 a.m. promotional texts were fine because the statute only says "calls." You'll lose that argument and pay for the creativity.

The CTIA, the wireless industry trade group, publishes messaging guidelines that recommend the same 8 a.m. to 9 p.m. window for commercial texts. Carriers enforce these through filtering and can deregister your short code or toll-free number. ^[7]

How do state laws stack on top of the federal 8-to-9 rule?

The federal 8-to-9 window is a floor, not a ceiling. States are free to be stricter, and a handful are.

Florida's Telephone Solicitation Act, significantly amended in 2021, restricts calls and texts to between 8 a.m. and 8 p.m. Eastern time, one hour tighter than the federal rule on the back end. Florida also allows private lawsuits with damages up to $500 per call or text, and up to $1,500 for willful violations. ^[8]

California's privacy statutes don't set different calling hours, but California's Unfair Competition Law and Consumers Legal Remedies Act create strong private rights of action that amplify liability for any underlying TCPA or TSR violation.

Indiana limits calls to 9 a.m. to 9 p.m. local time, starting an hour later than the federal rule. Arkansas restricts calls to 9 a.m. to 9 p.m. as well. Several states simply adopt the federal standard by reference.

Running a national campaign? The simplest operational move is to find the most restrictive combination of applicable state rules and apply it everywhere. It costs you some calls and kills state-by-state tracking errors. For teams with heavy Florida volume, running 8 a.m. to 8 p.m. local time for all records makes Florida compliance automatic.

Understanding what is cold calling in sales in the context of your specific geography matters here, because the legal framework shifts meaningfully by state.

What should you do if you realize you called someone outside the allowed hours?

Don't panic, but do act. Here's the sequence that matters.

First, stop the bleeding. Pull the campaign or the calling window right away. Make no more out-of-hours calls while you figure out the scope.

Second, document what happened. Pull the call logs, identify every call made outside the permitted window with timestamps and destination time zones. You need a precise count. That count helps your internal review and helps you in any future regulatory inquiry, where showing that you found and quantified the problem voluntarily works in your favor.

Third, find the root cause. A time zone database error? A dialer configuration mistake? A manual override someone shouldn't have had? Fix the specific failure point, more than a vague process.

Fourth, talk to a lawyer who handles TCPA and TSR matters before you contact consumers or regulators. If the FTC or a state AG reaches out, you want counsel involved from the first response. If a consumer's attorney sends a demand letter, same thing.

Fifth, decide whether proactive outreach to affected consumers makes sense. Some compliance attorneys advise a brief, factual apology with an opt-out confirmation and no admission of liability. Others advise silence. The right call depends on the volume of violations and your risk tolerance. This is a legal strategy question, not a blanket rule.

How does the FTC actually investigate calling-hours violations?

The FTC uses several detection methods. Consumer complaints filed at ReportFraud.ftc.gov and through the Do Not Call Registry complaint system pile up into patterns the agency watches. ^[9] A spike in complaints about early-morning calls from a specific company or call center throws a flag.

The agency also coordinates with the FCC and state AGs under information-sharing agreements. A state AG action can trigger FTC interest and the reverse.

When the FTC investigates, it usually opens with a civil investigative demand (CID), which is basically a subpoena for documents, communications, and data. Your call logs, CRM data, dialer configurations, and any compliance policies get requested. Clean records showing your time zone controls help you. No records plus a pattern of complaints is a problem.

The FTC's enforcement priority skews toward high-volume violations with bad patterns: robocall operations, repeat offenders, and cases where vulnerable populations (elderly consumers, for example) get targeted. That doesn't mean small teams are safe. One large campaign with widespread time zone errors can generate enough complaints to draw attention.

For context on what cold calling operations look like from the regulator's chair, the FTC's published complaint data and consent decrees are public and worth reading before you build your next campaign.

Frequently asked questions

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

The TSR says calls are permitted "between 8:00 a.m. and 9:00 p.m." at the called party's location. Calling at precisely 8:00 a.m. is technically within the window. Even so, a few minutes of buffer is wise, because system clocks, dialer latency, and time zone database rounding can push an intended 8:00 call to 7:58. Most compliance-focused teams start their dialers at 8:05 a.m. local time to stay clearly inside the rule.

Does the 8 a.m. to 9 p.m. rule apply to B2B calls, or only consumer calls?

The TSR's calling-hours restriction is written for calls to a person's residence. Purely business-to-business calls fall outside TSR coverage. But if you're calling a mobile number that doubles as a personal number, or reaching someone who works from home, the line blurs. The TCPA's residential restriction also focuses on residential lines. For safety, apply the window to any call where there's a reasonable chance you're reaching a personal or residential line.

What time zone applies if a person's mobile number has an area code from a different state than where they live now?

The rule says local time at the called party's location, not the area code's origin. If you know a person has relocated, use their current location's time zone. If you don't know and can't find out, the area code's time zone is the conventional industry default. Some compliance teams add a buffer at both ends of the day precisely to cover this uncertainty. No FTC or FCC guidance specifies an exact technical method for mobile numbers.

Does the calling-hours rule apply to ringless voicemail drops?

The FCC has taken the position that ringless voicemails (delivered straight to a voicemail system without ringing the phone) are covered by the TCPA as prerecorded voice calls. If that classification holds, the 8-to-9 window applies. This area of law is still contested, with some courts and industry groups arguing ringless voicemail is a different technology. Until there's a definitive ruling, apply the same calling-hours window to voicemail drops as to live calls.

Can a consumer consent to receiving calls outside the 8 a.m. to 9 p.m. window?

Yes. The TSR at 16 CFR § 310.4(c) allows outbound calls outside the permitted hours if the called party has given prior express permission. That permission has to be documented, voluntary, and specific about after-hours contact. In practice, collecting and maintaining this kind of consent is operationally complex. Most teams don't bother and just hold all calls to the standard window.

Is there a difference between the FTC's TSR calling-hours rule and the FCC's TCPA calling-hours rule?

Both land on the same 8 a.m. to 9 p.m. local time window, but they come from different statutes enforced by different agencies. The TSR is enforced by the FTC against sellers and telemarketers broadly. The TCPA is enforced by the FCC administratively and allows private lawsuits from consumers. You can face exposure under both at once. The private right of action under the TCPA is what generates most of the actual litigation.

What if a customer calls me back after 9 p.m. and asks me to return their call?

Returning a call at a consumer's specific, recent request puts you in a factually different spot than an outbound telemarketing call. Courts have generally not found liability when a business returns a call a consumer initiated. Document the inbound call that prompted the return. That said, some plaintiff attorneys will argue the return call is still subject to the restriction. If you're in doubt, call back the next day during permitted hours and document why you waited.

Do the federal calling-hours rules cover calls to Hawaii and Alaska?

Yes. The TSR and TCPA apply to calls to any U.S. state or territory. Hawaii is UTC-10 year-round (no daylight saving time), and Alaska is UTC-9 standard, UTC-8 daylight. If you're calling a Hawaii number from an East Coast dialer, 8 a.m. Hawaii time is 1 p.m. or 2 p.m. Eastern depending on the season. Your dialer needs to account for this. Many teams running national campaigns forget Hawaii and Alaska when configuring time zone logic.

How much does it cost to fix a calling-hours compliance gap?

For most modern dialers, enabling time zone-aware call blocking is a configuration change, not a purchase. If your dialer doesn't support it natively, third-party NPA-NXX time zone databases cost roughly $50 to $500 per year depending on the provider and update frequency. The operational cost is a few hours of setup and testing. That's a small number against the per-violation penalties, which run up to $51,744 under the TSR.

Can the FTC fine me for a single accidental call outside permitted hours?

Technically yes, each violation is separate under the TSR. In practice, the FTC spends its resources on patterns of violations and high-volume operations. A single accidental call is unlikely to draw an enforcement action by itself. What it can draw is a consumer complaint to the FTC and a potential private TCPA lawsuit, since the TCPA's $500 to $1,500 per violation structure gives plaintiff attorneys a reason to file even over small call counts.

Are there stricter calling-hour rules in any specific states I should know about?

Florida restricts calls to 8 a.m. to 8 p.m. local time under the Florida Telephone Solicitation Act as amended in 2021, one hour tighter than federal rules. Indiana and Arkansas both start their window at 9 a.m. rather than 8 a.m. If you're running high-volume campaigns into Florida, building an 8 a.m. to 8 p.m. floor for all Florida numbers is the safest approach. Check the specific statute for any state where you have substantial call volume.

Does the TSR calling-hours rule apply to text messages and automated SMS?

The TSR text is written around telephone calls to residences, not SMS. The TCPA and FCC regulations are what apply to texts, and the TCPA's calling-hours framework is generally applied to marketing texts by courts and industry practice. The CTIA's messaging guidelines specify the same 8-to-9 window for commercial texts. Applying the federal window to all outbound marketing texts is the defensible position and the practical industry standard.

Sources

1. FTC, 16 CFR Part 310 Telemarketing Sales Rule: 16 CFR § 310.4(c) prohibits outbound telemarketing calls to a residence 'at any time other than between 8:00 a.m. and 9:00 p.m. local time at the called party's location'
2. FCC, 47 CFR § 64.1200 Rules and Regulations Implementing the Telephone Consumer Protection Act: 47 CFR § 64.1200(c)(1) prohibits telephone solicitations to residential subscribers before 8 a.m. or after 9 p.m. local time at the called party's location
3. FTC, Federal Register Notice on Civil Penalty Inflation Adjustments (FTC Act § 5(m)): The FTC can seek civil penalties up to $51,744 per TSR violation as adjusted for inflation
4. FTC, News and Press Releases on Enforcement Actions: FTC enforcement actions against robocall operations have included tens of millions in disgorgement and civil penalties for patterns of TSR violations
5. Legal Information Institute, 47 U.S.C. § 227 Telephone Consumer Protection Act: 47 U.S.C. § 227(b)(3) allows consumers to sue for $500 per TCPA violation, up to $1,500 for willful violations; the statute does not preempt more protective state laws
6. Florida Legislature, Florida Telephone Solicitation Act (Fla. Stat. § 501.059): Florida's amended FTSA restricts telemarketing calls and texts to 8 a.m. to 8 p.m. Eastern time, with damages up to $500–$1,500 per violation
7. FTC, Report Fraud at ReportFraud.ftc.gov: Consumers file telemarketing complaints with the FTC through ReportFraud.ftc.gov; aggregate complaint patterns are used to detect enforcement targets
8. FTC, Do Not Call Registry Information for Businesses: The FTC's Do Not Call Registry complaint system aggregates consumer complaints about unwanted telemarketing calls, including calls outside permitted hours