The two settings
“9am to 5pm” only means something once you know whose 9am. A lead in New York and
a lead in Los Angeles are three hours apart. With contact timezone on, “9am to
5pm” becomes their local 9 to 5, not yours.
What it changes
Turning on contact timezone does more than shift the calling window. The lead’s timezone flows into the whole call, so it changes three things at once:
That middle row is the one people forget. Even when two leads are dialled at the
same instant, the agent should say “good morning” to one and “good evening” to
the other. Contact timezone is what makes that right.
Where the timezone comes from
The setting reads the timezone stored on the lead’s contact record. A few things worth knowing:- If a contact has no timezone on file, that lead falls back to your business timezone.
- You can turn it on for a single campaign or for the whole project. If either one has it on, the campaign uses contact timezone.
- Turn it on whenever you dial across regions. Leave it off when all your leads sit in one timezone.
The timezone comes from the contact record. On a GoHighLevel sub-account, see
how GoHighLevel captures a contact’s timezone
for how that field gets set on forms and surveys. On one that keeps its
contacts here it is the contact’s
timezone, an IANA zone such as
America/Chicago; see
Contacts without a CRM.In the API
The setting ismultipleTimezoneCheck, a boolean in two places:
- On the campaign, set with Update campaign.
- On the project, set with Update project, as the default for every campaign in it. If either is on, contact timezone applies.
useWindowTimezone decides whether a calling window
is read in the timezone it declares or in the sub-account’s. It does not change
whose clock the contact is judged on; multipleTimezoneCheck does.
Every field above is defined in the Glossary.