Round robin offers a team's combined free time and assigns each booking to one host by a rule. It is documented on the team scheduling page. The round robin guide explains eligibility, distribution, and ownership.
Before you start
- The list of eligible hosts and the hours each contributes.
- A distribution rule: equal share or first available.
- What happens when the guest already has an owner.
How to complete this task
- Choose eligible hosts and define the availability each contributes.
- Select a distribution rule and decide how existing ownership behaves.
- Test equal availability, no availability, and an absent team member.
- Review assignment outcomes instead of assuming equal booking counts.
Finish by opening the public link in a signed-out browser: a saved setting is not proof that the guest path works.
Troubleshooting
The problems people report most often with this task, and the cause behind each one.
One host receives most bookings.
Distribution follows availability. A host who publishes more open hours will absorb more meetings regardless of the rule — compare contributed availability before changing the algorithm.
A host on leave is still being booked.
Their availability was not removed. Round robin distributes among eligible hosts; eligibility has to be withdrawn explicitly.
No times appear when several hosts are eligible.
Check whether the rule requires all hosts rather than any host. That is collective scheduling, and it produces far narrower availability.
Related Meetin.gs help
Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.
