Perhaps. It keeps sending really weird
# general-english
l
Perhaps. It keeps sending really weird timestamps. In the latest one in sent timestamp for Sunday June 8th to Monday June 9th. Even though I asked it for times on June 6th.
h
looks like you are using HL, dont have the LLM do time conversions to Unix, even if you ask chat gpt to convert it will get it wrong
instead send the date in iso, I put this in the description for the tool -The day must be a date in ISO 8601 format EG: 2025-12-28 (do not include time zone in start date)
then format it in your server to do the request
my tool just sends start date and timezone in IANA format eg: America/Chicago
then I format to x , set hours to 8, for end date i just add 12hrs to start date. I used to use the same x for start and end but HL is wonky, so to make it more reliable I set hours to beginning of day and set end date 12hr after
I just have it check 1 day at a time, easier for the assistant to read slots "what day works for you?" check that day
l
Thanks @Ham After a lot of playing around. I just went a different route and now I am giving all of avaliable times for booking to the Agent when I make the call. That is giving consistent results instead of live calling GHL to get avaliablity.
Because this is actual bookings of customer, we couldn't take the risk of wrong demo times being booked.
Yes GHL time parameters are a mess. You get appointments in millsecond timestamps but you need book using ISO format.
They should use a single date format across.
5 Views