Round robin host unavailable: what happens and what to check

When a round robin host is unavailable, new bookings should go to the other eligible hosts, and the booking page shows fewer times if nobody else is free. Meetings already booked with that host don't move on their own. So you have two jobs: fix who can get new bookings, and decide who runs the meetings already confirmed.

Say Omar is off next week, but a demo is still on his calendar for Tuesday. Meanwhile, the team's booking page shows no afternoon times. It looks like one problem. It's really two.

Before you change anything, note the event link, the date, the host's name, the time zone and the booking reference. Then work on one question at a time. Changing several settings at once can hide the cause and still leave Tuesday's demo unsolved.

New bookings and booked meetings need separate checks

Use the confirmed meeting's details as your starting record. A round robin pool decides who gets future bookings, so don't expect it to reshuffle meetings that are already booked. Before you edit anything, decide who will talk to the attendee.

1. Check holidays and time off

For planned time off, look at the dates in the host's own time zone. Make sure the block covers the whole meeting plus any buffers. Check the actual event you're sharing, because a change to one schedule may not reach every event that host runs.

Caletus supports date-specific overrides that block days off without changing your regular weekly hours. Add the absence, then open the booking page and check that those times are gone. That covers new bookings only. For more on blocking dates, see holiday availability and date overrides.^[1]

2. Check the calendars that prevent double booking

A personal appointment can sit on a calendar that was never added to conflict checks. Or the event may be marked free instead of busy. Check which calendars are selected, and the event's status, before you decide the booking page is ignoring a conflict.

Caletus checks busy times across connected Google and Outlook calendars, and you choose separately which calendar new bookings go to. Review both settings. Adding a new meeting to one calendar is a different job from checking all of them for conflicts. Here's how to check up to 6 calendars to prevent double booking.^[1]

3. Treat a disconnected calendar as unknown, not free

A broken connection is different from an empty calendar. Check the authorization and connection status, reconnect through the normal process, then test again with a time you know is busy. Until the result is reliable, pause bookings for that host or handle them by hand.

Caletus's public pages don't say exactly what happens to bookings while a calendar is disconnected. They don't say whether the host is skipped, older data is used or the event stops. Write down what your test shows, and ask Caletus support to confirm the intended behavior.

4. Check limits, buffers and notice

A host can look free and still fail the event's booking rules. Check meeting limits, working hours, minimum notice, how far ahead people can book, and the buffers around the meeting. For example, a 30-minute gap won't fit a 30-minute meeting that also needs a 15-minute buffer.

Find out whether each limit applies to one host, one event or the whole workspace. Don't raise a limit just to make a test pass. First check whether the host has really hit the cap the team agreed to protect.

5. Check whether anyone can take the meeting

Someone can be free and still be the wrong person. Review the host pool, who's a member, who has the right expertise and any required-attendance rules. An available employee who isn't an approved interviewer can't run a technical interview.

When nobody suitable is free, offer later times or a staffed way to get in touch, such as a team inbox. That contact option is your team's process unless the product provides one. For panels, no overlap between required hosts is a different problem from an empty pool, as explained in collective vs round robin scheduling.

What Caletus covers, and what you should test

Caletus's team page mentions optional-host fallbacks and several distribution rules. It doesn't say that confirmed meetings are reassigned automatically, or how every calendar failure is handled.^[2]

Treat a fallback at booking time and a later host swap as two different things. Ask which host rule the fallback relaxes, when it kicks in, and what invitation the guest gets. A line in a feature list won't answer those questions, so test them.

Round robin availability tests to run

How to hand off a meeting that's already booked

1. 1Find the confirmed meeting and check its current host and attendee details.
2. 2Agree on a replacement host or a new time before you change the booking.
3. 3Use your scheduler's host-change or reschedule option. Don't assume calendar ownership or video permissions move with it.
4. 4Tell the attendee what changed and which meeting link to use.
5. 5Check the updated calendar events, reminders and meeting access, and clear up any duplicates.

A short message works: "Omar is out for our Tuesday demo. Maya can cover the same time and has the background you shared. We'll send the updated invitation shortly." Only send it once Maya has said yes. For more wording ideas, see these reschedule meeting email templates.

Also watch for half-finished bookings. An error after the guest confirms doesn't prove the booking failed. Before you ask them to book again, check the scheduling record and the host's calendar. A second booking can leave two invites, two hosts or double reminders to untangle. Keep one clear record of the intended meeting while support looks into the error.

Send support an example they can reproduce

If the result doesn't match your settings, send support the event reference, dates, time zones, screenshots with private details hidden, and the exact steps to reproduce it. Say what you expected and what happened. Never send calendar tokens, passwords or unrelated customer details. After the fix, rerun the same test.

The habit that prevents most surprises is simple: check future availability and existing meetings as two separate tasks. Then a holiday becomes a planned handoff, instead of a customer waiting alone in an empty meeting.

• unavailable meeting host
• round robin availability
• team booking troubleshooting
• calendar conflict checks