Help / Event types

Round-robin event types

A round-robin event type lets a team share a single booking link. Invitees see the combined availability of all the hosts, and 42min decides who actually takes each booking, spreading the load fairly.

What it is

• It's attached to a team (a named group of users in your organization).
• The booking page shows a slot if any team member is free for it.
• When someone books a slot, 42min assigns it to the team member who is available for that slot and has the fewest recent meetings, so over time, bookings are distributed evenly.
• The chosen host gets the calendar event; the invitee gets the confirmation as usual.

The team's settings control a couple of edge cases, for example whether a reschedule keeps the original host or re-picks one. Check the team's settings page if you need that behavior a particular way.

When to use it

• A "Talk to sales" or "Book a demo" link for a sales team.
• A support or onboarding team that shares incoming calls.
• Any situation where you want one public link but several interchangeable hosts.

If only ever one specific person hosts the meeting, use a one-on-one event type instead.

If many invitees should share each session (a webinar, a class, an onboarding cohort) while the host still rotates across the team, use Group + Round Robin.

How to set one up

1. First, make sure the team exists (Admin Center → Teams) with the right members.
2. Event Types → New Event Type, set Type → Round Robin, and pick that team from the Team dropdown that appears.
3. Fill in the name, description, duration and location. Leave Availability Source on Each member's own hours, or pick a schedule to limit the event to set hours. The rest of the editor works just like a one-on-one.
4. Save. The link is shared at the team level, e.g. 42min.us/team/<team-slug>/<event-slug>.

Zoom

The team itself controls how reschedules and slot availability behave. See Teams for those settings.

Limiting the event to set hours

By default a round-robin event offers times from each member's own working hours. In the editor's Availability & limits card, Availability Source reads Each member's own hours. Teammates in different time zones each keep their own day, and nobody is assigned a slot outside it.

To keep the event inside fixed hours (a demo line open 9:00 to 13:00 Lisbon time, for example), set Availability Source to one of your saved schedules or to Custom schedule. A booking then has to fit within both of these:

• the event's schedule, read in that schedule's time zone;
• the assigned member's own hours, read in theirs.

The event's hours narrow the members' hours and never extend them. If one member's day ends at 11:00 Lisbon time, they get nothing after 11:00, while a teammate who works later can still take the 12:00 slot. A slot appears when at least one member is free inside the window.

A saved schedule shows its hours and time zone under the selector, and its date overrides shape the window as well. Custom schedule opens weekly hours right below, with a Schedule Timezone that a team event always fills in.

A round-robin event created from a template keeps each member's own hours. The template doesn't carry this setting.

Common pitfalls

• No team yet. You can't create a round-robin without a team, so set up the team and its members first.
• One member's calendar is wide open and gets everything. Assignment balances by recent meeting count, but if a teammate hasn't connected their calendar (or has no busy times), they'll look the most available. Make sure every host has their calendar connected and their schedule set.
• No slots after limiting the event. The event's hours and the members' hours never overlap, for example a 9:00 to 13:00 New York window for a team that works in Singapore. Widen the schedule, or set Availability Source back to Each member's own hours.
• Expecting "the invitee picks the host". Round-robin assigns the host automatically. If invitees should choose, give them separate one-on-one links instead.