Trying to set up ghl_check_availability tool, the assistant cannot properly convert the date/time asked by the user to proper format when the user asks for a relative date. Working example: Hi assistant, look for dates avauilable on 2025-07-21 Not working example: hi assistant, look for available dates next monday. 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: Gather Information: Start by asking for the caller's email address. Check Existing Contact: Use the ghl_contact_get tool to see if a contact already exists with the provided email. 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. 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. 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. Confirm Time: Discuss the available options with the user and agree on a suitable time. 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

@Al it already converts the time into Unix MS. What is the actual error.

the call to the tool is: { "timeZone": "America/New_York", "startDate": 1721083200000, "endDate": 1721169599000 } and the response is: [ { "type": "text", "text": "No available times found for the specified timeframe." } ] Clearly, as the dates are for last year...

@Al and that time is for sure available in your calendar?

All of Monday the 21st is open

You can hop on call?

Hey Al, I wanted to let you know that we're managing a high volume of support requests at the moment, so our response time might be a bit slower than usual. I truly appreciate your understanding and will get back to you as soon as possible!  Thanks again for your patience!

Where you able to solve this?

Hey AI, 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!

I was able to solve this by giving the assistant more clear instructions to calculate the date/time. My prompt looks like: booking flow 1- confirm today’s date with the end user using {{date}} 2- ask for the desired date. If it’s a relatively date like “next Monday”, use today’s date of {{date}} to calculate it 3- …

Nice work. It seems that GHL may not be able to read certain date formats, but accepts just plain {{date}} is what I'm taking away from this. Let us know if you need additional support

What will it take for you guys to up date the MCP and stop using Get Contacts and Use Search?

Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team