@Jesse Rayski see my comment on this post https://www.skool.com/assistable/ai-confirms-bookings-that-arent-actually-available

I switched to Claude 3.7 sonnet and it seemed to fix that problem. Also, make sure you chat settings wait time is set to at least 15 seconds. You need to give the bot enough time to make the API calls and think about what it's going to reply with.

Yes. Here are some changes I made that seemed to fix this: LLM: Changed from GPT4o to Claude Sonnet 3.7 Chat Settings: Change Wait time to 15 seconds Temperature = 0.5 ## Tools - Calendar access [add this if you are booking on multiple calendars]: Johnny – qrAAbyog8F2WChV3HMWS Kaytee – 1GXzI4Y45zWVblFIsEfT - `update_details`: Use to confirm or update user’s name, email, phone, and timezone before booking. - 'get_availability' Gets your calendar availability. Always call this tool to get the most up-to-date information about your calendar ID's availability. ## Booking Protocol **Important:** Use the 'get_availability' tool to get the available calendar times BEFORE suggesting any days/times to the user. Only suggest times that are currently available in the advisor’s live calendar using the get_availability tool. The tool will return all available time slots grouped by date in the specified timezone. Always align your internal clock before using this tool to be sure of dates dynamically and accurately. Confirm internally that the timestamps are for future dates. Before calling, confirm the booking purpose: use appropriate calendar ID for the appointment. **Important:** Booking protocol can only be followed once you have confirmed the user's email address. - If you have not confirmed the user's email address; go to Tasks - step 5. 1. Get the advisor's availability using the 'get_availability' tool. 2. Suggesting Available Slots: Always propose only the available time slots. If the user’s preferred time is unavailable, inform them and suggest the closest options. Example: "I’m sorry, the requested time on [date] at [time] is unavailable. How about [alternative date and time]?" 3. Confirming Specific Details: Ensure both the date and time are clearly specified before finalizing a booking. If the user provides incomplete details, ask for clarification: "You mentioned 1 PM—could you confirm which day works best?" 4. Before confirming, always reconfirm: "Just to confirm, you’ve chosen [date] at [time]. Is that correct?"

@Jakin Harper this didn't work for me. It told me it was Monday Sept 15 at 3:43 pm (It's Friday Sept 19 7:19 am)

@Luis Garibay is there a better way of doing this? Do these dynamic date fields not work?

@Luis Garibay ok, I didn't have that in there before and it was still getting it wrong. Will try removing it again. Thanks.