Hi, I'm using Gohighlevel availability checking tool in one of my vapi assistant. It was correct when we launched. Now it's giving incirrect day of the week while checking availability. It's saying July 23rd is Tuesday, but it's Wednesday. It's saying dates 1 day behind of the actual date. How to fix it? @Vapi

add this to your prompt - {{"now" | date: "%A, %B %d, %Y, %I:%M %p", "America/Detroit"}}

really struggling with this too...It only correctly sends the dates if the user speciifes an exact date, but if the user has a relative date (i.e. "next monday") then it doesnt work. Here's my prompt: You are a helpful and efficient scheduling assistant. Your primary goal is to book appointments for users. Follow these steps carefully: 1. **Gather Information**: Start by asking for the caller\'s email address. 2. **Check Existing Contact**: Use the

ghl_contact_get

tool to see if a contact already exists with the provided email. 3. **Create Contact (if needed)**: If no contact is found, use the

ghl_contact_create

tool to create a new contact with their name and email. 4. **Discuss Appointment Time**: Once you have a contact ID (either from an existing contact or a newly created one), ask the user for their preferred date for the appointment. 5. **Check Availability**: Use the

ghl_check_availability

tool to check for open slots. It\'s a good idea to check for the entire preferred day to offer alternatives if their initial request isn\'t available. 6. **Confirm Time**: Discuss the available options with the user and agree on a suitable time. 7. **Book Appointment**: Finally, use the

ghl_create_event

tool to book the appointment, ensuring you use the correct contact ID. Important Guidelines: * Always use

ghl_contact_get

to check for an existing contact before attempting to create one with

ghl_contact_create

. * You must have a contact ID (from

ghl_contact_get

or

ghl_contact_create

) before you can book an appointment with

ghl_create_event

. * Always confirm availability with

ghl_check_availability

before attempting to book an appointment with

ghl_create_event

. * For relative dates like "next monday", use Today's date is {{\"now\" | date: \"%A, %B %d, %Y, %I:%M %p\", \"America/New_York\"}} and then look for the the relative date

Regenerating timestamps fresh using startOf('day') and endOf('day') in the correct timezone, and always confirm parsed dates with the user before checking availability..

I'm using this inside system prompt: ## Current Time in EDT {{ "now" | date: "%b %d, %Y, %I:%M %p", "US/Eastern" }} Is it correct?

Yes, your syntax is almost correct, but use "America/New_York" instead of "US/Eastern" for reliable timezone formatting.

Done that but it's still giving the same issue.

check for duplicate timezone settings in your assistant (only one should exist), restart the assistant to clear cache, and if it persists, share your recent call_id..

Here is one recent call id: e9597c7b-37c4-4dce-a9fe-ef4c8a4e368e Assistant system prompt attached as text file. Only one timezone is there in the assistant system prompt. In my Gohighlevel subaccount, the timezone is GMT-04:00 US/Eastern (EDT). Is it causing issues? https://cdn.discordapp.com/attachments/1395063558785466378/1395656666502004818/message.txt?ex=687b3e0f&is=6879ec8f&hm=f8a03ba5af421f2b05b45d67e27df824004c435dc53195c9a507b4b6c52fa860&

Hey Subhadip, I sincerely apologize for the delay in our responses this week. We experimented with some process adjustments that didn’t work as intended, and unfortunately, this caused some disruptions. That’s entirely my responsibility. Just a quick note—our team is unavailable on weekends. However, if something urgent or critical comes up, feel free to reach out to me directly, and I’ll assist you. The support issues will be resolved in the coming weeks, and starting Monday, you can expect more consistent and improved support. Thank you so much for your patience and for continuing to stick with us!

Sure, waiting for it. Thanks for the update

Looking into it

Hi @Kings_big💫 @Shubham Bajaj , any update on this?

Also try using {{date}} instead. We had one user with GHL using this which may point to a formatting issue, but please give it a try and let us know what the results are.