cal.com
cal.com copied to clipboard
troubleshooter doesn't provide sufficient info
Is your proposal related to a problem?
The troubleshooter doesn't provide sufficient info to figure out what is blocking availability. It simply gives a list of busy times:

which on an account with multiple integrations / calendars doesn't help figure out where the bookings are coming from.
Describe the solution you'd like
For each booking, show the event title, and which integration / calendar it comes from.
Describe alternatives you've considered
Instead of showing a list of bookings, copy calendly's approach, and show a list of slots, and for each unavailable slot, an explanation of why it is unavailable:

This is probably better, because it can explain that slots are unavailable not just due to overlap with existing events, but also for other reasons, e.g. the slot is outside the standard working hours for the account, or it's too short notice to book that slot, or it doesn't leave enough of a buffer before the next meeting.
Additional context
Notice how much clearer calendly's date picker is. The cal.com one is really hard to spot:

Hi @aspiers, I will get this raised with our engineering team to see how we can improve this.
Thanks @ConnorGargano, much appreciated!
Hey @ConnorGargano any thoughts on this one?
the troubleshooter has been deprioritized and will get more attention after 2.0! 🙏
The troubleshooter is getting a major overhaul.
@keithwillcode Great to hear it's getting a major overhaul! In that case presumably there is another issue you can link to from here so we can follow that one? Otherwise it's a bit dissatisfying to see this acknowledged as an issue but closed with no further information on how to track progress.
And in that case, shouldn't this be closed as a duplicate rather than as "completed" or "not planned"? Neither of those statuses seem congruent with the good news that it's getting a major overhaul.
Thanks!
I elaborated a bit further on this topic of optimal communications in https://github.com/calcom/cal.com/issues/6729#issuecomment-1822727602.