The Federal Baseline and Why It's Not Enough

Ask ten business owners when it's "too late to call," and you'll get ten answers — but the law gives you exactly one. The federal baseline is clear: under the TCPA and the FTC's Telemarketing Sales Rule, telemarketing calls are permitted only between 8:00 AM and 9:00 PM in the recipient's local time, and any call outside that window is treated as prohibited under both federal regulation and the TCPA.

Here's the detail that trips up most businesses: the clock that matters belongs to the person receiving the call, not the person placing it. As compliance experts point out, the caller's clock is legally irrelevant, and area codes are an unreliable proxy for time zone because number portability means a 305 area code could ring in Seattle. Your dialer must enforce time zones by the recipient's actual location, derived from address or zip code — which is why compliance guidance recommends asking any calling vendor how they derive time zone and what happens when someone tries to dial outside the window.

The stakes are not theoretical. TCPA violations carry statutory damages of $500 to $1,500 per call, class actions routinely settle for millions, and some of the largest contact center operators have paid nine-figure settlements for non-compliant outbound programs. Class action settlements averaged $6.6M in 2023, and the FTC received over 2.6 million Do Not Call complaints in FY 2025 alone.

The real problem is that the federal window is a floor, not a ceiling. A growing patchwork of state "mini-TCPA" laws imposes stricter limits:

• Florida caps calls at 8:00 PM under the FTSA.
• Texas (SB 140, effective September 2025) allows calls only 9 AM–9 PM Monday–Saturday and noon–9 PM Sunday.
• Pennsylvania (SB 992, effective October 2026) limits calls to 9 AM–7 PM with no Sunday solicitations.
• Maryland and Oklahoma prohibit more than three telemarketing calls in 24 hours on the same subject.

That means a single multi-state customer list — say, a home services company with past clients in New York, Florida, and Texas — carries multiple enforceable calling windows at once, each with its own start time, end time, and day-of-week rules. Treating 9:00 PM as a universal cutoff is the fastest way to turn a win-back campaign into a liability.

This is why done-for-you outreach services like CallMyCustomers build calling-window enforcement into the campaign itself rather than leaving timing to agent discretion, since reactivation only works when the outreach lands legally — and at a moment the customer is actually receptive.

State-by-State Variations That Shrink the Window

If you run a multi-state customer list, the "latest time you can call" question has no single answer — the answer changes with every zip code you dial. A single contact list spanning New York, Florida, California, Texas, and Washington simultaneously carries at least five distinct enforceable calling windows, each with its own start time, end time, and day-of-week restrictions.

The federal baseline of 8 a.m. to 9 p.m. local time is just that — a baseline. State "mini-TCPA" laws layer stricter rules on top, and several states have tightened their windows in the last two years. Treat the federal window as a hard minimum, then layer in the state rules wherever they apply.

Here are the state restrictions that shrink the window the most:

• Florida cuts off at 8 p.m. The state's Florida Telephone Solicitation Act restricts calls to 8 a.m.–8 p.m. — a full hour earlier than the federal limit.
• Texas SB 140, effective September 1, 2025, sets calling hours at 9 a.m.–9 p.m. Monday through Saturday and noon–9 p.m. on Sundays. The same bill also allows texting violations to be enforced as deceptive trade practices.
• Pennsylvania SB 992, effective October 2026, limits calls to 9 a.m.–7 p.m. and bans Sunday solicitations entirely — the tightest window of the three.

Timing isn't the only state-level variable. Maryland and Oklahoma both prohibit more than three telemarketing calls in a 24-hour period on the same subject matter, so even a compliantly-timed call can cross the line if it's one too many. For businesses running win-back or renewal campaigns, these frequency caps matter as much as the clock.

The stakes for getting this wrong are real. Violating calling hours can trigger fines of up to $500 per violation, or $1,500 for willful violations, plus class actions — which averaged $6.6 million in settlements in 2023. Some of the largest contact center operators have paid nine-figure settlements for non-compliant outbound programs.

This is why calling window enforcement has to happen before the dial, not after. Area codes are not a reliable proxy for time zone due to number portability, and the caller's clock is legally irrelevant — enforcement must be based on the recipient's actual location. Platforms that batch-process overnight leave exposure gaps that agent discretion can't cover.

At CallMyCustomers, we build these state-by-state rules into every campaign from the start — recipient-location-based timing, frequency caps, and opt-out handling — so a customer list spanning multiple states gets one consistent, compliant approach. Every script and message is approved by the business owner before anything goes out, so the outreach stays useful, not pushy, no matter which state it lands in.

Why Area Codes Fail and Location Detection Must Be Precise

Area codes were once a reliable clue about where someone lives. Today, they're one of the fastest ways to accidentally call a customer at 10:30 PM — and end up on the wrong side of the TCPA.

The core problem is number portability. Americans keep their phone numbers when they move across the country, which means a 415 San Francisco area code might now belong to someone in Tampa. As compliance experts put it plainly, "the caller's clock is legally irrelevant, and area codes are not a reliable proxy for time zone due to number portability." The law measures the calling window by the recipient's local time — not yours, and not what their phone number suggests.

The stakes are real. TCPA calling-hour violations carry statutory damages of up to $500 per violation, or $1,500 for willful violations, and class action lawsuits routinely settle for millions — with some of the largest contact center operators paying nine-figure settlements. A single misdialed hour on a multi-state list can compound those numbers quickly.

So what does accurate recipient-location detection look like in practice? Compliance-focused systems derive time zone from what you actually know about the customer, not what their number implies:

• Service address or zip code from your CRM, point-of-sale, or booking records — the most reliable anchor for local time.
• Pre-dial enforcement, since quiet-hours rules under 47 CFR 64.1200(c)(1) make calling-window checks a requirement before the dial, not after.
• State-specific layering, because a list spanning New York, Florida, Texas, California, and Washington can carry at least five distinct enforceable calling windows with different start times, end times, and day-of-week rules.
• Hard blocking rather than warnings, so an agent can't manually place a call outside the window even by accident.

Some advisors suggest a fallback: if you can't determine location, only call between 11:00 AM and 9:00 PM ET, which covers every U.S. time zone. That's a reasonable hedge for cold data — but it shrinks your usable calling day and still doesn't address stricter state windows like Florida's 8 p.m. cutoff.

For businesses running reactivation campaigns, this is why working from a real customer list matters. When your outreach is built on actual service history, you already hold the address and zip code that make precise time-zone detection possible. That's exactly how CallMyCustomers approaches win-back and renewal outreach: campaigns run from your existing customer records, with calling windows enforced by recipient location before any dial goes out.

Accurate location data isn't a nice-to-have — it's the difference between a compliant evening call and a $500-per-call liability.

Texting, Consent, and the Hidden Compliance Traps

Most businesses know the federal window for calls is 8:00 AM to 9:00 PM local time, but fewer realize the same clock governs every SMS they send. The TCPA treats text messages identically to voice calls for timing purposes, and recent enforcement trends show regulators and plaintiffs' attorneys are applying that rule aggressively to texting campaigns that drift outside the window.

Texas just raised the stakes considerably. Under SB 140, which takes effect September 1, 2025, a text sent outside permissible hours isn't just a TCPA violation — it can be enforced as a deceptive trade practice, opening the door to treble damages and mandatory attorney's fees. The bill analysis makes clear the legislature intended to close the gap that let some marketers argue texts fell outside existing telemarketing law. For a business texting customers across state lines, that single provision changes the risk profile of every campaign.

• Federal baseline: 8:00 AM–9:00 PM in the recipient's local time zone for both calls and texts
• Texas SB 140: 9:00 AM–9:00 PM Monday–Saturday, noon–9:00 PM Sunday, with deceptive-trade-practice enforcement
• Florida FTSA: 8:00 AM–8:00 PM window, stricter than federal
• Pennsylvania SB 992 (effective October 2026): 9:00 AM–7:00 PM, no Sunday solicitations

Compliance with the clock, however, is only half the equation. Valid, documented consent is a separate prerequisite that calling-window compliance alone cannot satisfy. The FTC's Telemarketing Sales Rule explicitly states that unless a telemarketer has a consumer's prior consent to do otherwise, placing an outbound call outside 8:00 AM–9:00 PM local time is a violation — but even inside the window, the call or text is unlawful without proper consent. In FY 2025, the FTC received over 2.6 million Do Not Call complaints, and the National Do Not Call Registry contains more than 258 million registered numbers, underscoring how central consent and preference management remain to lawful outreach.

CallMyCustomers builds both requirements into every campaign: time-zone detection tied to the recipient's address or zip code — not area code, which is unreliable due to number portability — and a consent verification step that runs before any message leaves the platform. The owner approves every script and offer before launch, and opt-outs are honored immediately across all channels.

How CallMyCustomers Enforces Compliant Calling Windows

How CallMyCustomers Enforces Compliant Calling Windows

Before any outreach begins, CallMyCustomers applies a pre-dial enforcement architecture designed to eliminate compliance risk at the source. The system resolves each customer’s time zone in real time using verified address or zip code data, avoiding unreliable area code assumptions due to number portability. This ensures calling window checks are based on the recipient’s actual local time, a critical requirement under both the TCPA and TSR where violations can trigger fines of up to $500 per incident or $1,500 for willful offenses.

The platform layers federal and state regulations automatically, blocking calls outside the strictest applicable window — whether that’s the federal 8:00 AM to 9:00 PM baseline or tighter state limits like Florida’s 8:00 AM to 8:00 PM restriction or Pennsylvania’s 9:00 AM to 7:00 PM limit with no Sunday solicitations. These controls apply identically to voice calls and text messages, reflecting the growing enforcement focus on SMS timing under laws such as Texas SB 140, which permits texting violations to be pursued as deceptive trade practices. Every number is scrubbed against the National Do Not Call Registry using data updated within the past 31 days, as required by 16 CFR § 310.4 and 47 CFR § 64.1200(c), while consent verification confirms prior authorization before any outreach is queued.

• Real-time time-zone resolution from customer address data
• Automated blocking of calls outside the strictest applicable window (federal + state layering)
• DNC scrubbing within 31 days, consent verification, and identical controls for voice and text

By enforcing these rules before a single dial occurs, CallMyCustomers removes reliance on agent discretion and prevents exposure from batch-processing delays. This pre-dial approach aligns with expert guidance that calling window compliance must be built into the carrier-level connection process, not layered on afterward. For service businesses managing multi-state customer lists, this architecture transforms a complex regulatory landscape into a seamless, permission-based outreach engine — where timing isn’t just compliant, it’s respectful.