Hi VAPI team, I’m experiencing an issue with the Google Calendar integration. Specifically, the checkAvailability tool is not reliably preventing double bookings. The AI assistant is able to book appointments even when there's already an event scheduled for the same time slot. The assistant uses checkAvailability first, then createEvent if the time appears free Problem: Despite checking availability, the AI sometimes proceeds to book overlapping appointments. Either: checkAvailability is not detecting existing events as conflicts or The tool is returning empty or unclear data, and the assistant isn't correctly interpreting it In both cases, it leads to events being double-booked. What I Need: Confirmation that checkAvailability does check for conflicts with existing events Clarification on the expected output format so the AI can reliably validate open slots Any recommended adjustments or safeguards to ensure that an event is only booked when no conflict exists

Are you using the native check availability tool or make.com integration?

The checkAvailability tool does detect scheduling conflicts via a busy array, and to prevent double bookings, your assistant must explicitly verify that busy is empty, ensure consistent timezone formatting, handle edge overlaps with buffer time, and optionally re-check availability just before creating the event to catch last-minute changes or race conditions..

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!