Calling prospects in different time zones without breaking the rules

When calling prospects in different time zones, the contact’s local time decides, not your rep’s. US, Canadian and Australian rules all measure calling hours where the person is, so plan call blocks around each region’s window, check the number’s area code against the CRM address, and treat weekends and clock changes as rules of their own.

Whose clock counts: the contact’s

Every rule below is written in the called person’s time, checked against the regulator’s text in October 2026. Each has exceptions, for example for people who agreed to a call at a set time, so read the source before you rely on a row, and check with your counsel.

Country	Calling window, contact’s local time	What the rule says about time	Weekends
United States (federal)	8:00 AM–9:00 PM	“local time at the called party’s location” (47 CFR 64.1200(c)(1))	No days excluded in the federal rule
Canada	Weekdays 9:00 AM–9:30 PM	The hours “are those of the consumer receiving the telecommunication” (CRTC)	10:00 AM–6:00 PM
Australia	Weekdays 9:00 AM–8:00 PM	The time at the account-holder’s usual residential address (Industry Standard 2017, s. 8)	Saturday 9:00 AM–5:00 PM; no Sunday calls
India	10:00 AM–9:00 PM by default	Time bands from 9:00 PM to 10:00 AM are off by default (TCCCPR 2018)	None by default; subscribers can block days, holidays included

The US federal rule covers calls to residential and wireless numbers. India uses one time zone, so its window is the same across the country; its other rules are in our guide to TRAI telemarketing rules. For state rules, more countries and the B2B scope of each rule, see legal calling hours by country.

Area code or CRM address: which time zone to trust

A phone number tells you where it was issued. A mobile number travels with its owner, so a 212 number can belong to someone who now lives in Denver. The rules follow the person, not the number.

Australia’s standard spells this out. Its example is a call answered on a mobile in a different time zone from the account-holder’s home. If the caller learns that the person is away from home and it is a prohibited time where they are, the call must end at once, unless the person asks to continue (sections 8 and 13).

Use every signal you have, and when they disagree, call only in the hours that fit all of them.

Signal	What it tells you	Where it goes wrong
Area code or number prefix	Where the number was issued	People move and keep their mobile numbers
CRM address of the company	Where the office is	Remote staff, regional offices, head-office addresses
CRM address of the person	Where they work or live	Often missing or out of date
What the person told you	Their real location	Only after a first conversation; note it on the record

For example, a contact with a New York number and a Denver address is 2 hours behind New York. Under the US federal window, the overlap is 10:00 AM to 9:00 PM New York time, which is 8:00 AM to 7:00 PM in Denver. When a contact tells you where they are, record their time zone on the contact, so the next rep does not have to guess.

Plan follow-the-sun call blocks

A follow-the-sun schedule moves calling from region to region through the rep’s day, so each block falls inside the window of the region being called.

1. Split your lists by region, using the time zone you settled on above, not the area code alone.
2. Write each region’s window in your rep’s local time. For a contact window of 9:00 AM–8:00 PM, add or subtract the gap between the two time zones.
3. Put each block where the windows overlap with your rep’s working day. Leave a 30-minute buffer before each window closes, so redials and callbacks do not run past it.
4. Order blocks by when each window closes, so the region that closes first in your rep’s day comes first.
5. Redo the schedule when clocks change, in your rep’s country or the contact’s.

Clocks do not change on the same day everywhere. In the US, daylight saving time ends on the first Sunday of November, which is 1 Nov in 2026 (NIST). In the UK, clocks go back on the last Sunday of October, 25 Oct in 2026 (GOV.UK). For that week, the gap between London and New York is one hour shorter than usual. Some places do not change at all: NIST lists Hawaii and most of Arizona among them.

Weekends and holidays are separate rules

A window that works on Tuesday can be wrong on Saturday.

• United States. The federal rule sets hours but no excluded days. Check state rules for any state on your lists.
• Canada. Weekend calls are allowed from 10:00 AM to 6:00 PM, a shorter window than on weekdays.
• Australia. Saturday calls run from 9:00 AM to 5:00 PM, with no telemarketing calls on Sundays. There are no calls on 7 national public holidays, or on a weekday holiday given in lieu of one. State and territory holidays are not banned by the standard, but the normal hours still apply.
• The working week. Not every country works Monday to Friday. Check the local working week before you plan a block, even where the law allows the call.

A weekend can also be a different day for each side. A rep’s Friday afternoon in the Americas is already Saturday in Australia and New Zealand.

How DialSavvy handles this

DialSavvy compliance checks calling hours in the contact’s time zone before every call, from the rule pack for the country you are calling. The contact’s local time comes from their number, and reps see it on every row before they dial. Contacts outside their window are not dialed: they stay queued and come back when the window opens. Per-state US rules, which will use the area code and the CRM address, are coming, as are public-holiday calendars. See country coverage for the calling mode planned in each country.

Before next week’s calling, split your lists by region, write each window in your reps’ local time, and mark 25 Oct and 1 Nov on the team calendar.