VICIdial Lead Time Zone Lookup Explained

VICIdial codes each lead to a time zone at load using phone code, area code, postal code, or the owner field — and checks daylight saving too.

Calling someone at the wrong hour is more than rude, it is often illegal. That is why VICIdial codes every Lead to a time zone the moment it loads, well before the dialer ever picks it. The system stores a GMT offset for each record, which becomes the GMT offset (lead) your call-time rules check against. Get this wrong and either your agents sit idle or you call people outside permitted hours.

The lookup methods

Country code and area code only — the default. Uses the phone code plus the first three digits of the number. It is also the fallback when any other method fails to find a zone.
Postal code first — USA addresses with a populated zip code, giving more accurate coding than area code alone.
Owner time zone code first — reads a valid TZ abbreviation like EST, CST, MST, or PST from the owner field.
NANPA area code prefix first — uses the optional NANPA database for the most precise North American lookup. Not included by default.

How the zone is chosen at load

flowchart TD
  A[Lead loads] --> B{Method chosen}
  B -->|Postal first| C[Try US zip]
  B -->|Owner first| D[Read TZ in owner field]
  B -->|NANPA first| E[NANPA prefix lookup]
  C -->|No match| F[Country + area code]
  D -->|No match| F
  E -->|No match| F
  F --> G[Check daylight saving]
  G --> H[Store GMT offset]

Under the hood the encoding leans on the phone code, the phone number, and the state field, and what it uses depends on the country. For Australia, with a phone code of 61, the state decides the zone and daylight saving scheme. For the USA, Canada, the Caribbean, and Mexico, the area code drives it, or the zip code in the USA if you chose postal-first. Every other country relies on the phone code alone, which is why a correct Phone Code Override on your import matters so much.

If a lead has no proper phone code, its time zone may be set to 0 or simply wrong, which can lead to calling outside legal hours. Always set the right phone code on every import.

Daylight saving stays current

Each lead is also checked for whether it observes daylight saving when it loads. Because the offset can shift twice a year, a small overnight script needs to run every early morning to keep the time restrictions correct when daylight saving flips. On a managed box that housekeeping is handled for you, so your call-time rules stay accurate without you thinking about it.

A practical tip: if some of your leads keep landing in the wrong zone, check the source data before you blame the lookup. Spelled-out states instead of two-letter codes, missing zip codes, or a phone code left blank are the usual culprits. The lookup can only be as good as the fields you feed it, so a few minutes spent standardising those columns pays off across every record. When the inputs are clean, the country-and-area-code fallback alone gets the vast majority of North American leads right, and the postal or NANPA methods tidy up the rest.

Time zone coding ties into the wider story of how lists govern who gets called and when. The VICIdial lists and leads guide connects the dots, and what is a VICIdial list covers the container these records live in.

Accurate time zones keep you compliant and keep agents busy. VICIfast provisions a hardened VICIdial server, with the daylight-saving housekeeping running for you, in under 40 seconds. Explore VICIfast pricing to start dialing the right hours.