Why isn't that slot showing up? Introducing the availability troubleshooter
A new view that tells you exactly why a given time slot is — or isn't — appearing on your booking page, so you stop guessing and start shipping fixes.
Every scheduling product eventually collides with the same support ticket: "Why can't my invitees book Tuesday at 3pm?" The answer is almost always some interaction between calendars, working hours, event durations, buffers, date overrides, and team round-robin rules — a stack of settings that individually make sense and collectively become a black box.
Until now, the honest answer from us was often "let's get on a call and walk through your settings together." That's not a great answer. So we built something better.
What we shipped
The availability troubleshooter lets you inspect why specific time slots are or aren't showing on your booking page Troubleshoot Your Availability. Instead of reverse-engineering your own configuration, you open the troubleshooter and see the underlying reasoning for each slot on a given day — whether it's blocked by a calendar event, falls outside your working hours, is consumed by a buffer, or is simply available and ready to book.
It's the same mental model our support team has always used internally, now exposed directly to you.
Why this matters
Booking pages are trust surfaces. When a customer, candidate, or client hits your link and sees the wrong hours — or worse, no hours — the cost isn't a support ticket, it's a lost meeting. The faster you can answer "is this configured the way I think it is?", the faster you can trust the link you're about to send.
We also expect this to shorten the feedback loop when you're setting up something complex: a new event type, a team round-robin, a schedule with overrides for a specific week. Instead of publishing, opening an incognito window, and clicking around your own booking page to sanity-check, you can inspect the slots directly.
What's next
This is the first cut. We're planning to expand the troubleshooter to cover more of the edge cases that show up in team scheduling and multi-calendar setups, and to surface suggested fixes inline rather than just diagnoses. If you hit a slot the troubleshooter can't explain clearly, tell us — those are exactly the cases we want to close next.