Leads Dialing in the Wrong Time Zone: How to Fix It in VICIdial

If your dialer is placing calls too early in the morning or too late at night for the people it is reaching, the most likely cause is leads coded to the wrong time zone. This is not a cosmetic problem. Calling outside permitted local hours is a compliance risk, and it is also just a fast way to burn good leads with angry customers. The fix is methodical once you know how VICIdial decides each lead's zone.

VICIdial encodes a time zone onto every lead when it is loaded, and that zone becomes a GMT offset (lead) stored on the record. The dialer checks that offset against your calling-hour rules before placing the call. When the offset is wrong, the call happens at the wrong local hour. So fixing this is about fixing the encoding.

How leads get their time zone

The encoding is based on the phone_code, phone_number, and state fields, and it depends on the country. For the USA, Canada, and the Caribbean (phone code 1) and for Mexico (phone code 52), the first three digits of the phone number, the area code, drive the lookup, or optionally the zip code in the USA. For Australia (phone code 61) the state field is used. Every other country relies on the phone code itself.

The most common root causes

• Wrong or missing phone code. The number was loaded without the right country code, so the lookup had nothing to anchor to.
• Area code does not match where the person lives. Cell numbers move; an area code can point to a city the customer left years ago.
• The wrong lookup method for your data. Using area code when you actually have clean zip codes throws away accuracy.
• Daylight Savings not being maintained. Without the nightly script, leads drift out of sync when DST changes.

flowchart TD
  A[Lead loaded] --> B{phone_code valid?}
  B -->|No| Z[Zone set to 0 or wrong]
  B -->|Yes| C{Lookup method}
  C -->|Area code| D[Use first 3 digits]
  C -->|Postal code| E[Use zip]
  C -->|Owner code| F[Use owner field]
  D --> G[gmt-offset stored]
  E --> G
  F --> G
  G --> H{Inside call window?}
  H -->|No| I[Call held]
  H -->|Yes| J[Call placed]

Fixing it

First, fix the source data. Make sure every lead has the correct phone code before it goes in. If you have already loaded bad data, you can choose a better lookup method. For USA leads with good zip codes, postal-code lookup is more accurate than area code. If you trust your source's zone data, you can load the abbreviation into the owner field and use owner-code lookup. These method choices live both on the list and at load time; for the load-time side, see VICIdial lead time zone lookup.

Second, let the nightly recode run. The list-level Time Zone Setting controls the ongoing recoding method, and that process runs overnight, not instantly. Change the method, then wait a night for the leads to recode. For the list-level field, see the list statistics view, where the by-timezone breakdown shows you whether your fix worked.

Do not forget state rules

Time zone is not the only thing that gates a call. State-level rules are based on the lead's state field, not just the time zone. So a lead can have a perfectly correct offset and still be held by a stricter state rule, or dialed when the state field is wrong. Keep both the phone-derived GMT offset (lead) and the state field clean so your Call times and any state-specific DNC (do not call) handling line up. Every Lead you call deserves an accurate local clock.

Wrap-up

Wrong-time-zone calling traces back to bad phone codes, the wrong lookup method, or an unscheduled DST script. Clean the source data, pick the lookup that fits it, and confirm the nightly maintenance runs. For the full set of list and lead controls behind dialing, start with the VICIdial lists and leads guide.

On a managed VICIdial box the DST maintenance script is scheduled and watched for you, so your time-zone coding stays correct without manual cron babysitting. New dialers provision in under 40 seconds. See our pricing.