How long your AI Agent waits for your calendar
When your AI Agent books appointments on a connected calendar, it has to wait for the calendar to respond. Some calendars take longer than others. Your AI Agent now waits up to 15 seconds for a response before treating a scheduling request as failed.
This fixes calls where a slow calendar caused the agent to tell a caller their booking didn't go through, even though the appointment was actually made. There's nothing to set up. The change applies automatically to every AI Agent that uses a connected calendar.
What's covered
The 15-second wait applies to every scheduling action your AI Agent takes:
|
Scheduling action |
Before |
Now |
|---|---|---|
|
Check availability |
10 seconds |
15 seconds |
|
List appointments |
10 seconds |
15 seconds |
|
Cancel an appointment |
10 seconds |
15 seconds |
|
List bookable services |
10 seconds |
15 seconds |
|
Book an appointment |
15 seconds |
15 seconds |
|
Reschedule an appointment |
15 seconds |
15 seconds |
It works with every calendar your AI Agent can connect to, including Google Calendar, Calendly, HubSpot Meetings, Outlook Calendar and Microsoft Bookings.
What callers hear
No hold music or sound plays while the agent waits for your calendar.
Frequently asked questions
Do I need to change any settings? No. There are no new settings, and you don't need to republish your agent. The longer wait applies automatically.
What happens if my calendar takes longer than 15 seconds? The agent treats the request as failed and lets the caller know it's having trouble reaching the calendar. If this happens often, check your calendar integration's connection in Settings > Integrations.
A caller was told their booking failed, but it's on my calendar. What happened? That could happen before this update when a calendar was slow to respond. With the longer wait, the agent now gets the confirmation in time.
Can I add hold music while the agent checks my calendar? Not at this time.