Every growing team hits the same scheduling wall. One person's calendar becomes the bottleneck, a second person's stays half empty, and someone spends Friday afternoon manually reassigning demos in a spreadsheet. Round-robin scheduling exists to remove that job. This guide explains what it is, exactly how the assignment logic works, when it is the right choice, and how to set it up so the rotation stays fair without anyone babysitting it.
Quick answer: Round-robin scheduling lets a team share one booking link. When an invitee picks a time, the tool assigns the meeting to one teammate who is free at that moment, favouring whoever has the fewest recent bookings. In PepoSmart, assignment considers each host's availability schedule, connected-calendar conflicts, per-host meeting limits, and how recently each host was assigned. Nothing is routed by CRM ownership or territory.
Key takeaways
- Round-robin is about load distribution, not about the invitee choosing a person. If the invitee cares who they meet, use a choose-a-professional event instead.
- The booking page shows the union of host availability: any slot where at least one eligible host is free. Collective events show the intersection.
- Fairness comes from two rules working together: skip hosts who are unavailable or over their meeting limit, then prefer the host with the fewest and least recent assignments.
- Most "the rotation is unfair" complaints trace back to one host with a disconnected calendar, a stale availability schedule, or a missing conferencing integration.
- Round-robin has real limits. There is no weighted distribution, no territory routing and no qualification form in PepoSmart, and it is better to know that before you design a process around it.
What is round-robin scheduling?
The term comes from computing, where a round-robin scheduler gives each process a turn in a fixed rotation. In meeting scheduling the idea is the same, applied to people. A team publishes one link, for example "Book a 30-minute product demo". Behind that link sit several hosts. The invitee never sees the roster. They see a calendar of available times, pick one, and the tool decides which host takes the meeting.
That single decision is the whole feature. Everything else is plumbing: the calendar invite, the video link, the confirmation and reminder emails, the CRM record. Those behave exactly as they would for a one-on-one event. The difference is that the "who" is computed at booking time rather than fixed when the link was created.
Round-robin is one of several team event shapes. The others are worth naming now because people often reach for round-robin when they actually need one of these:
- Collective events put every host in the same meeting, so times are only offered when all hosts are free. Panel interviews and joint discovery calls use this.
- Group events let many invitees book the same slot, up to a capacity you set. Webinars, office hours and class sessions use this.
- Choose-a-professional events show the roster and let the invitee pick a person. Clinics, salons and coaching centres use this.
- One-off meetings offer a handful of specific times you hand-pick for one conversation.
PepoSmart supports all of these as separate event types, which is documented on the product-facts page.
How does round-robin scheduling work?
It helps to walk through one booking from the invitee's first click to the calendar invite landing in a host's inbox.
Step 1: The booking page builds a combined calendar
When someone opens a round-robin booking page, the tool asks each host's availability schedule for open hours, checks each host's connected calendars for existing commitments, and applies each host's rules such as minimum notice, buffers and booking window. It then takes the union of the results. If Priya is free at 10:00 and Marcus is free at 14:00, the invitee sees both slots. A slot appears as long as at least one host could take it.
This is the first thing that trips teams up. The page can look "very available" even when one host is nearly full, because the other hosts are filling in the gaps. That is working as designed.
Step 2: The invitee picks a time
The invitee chooses a slot, answers the intake questions, and submits. At this moment the tool re-checks availability, because a slot that was open when the page loaded may have been taken in the meantime.
Step 3: Ineligible hosts are removed
For the chosen time, the tool discards any host who:
- has no open hours at that time on their schedule,
- has a conflicting event on a connected calendar,
- has already hit a daily, weekly or monthly meeting limit for that period, or
- lacks a required integration, such as a connected Zoom account when the event's location is Zoom.
Only hosts who genuinely can take the meeting survive this step. If none survive, the invitee sees a message asking them to pick another time.
Step 4: The fairness rule picks one host
Among the eligible hosts, the tool prefers whoever has the fewest bookings and was assigned least recently. This is what keeps the rotation from clustering on the person with the most open hours. A host who just took a meeting drops to the back of the queue; a host who has been quiet moves to the front.
PepoSmart's documentation lists the factors it weighs in exactly this order: the host's own availability schedule for the event, conflicts on connected calendars, per-host meeting limits, and previous assignments including how recently each host was assigned. You can read the full description on the team events feature page and in the Teams documentation.
Step 5: Everything downstream runs for that host
The booking is written to the assigned host's calendar, the conferencing link is created on that host's Zoom, Google Meet or Microsoft Teams account, confirmation and reminder emails go out, and any CRM sync or webhook fires with the assigned host's details. Team owners see every booking on events they own, with a badge showing which host received it.
| Assignment factor | What it does | Where you control it |
|---|---|---|
| Availability schedule | Removes hosts with no open hours at the chosen time | Each host's Availability page |
| Connected-calendar conflicts | Removes hosts with an existing commitment | Google Calendar or Outlook connection |
| Meeting limits | Removes hosts who hit a daily, weekly or monthly cap | Meeting limits on the host's schedule |
| Required integrations | Removes hosts who cannot generate the event's video link | Each host's integrations page |
| Recency and load | Prefers the host with the fewest and least recent bookings | Automatic |
Round-robin vs collective vs group vs choose-a-professional
Picking the wrong event type is the most common reason a team event "does not work". Use this table before you create anything.
| Situation | Right event type | Why |
|---|---|---|
| Any one rep can run the demo; you want bookings spread evenly | Round-robin | One host per booking, assigned by availability and fairness |
| Two or more people must all attend, such as a panel interview | Collective | Slots only appear when every host is free |
| Many attendees join one session, such as office hours | Group | One slot, many invitees, capacity you set |
| The invitee should choose the person, such as a clinic or salon | Choose a professional | Roster is shown; times are that person's alone; nothing rotates |
| You want to offer three specific times to one prospect | One-off meeting | Hand-picked slots, single use |
The clearest way to remember it: round-robin hides the roster and shares the load; collective hides the roster and requires everyone; choose-a-professional shows the roster and lets the invitee decide. If you are setting up a clinic or coaching centre, the guide to letting clients choose their professional covers that path in depth. Recruiting teams comparing collective and round-robin for interview loops will find the interview scheduling guide more specific.
When should you use round-robin scheduling?
Round-robin earns its keep whenever the invitee is indifferent to who they meet and the team wants throughput. Typical cases:
Inbound sales demos. A prospect clicks "Book a demo" on your pricing page. Any account executive can run it. Round-robin removes the delay of a coordinator assigning the lead, which matters because response speed on inbound requests is something most sales teams measure closely. The sales solution page walks through how the recorded demo then feeds coaching and CRM updates.
Support and onboarding calls. Customer success teams often run a shared "Onboarding session" link. Round-robin keeps new-customer calls from landing on whichever specialist happens to be listed first. See the customer success solution for how relationship health is tracked afterwards.
Consultation intake. Law firms, agencies and financial advisers with a pool of qualified staff can offer a single "Initial consultation" link. This works well when the consultation is exploratory and the client will be matched to a specialist later.
Recruiter screens. First-round phone screens are usually interchangeable across a recruiting team, which makes them a good round-robin candidate. Later panel rounds are usually collective.
When round-robin is the wrong choice
Round-robin is a poor fit in three situations, and it is better to design around them than to fight the tool.
The invitee has a relationship with a specific person. Existing customers who already work with a named account manager should book that person directly. Sending them into a rotation feels like being handed to a stranger. Give each host their own link for existing relationships and keep the round-robin link for new inbound.
Assignment must follow business rules the tool cannot see. Territory, deal size, language, seniority or CRM ownership are not inputs to PepoSmart's assignment. There are no routing or qualification forms in front of the calendar, and no weighted or territory-based distribution. This is stated plainly on the team events page and it is the main reason teams compare PepoSmart with routing-first tools; the Chili Piper alternative comparison sets out that trade-off honestly.
Skills differ sharply across the pool. If only two of five hosts can demo the enterprise tier, a single rotation will send enterprise prospects to the wrong people. Create two events with two host pools instead, and let the invitee self-select on the booking page.
How to set up a round-robin event step by step
The setup takes about twenty minutes the first time. Most of that is making sure each host's own account is ready, because a round-robin event is only as reliable as its least-configured host.
1. Build the team and set permissions
Invite each host from the Team page and grant the Can host events permission. Invitations expire after 14 days, and on paid plans every accepted invitation becomes a billed seat. The Free plan is owner-only, so round-robin needs a paid plan. Current seat and price details are on the pricing page.
2. Have every host connect their calendar and conferencing
Each host should connect Google Calendar or Outlook, plus whichever video tool the event will use, such as Zoom. PepoSmart can only see conflicts on calendars that are connected, so a host with an unconnected work calendar will look free when they are not. A host without the event's required video integration is not eligible to be assigned at all.
3. Set each host's availability and limits
Every host keeps their own weekly hours, buffers, minimum notice and booking window under availability rules. This is also where meeting limits live. A sensible starting point for a demo rotation is a per-day cap so nobody ends up with six back-to-back demos, plus a buffer after each meeting for notes.
4. Create the event and pick Round robin
From the Create menu choose Round robin. The event is created immediately with a placeholder title and a phone location, then you land on the edit page. Set the title, description, duration and the real location. Keep the event private until it is tested.
5. Add the hosts
Open the Team members section of the event and share it with the hosts who should be in the rotation. Only members with the hosting permission appear. The setup steps are detailed in the Events and Booking documentation.
6. Test with a real booking
Open the public page in a private browser window, book a slot, and check three things: the assigned host's calendar received the event, the confirmation email carries the correct video link, and the host that received it makes sense given who was free. Cancel the test booking from the confirmation email so the calendar entry is removed.
7. Make it public and share the link
Switch the event to public, style the page with the page builder if you want it to match your brand, and share the link. The same link can be embedded on your website; the website embed guide covers that.
Common round-robin mistakes and how to fix them
One host gets everything. Usually this host has the widest open hours while the others have narrow or stale schedules. Compare the schedules side by side. Fairness only applies among hosts who are eligible for a given slot, so a host who is never eligible never gets a turn.
A host never gets anything. Check that they have the hosting permission, that they are actually added to the event, that their calendar is connected, and that they have the event's conferencing integration. Any one of these silently removes them from the pool.
Invitees see slots but bookings fail. This points to a conflict that only appears at booking time, most often a calendar that was connected after the page loaded or a meeting limit that was reached in the meantime. Ask the invitee to refresh and choose again.
Double-bookings on a personal calendar. PepoSmart checks connected calendars before showing a slot and again when the booking is submitted. If a host keeps personal appointments on a calendar that is not connected, those appointments are invisible. Connect it or block the time on the connected calendar.
Reminders arrive but the video link is missing. The assigned host does not have the video integration connected, so the location fell back. Every host in the pool needs the same conferencing connection as the event's location.
Measuring whether the rotation is fair
Do not trust a feeling about fairness; count. Team owners can see every booking on the events they own with the assigned host shown on each one, and can filter the Meetings list by team member. A simple weekly check is enough:
- Count bookings per host for the week.
- Count each host's open hours for the same week.
- Divide. Hosts with similar bookings-per-open-hour are being treated fairly, even if their raw totals differ.
Large gaps in that ratio almost always come from step three of the assignment logic: someone is being removed from the pool for a reason that is not obvious from their calendar. The team events page lists the eligibility factors; walk through them for the under-assigned host.
If the goal is not just fairness but fewer empty slots, pair the rotation with the tactics in the guide to reducing no-shows, because a fair rotation of meetings that never happen helps nobody.
How round-robin fits with the rest of the meeting
Once a booking lands with a host, the meeting can be recorded by the AI notetaker if the event's location is Zoom, Google Meet or Microsoft Teams and notes are enabled. The transcript, summary, action items and follow-up draft attach to the assigned host's meeting record, and on Professional and above the contact and meeting can sync to a connected CRM. That means a round-robin demo rotation produces a consistent record of every call regardless of who ran it, which is the point at which team leads usually stop worrying about who got which lead and start looking at what happened on the calls. The AI meeting notes page explains prerequisites and plan allowances.
Summary
Round-robin scheduling replaces a manual assignment job with a rule: give the meeting to an eligible host, and among eligible hosts prefer the one who has waited longest. It is the right choice when invitees are indifferent to who they meet and the team wants bookings shared. It is the wrong choice when the invitee has a relationship with a named person, when assignment must follow territory or ownership rules, or when skills differ sharply within the pool. Set it up by getting every host's calendar, conferencing and availability in order first, then test with a real booking before you publish.
If you want to compare how other tools handle team scheduling, the Calendly alternative comparison covers the differences in team event types and pricing, and you can start a free PepoSmart account to try the setup above.
