availability-inspector

Calendar availability shows no slots when a rep's calendar has blockers like disconnection, missing working hours, meeting limits, or being fully booked. The Availability Inspector queries the availability-slots API and interprets the failures map to surface the exact root cause.

To diagnose team calendar blockers, run an availability check against the distribution to identify which specific attendee is blocking the slot. The Inspector supports team-level checks and highlights the individual causing the scheduling failure.

Checking calendar availability requires meetingTypeRef.id, expectedHost, attendees with type and required flags, and an interval. The Inspector uses this input shape to produce a per-day slot breakdown and diagnose working-hours alignment across the lookahead window.

To translate calendar scheduling failures into fixes, interpret the availability-slots failures map to identify issues like unconnected calendars or meeting limits. The Inspector converts these calendar blockers into human-readable diagnoses with concrete remediation steps.

Yes, you can see a per-day breakdown of available slots across the lookahead window, including zero-slot days. This reveals patterns in working hours and recurring calendar blocks to help pinpoint when availability drops to zero.

Common calendar blockers that prevent scheduling include the calendar not being connected, no working hours configured, querying outside working hours, hitting meeting limits, or the rep being fully booked. The Inspector identifies these specific failures from the availability map.