Why an external-phone agent needs the right Local GMT setting

The Local GMT field on a VICIdial external phone record is the numeric UTC offset for the Agent's physical location. VICIdial uses it to evaluate whether the agent is within permitted Call times and to timestamp activity in reports. If the offset is wrong, the system applies call-time restrictions based on a time that does not match the agent's actual clock — blocking calls that should be allowed or, worse, allowing calls during restricted hours.

What the field controls

VICIdial enforces Campaign call-time windows based on local time. When computing local time for an agent, the system reads the Local GMT value from their phone record and adds it to the server's UTC clock. An agent in New York in winter is at -5. If their record says -4, VICIdial thinks it is an hour later than it really is at the agent's location, and every call-time check for that agent is off by that margin.

For outbound Campaign operations where legal calling hours are tightly regulated, a one-hour error in Local GMT is a compliance risk. TCPA rules in the US restrict calls to between 8am and 9pm in the called party's local time. An agent-side timezone error does not affect the called party's timezone, but it can disrupt routing logic that depends on agent availability windows lining up with permitted hours.

The no-DST gotcha

The Local GMT field is a fixed numeric value. It does not update automatically when Daylight Saving Time begins or ends. If an agent is in the US Eastern timezone, they operate at -5 in winter (EST) and -4 in summer (EDT). When the clocks spring forward in March, the phone record still says -5 unless someone updates it. VICIdial will not detect the transition and will not adjust on its own.

How the offset feeds time handling

flowchart TD
  A["Agent logs in"] --> B["VICIdial reads Local GMT from phone record"]
  B --> C["Computes agent local time = server UTC + Local GMT"]
  C --> D{"Agent local time within campaign call-time window?"}
  D -->|"Yes"| E["Calls allowed to bridge to agent"]
  D -->|"No"| F["Agent blocked from receiving calls"]
  B --> G["Local time stamps agent activity in reports"]
  G --> H["Wrap-up times and session logs reflect agent-local clock"]

Setting the correct value

Use the agent's standard UTC offset for their timezone at the current time of year, expressed as a signed number. UTC offsets are negative west of UTC and positive east. Common US values: EST = -5, CST = -6, MST = -7, PST = -8. During summer Daylight Saving Time, add 1 to each: EDT = -4, CDT = -5, MDT = -6, PDT = -7.

The field accepts decimal values for half-hour and quarter-hour offset zones. India Standard Time is +5.5, Nepal is +5.75, and so on. Enter only the number — no letters, no timezone abbreviations, no UTC prefix. Just -5 or 5.5 as a plain numeric value.

Keeping records current across a distributed team

For teams with Remote agent staff across multiple timezones, build a recurring calendar reminder to audit Local GMT values on all external phone records before each DST transition takes effect. The transition dates differ by country, so check each agent's jurisdiction separately. A simple admin query filtered by phone type = external gives you the list to review. Getting this right consistently is especially important for any Blended dialing campaign that combines inbound and outbound work, because agent-availability windows affect how the dialer paces outbound calls.

For the full external phone record setup, see how to run a VICIdial agent on a home phone. The remote agents guide covers how all the external phone fields work together. If you want a managed VICIdial server without managing infrastructure yourself, see our pricing plans — up and running in under 40 seconds.