Calling Windows and Time-Zone Management for Outbound Campaigns

The Federal Baseline: 8 AM to 9 PM Local Time

The FTC's Telemarketing Sales Rule establishes a baseline calling window of 8:00 AM to 9:00 PM in the called party's local time. "Local time" means the time zone of the number being called — not your call center's time zone, not your CRM's default time zone, not the time zone of the list vendor.

This is not a technical gray area. The FTC has brought enforcement actions specifically tied to calls made outside permitted hours. At $51,744 per violation (the current maximum civil penalty for TSR violations), a predictive dialer that fires 3,000 calls at 7:45 AM local time across a multi-state list can generate substantial exposure before anyone notices.

State Laws That Tighten the Window

Several states impose calling windows stricter than the federal baseline. Some examples your counsel should verify against current law:

• Florida: Telemarketing calls restricted to 8 AM–9 PM, but certain state-specific rules may be broader
• Alabama: Some interpretations restrict to 8 AM–8 PM
• California: 8 AM–9 PM per state law, though various local interpretations apply
• Colorado: Telemarketing restricted to 8 AM–8 PM weekdays; 9 AM–6 PM Sundays; no calls on specific holidays

The conservative approach is to compile state-specific calling window restrictions for every state your campaign will reach and apply the strictest applicable standard. If a state restricts to 8 PM, cap it at 8 PM regardless of the federal 9 PM ceiling.

Time-Zone Determination: The Technical Problem

Knowing a number's time zone is harder than it sounds. Area codes do not map reliably to time zones — a 212 number can belong to someone who has ported it and moved across the country. The correct approach is:

1. Use an LRCA/LERG lookup or wireless carrier data to identify the number's current rate center or registered location at the time of dialing
2. Map that location to the correct time zone, accounting for daylight saving time transitions
3. Compare the current time in that zone against your permitted window before dialing

This should happen at dial-time, not when the list is loaded, because time zones change relative to wall-clock time (daylight saving transitions) and because lists age — a number's rate center may have changed since the list was compiled.

How High-Volume Dialers Should Handle This

For predictive and power dialers running hundreds or thousands of concurrent lines, time-zone enforcement needs to be a system-level gate, not a manual check. Architecture approaches include:

• Enriching contact records with time-zone data during list import and updating at regular intervals
• Implementing a pre-dial check that compares current UTC to the permitted local window before each call attempt
• Logging the local time at point of dial for every call, capturing it in the CDR export

Exportable CDR data that includes the dialed number, the timestamp of the call in UTC, and the geographic destination of the call gives you the raw material to audit whether your time-zone controls functioned as designed. See our post on audit trails for how to structure that review.

Business vs. Consumer Considerations

The FTC's calling window rules under the TSR apply to telemarketing calls. Business-to-business outbound calling for non-telemarketing purposes may not be subject to the same restrictions — but this depends on the nature of the call and state law. If your B2B list includes cell phone numbers for business contacts (common for SMB outreach), those numbers may trigger consumer-facing rules even when the call is substantively B2B.

Consult your counsel on how to classify your specific campaign type before relying on any B2B exemption.

Connecting Time-Zone Management to Caller ID

Time-zone compliance pairs with local caller ID strategy. Calls that display a recognizable geographic caller ID matching the called party's region tend to have higher answer rates — but provisioning caller IDs in every relevant market is operationally complex on per-minute SIP trunking. UnlimCall provisions caller IDs on demand across 33 live markets so your outbound number can reflect the correct geographic context at dial time, not just a random trunk number.