Troubleshooting revamp

What we will add

  • Showing ALL reasons, not just 1

  • Adding fix link, so they can fix issues

  • No slots available, troubleshoot to see why? link

  • For round robin/ multi-host look at all reasons as one on one

  • For round robin/multi-host show common reasons on top, and host level reasons below

  • Under questions about slots, let's show. Still not able to figure out the issue, chat with us. Opens NeetoChat

  • Showing full day blockers first with, Whole day not available due to, reasons, See individual slots.

  • Booking limit separation for scheduling link and host

  • Treating internal and external meetings differently, View button for internal meetings

  • Show why slots are available - for availability override & external events which are free

  • New reason for duration exceeds availability

  • Group meeting filled reason

  • Date range exceeded reason

  • Revamped precedence order for availabilities.

To consider adding in future

  • Share-able troubleshoot link to share with customer support.

Reasons why slots are not available with precedence.

  1. Viewing in different timezone

    Compare scheduling link page timezone with profile timezone of team member, if different show modal. If timezone changed, modal disappears, or will disappear on clicking Continue anyway.

    Title: View slots in a different time zone?

    Description: You're viewing slots in {{selected_timezone}}, but your profile is set to {{profile_timezone}}. We recommend switching to your profile time zone to avoid confusion during troubleshooting.
    Action items: Switch, Continue anyway.

    Switch, will change the timezone to the profile time zone. Should we add this or let them manually do it.

  2. Slot is in the past

    Grey out all slots, but show as it was - whether available or unavailable.

    If unavailable, mention the reasons.

    Do we show unavailable only? Proposing not to.

    Title: Past

    Message: Slot is in the past, but was available / Slot is in the past, but was unavailable due to the below reason(s)

  3. Date range exceeded

    Grey out all slots, mark all as unavailable.

    Currently, not clickable via troubleshooting. Once clickable, should we show slots or block out whole day?

    Title: Date range

    Message: Slot is outside the date range set for this scheduling link

    Fix link redirect to /where

  4. Holiday

    Grey out all slots, mark all as unavailable.

    Currently we don't show slots, we block out the whole day. Should we show slots or block out whole day?

    Title: Holiday

    Message: This day is marked as a holiday for {{holiday_name}} in NeetoCal

    Fix link redirect to /admin-panel/general/holidays

  1. Outside host's availability

    Grey out slots outside the availability, mark all as unavailable.

    Currently we don't even show these slots

    Title: Host unavailable

    Message: Slot is outside {{host_name}}'s availability {{availability_name}}

    Fix link redirect to /host/self/availability/{id} - Only show fix link if host is troubleshooting or if admin.

  1. Availability override

    Mark as unavailable.
    In the case of override we will not mention this reason for unavailable slots outside the original availability. We will only mention this reason for unavailability for slots inside the original availability, which is not unavailable due to override.

    For cases where slots are now available outside the original availability we will show info icon with reason why it's available.

    Currently we don't even show these slots

    Title: Override

    Message: Slot is unavailable due to override in {{host_name}}'s availability {{availability_name}}

    Fix link redirect to /host/self/availability/{id} - Only show fix link if host is troubleshooting or if admin

  1. Lead time

    Mark as unavailable.

    Title: Lead time

    Message: Lead time of {{lead_time}} prevents this slot from being available

    Fix link redirect to /where

  2. Meeting limit for scheduling link

    Mark as unavailable.

    Currently, same message for scheduling link and host limits

    Title: Limit

    Message: Daily/Weekly/Monthly booking limit of {{limit_no}} has been reached for this scheduling link

    Redirect to /settings/limit

  1. Meeting limit for the host

    Mark as unavailable.

    Currently, same message for scheduling link and host limits

    Title: Limit

    Message: Daily/Weekly/Monthly booking limit of {{limit_no}} has been reached for {{host_name}}

    Fix link redirect to /host/self/booking-limits - Only show fix link if host is troubleshooting (v1)

  2. Group meeting limit reached

    Mark as unavailable.

    For group bookings when the group limit has reached we say. "Maximum number of bookings has reached for this slot". This is not accurate.

    Use "Maximum group size has been reached"

    Title: Max group size

    Message: Meeting duration extends past {{host_name}}'s availability {{availability_name}}

    Fix link redirect to /what

  1. Duration exceeds availability

    Mark as unavailable.

    Currently, we are not showing the slots.

    Title: Duration

    Message: Meeting duration extends past {{host_name}}'s availability {{availability_name}}

    Fix link redirect to /host/self/availability/{id} - Only show fix link if host is troubleshooting (v1)

  1. Overlapping meetings

    Mark as unavailable.

    Currently, we don't handle meetings made in NeetoCal(internal) vs external events any differently, but doing so we can add additional information such as client name for internal meeting. Calendly treats them separate.

    Also we don't show conflicts in the past, should we handle it?

    Title: Conflict

    Message: Conflict with Google/Outlook/iCloud calendar event {{event_name}} on calendar {{calendar_name}}

  2. Buffer time

    Case 1: External event has buffer, but this scheduling link does not

    Mark as unavailable.

    Title: Buffer

    Message: Blocked by {{buffer_time}} buffer before/after event {{event_name}} on calendar {{calendar_name}}

    Case 2: External event does not have buffer, but this scheduling link does

    Mark as unavailable.

    Title: Buffer

    Message: Cannot satisfy the before/after buffer of {{buffer_time}} required due to event {{event_name}} on calendar {{calendar_name}}

    Fix link redirect to /host/self/availability/{id} - Only show fix link if host is troubleshooting (v1)

  3. Multi-host/Round-robin

    We show all of the above reasons on a host level for every slot.

    For round robin, slot is available even if 1 host is available. With no i icon.

    For round robin, even if available, allow to see the reasons per host.

    In case of common blockers like lead time, holiday, scheduling link limits, date in past, date range exceeded. We show it on top as it's common, and not under any host.

For group bookings when the group limit has reached we say. "Maximum number of bookings has reached for this slot". This is not accurate.

Use "Maximum group size has been reached"

Round-robin, Multi-host

  • Lead time is not shown

  • Holiday is not shown

  • Limit is not shown





Responses from AI

Order of precedence

  1. Slot is outside host's availability

  2. Availability override

  3. Holiday marked

  4. Meeting limit has been reached

  5. Lead time

  6. Buffer time

  7. Overlapping meeting

Priority

Reason

Rationale

1

Past time

Obvious, no action needed—don't waste user's time

2

Date range exceeded

Event-level setting—slot was never meant to be bookable

3

Outside host's availability

Fundamental—if hours aren't set, nothing else matters

4

Holiday marked

Explicit intent to be unavailable

5

Availability override

Explicit override for specific date

6

Lead time

Time-based rule blocking near-term slots

7

Meeting limit for scheduling link
(day, week, month)

Meeting limit for host
(day, week, month)

Duration mismatch

Gap exists but isn't long enough for duration of meeting

Buffer time

Adjacent meeting's buffer eating into this slot

Overlapping meeting (internal)

Another booking in your system

7

Calendar conflict (external)

External calendar blocking—actionable by changing event to "free"

8

Host unavailable in multi-host

9

Group event full

10

Slot reserved for payment

13

Team/Host unavailable

Collective event specific

14

Round-robin fairness

Team distribution rule

15

Group event full

Capacity for group events

16

Reserved/Pending

Temporary hold

17

Time slot interval mismatch

Edge case configuration issue

2

Calendar not connected

System failure—user can't trust any availability data until fixed