Time zones and scheduling

Time zones aren’t unified across Get2Dial — each feature uses whichever one makes sense for it. This page is the complete list of which, and what each falls back to when one isn’t set. All are IANA time zone names (for example America/New_York), so daylight saving is applied automatically; none of this uses a fixed UTC offset.

Where each time zone comes from

Feature	Time zone used	Fallback
Business hours schedule	The time zone set on that schedule	None — required when you create the schedule
Calling-hours windows	The lead’s own time zone, from your lead list	The campaign’s Default time zone setting
Campaign Default time zone	Set on the campaign — see Campaign settings	`UTC` if you never set it
Campaign Max dials per day cap	The lead’s own time zone (same as calling hours)	The campaign’s Default time zone
Call detail records and Recordings timestamps	Your Timezone — Change your profile	Your browser’s detected time zone if you haven’t set one
Audit log timestamps	Your Timezone	Your browser’s detected time zone if you haven’t set one
Dashboards call-volume trend	Your Timezone	`UTC` if you haven’t set one
Scheduled reports send time	Always `UTC`	Not configurable — there’s no per-user or per-workspace override

Change your profile to set your own time zone.
Calling hours and business hours for the tasks that set a schedule’s time zone.

⌘I

Get started

Account and access

Voice connectivity

Inbound calls

Outbound and dialer

Agent workspace

Supervision and quality

Reporting and analytics

Compliance and trust

Troubleshooting

Reference

Time zones and scheduling

Where each time zone comes from

​Where each time zone comes from

​Related

Where each time zone comes from

Related