Contact Timezones
L
Len Cummings Digitisory
At the moment, the timezone of the contact is directly linked to the ip address of the person who uploaded the csv or the timezone of the account. Please can you separate them. Otherwise if you have contacts in different timezones they all get set to the same timezone. Automations get sent out in the middle of the night instead of first thing in the morning. Perhaps link the timezone to the address, postcode, country or state (for the US) . The current situation is atrocious.
Log In
C
Cameron Smith
this is easily fixed with code to set the time zone by state after the contact is created, but its standard HL to make you do this kind of stuff.
If you do a contact search with API you cant even get the contact timezone, so you create a custom field to copy the timezone into so it shows up in the search but when you do that it changes from America/Chicago to CDT. So its not even the correct timezone when daylight savings changes. So you need to write code to change it back to America/Chicago.
Then when you want to search for available slots on the calendar they want the date in x format (1748991600000) and the timezone separately in IANA format eg: America/Chicago but when you book an appointment they want the start time in in ISO8601 Format with timezone offset eg:
2025-06-23T03:30:00+05:00
Its like they had 4 people programing this stuff and none of them even talked to each other.
C
Caroline Binnion
Apparently this still isn't resolved. 3 years later. What is this dev team/leadership doing?? How is this not a priority?
Curious if anyone has found a work around for now. I asked support and they said no work around other than updating each contact manually LOL. We upload 400+ contacts/day....not feasible for us.
R
Rhys Templeman (admin)
This has been in request for TWO YEARS with no solution??!! And it's a core capability requirement of a CRM system....
J
John Betterr
just did an auto-sub account creation through Pabbly, I'm in MDT, the client is in EDT, and the timezone assigned was PDT.
J
John Betterr
What CRM adds a timezone to a contact that is hours different from the city/state/country of that contact?
Worse... what crm company treats this as a feature request that needs to wait in line?!
GHL treating this as a feature request instead of as an urgent issue that needs to be fixed immediately.... says a lot about GHL.
GHL = money before quality.
Toyota = quality before money
Both philosophies can make grundles of money. So why would anybody choose the GHL path instead of the Toyota path?
Instead of "buttoning up" all the issues it has, it keeps spreading itself thinner and thinner with more features. This is my #1 gripe about GHL. They invest in customer service rather than creating user experiences that are intuitive, easy and just work. Customer service, is always, always a stop gap. It is never, ever a solution. A quality first mindset is sorely missing in GHL culture.
Here is how this happens...
GHL is "money first." This will always result in a subpar experience. For exmpale, agencies and users don't even realize how slow and difficult to navigate GHL is. It has to be bottom 10% for all CRMs. Agencies are literally selling a bottom 10% CRM... Why? Because they too are money first.
Crap products win in the market all the time, if the money is flowing.
But it is a stupid choice to be money first, when quality first can make you just as much money!!!!!
If you're mostly about the money, then you don't complain. If you're about the user experience, you will find you can't stop complaining about GHL.
I think what will happen is those of us who care about the user experience... something better will come along that is quality first, and we will leave GHL.
D
Derek Fox
How can this even be a think come one guys we need this fixed asap
P
Pallavi Kothari
Merged in a post:
Show The Correct Country & Time Zone Based on Contact's Browser / IP Address (To Prevent Misinformation)
R
Raelyn Tan
I'm collecting leads and customers from the opt in forms and order forms in GHL.
HOWEVER, all my contacts' country and timezone (wrongly) defaults to my sublocation's country & timezone - Singapore - when the lead actually comes from somewhere else (US, Canada, anywhere else in the world...).
I can change it manually and remove "Singapore" one by one but its not very sustainable at scale. The correct & best way would be for GHL to auto-detect where the lead is located from their IP or something and pull in the correct country and time zone.
This change will help to prevent misinformation where I keep thinking a lead is local when he/she is not.
Ideally, want it to auto-populate with the contact's country & time zone from their browser when there is no data. But at the very least, if that's not possible, for it to show as BLANK when the data is missing and not the sublocation's country.
This info is already available in the API so its an easy fix i presume.
P
Pallavi Kothari
Merged in a post:
Collecting Lead TIMEZONE
J
Jay Phillips
The system does not pick up the leads timezone automatically like most other CRM's. This means that nearly all contacts get assigned the accounts timezone. This is a major issue and needs fixing. Should be able to do this easily from the IP address's
Justin Buswell
this could be the stupidest think I have ever heard of for a CRM. Set by the IP of the person who uploads the contact. Unbelievable.
J
John Betterr
Justin Buswell Far FAR stupider that an issue is being treated as a feature request. This says GHL has major issues when it comes to using its resources to create a quality product. New features with a lot of votes, are beating out quality. Now multiple this times 1000 for GHL.
They need to stop chasing new features, for just a month.
J
Jeff Kelly
Set the timezone automatically based on the country/state-territory.
Load More
→