Team scheduling
Team scheduling without the enterprise tax.
Most schedulers gate the team features — round-robin, shared links, pooled availability — behind their most expensive per-seat tier. We make them the product: a shared team link free for up to 3 hosts, round-robin and pools up to 50 on Team at $8/seat/mo, and your whole team live in one sitting.
Round-robin that's actually fair
Bookings rotate through your host pool with fair-rotation tracking, and assignment is race-proof — two simultaneous bookings can't land on the same host slot. If a host's calendar can't be verified, we show fewer slots rather than risk a double-booking.
Collective scheduling
Need everyone in the room? Collective events intersect the whole pool's availability and hold every host's calendar, so the group is only ever offered times that work for all of them.
One shared team page
A single link for the whole team — demos, intro calls, interviews — with everyone's Google Calendars conflict-checked behind it and a Google Meet link on every Meet event type.
Invites without admin
Paste your teammates' emails. Each gets a link, connects a calendar, confirms hours, and is bookable — typically in under a minute. No seat provisioning, no role matrix, no approval loop.
How round-robin actually works here
Round-robin looks like a toggle and behaves like a small distributed-systems problem: several calendars, several timezones, and several people clicking the same slot at the same second. Here is the exact sequence between an invitee clicking a time and a host getting the invite — the ordering is the part that matters.
Each host's real free time is computed separately
Their own weekly hours, in their own timezone, minus their own date overrides, minus their existing bookings, minus every busy block their connected Google Calendars report.
The invitee sees the union
One merged grid of times when at least one host is free — which is why a pooled link fills next-day slots that no individual's calendar could offer. Invitees never see who is behind a slot.
On booking, availability is recomputed
The page may have been open for twenty minutes. The set of free hosts is rebuilt from scratch at the moment of booking rather than trusted from the render.
Rotation picks among the hosts who are genuinely free
The host assigned longest ago wins, with an explicit per-host priority as the tie-break. We never pick a host by turn and then discover they're busy — availability filters first, fairness decides second.
The database has the final word
The booking is inserted under a uniqueness constraint on host and start time. If that host lost a race to a booking on another link a millisecond earlier, the insert fails and the next free host takes it. Double-booking isn't prevented by careful code — it's structurally impossible.
One honest consequence worth knowing before you turn it on: rotation fairness is not workload fairness. A host who publishes forty hours of availability appears in the free-host set far more often than one who publishes six, so they will take more meetings under any rotation rule. Our round-robin explainer covers that and the other five failure modes in full.
Round-robin or collective?
Same host pool, opposite set operation. Choosing the wrong one is the most common reason a new team link shows far fewer times than expected.
Round-robin — “someone from the team”
Shows the union of everyone's free time and assigns one host. Denser availability, faster booking, load spread automatically. Use for demos, screens, support calls, office hours.
Collective — “all of us, together”
Shows only the times when every host is free and holds all their calendars. Fewer slots by design — that's the point. Use for panel interviews, kickoffs, and joint calls.
Who shared links are for
Pooled scheduling earns its keep whenever the invitee doesn't need one specific person. If relationships are owned individually, individual links stay simpler — and cheaper.
Inbound sales & demos
Speed to meeting is the whole game — pooled availability is usually the difference between “this afternoon” and “next Tuesday”, and interest decays fast in between.
Recruiting & first-round screens
Candidates don't need a specific interviewer for a screen. Round-robin spreads the load; collective handles the panel round without a scheduling thread.
Customer success & onboarding
One link per stage of the journey, backed by whoever is on duty. Coverage survives a holiday instead of going empty.
Office hours & advising
Faculty, mentors, and support engineers share one page. Buffers and minimum notice stop back-to-back overload without anyone policing a calendar.
Setting up a team, start to finish
There is no admin console, no seat provisioning, and no approval loop — each host configures themselves, which is why a team of five is usually live in one sitting.
- Sign in with Google. Your own booking page exists before you configure anything.
- Create a team event type and choose round-robin or collective assignment.
- Paste your teammates' email addresses. Each gets an invite link.
- Each host connects their Google Calendar and confirms their hours in their own timezone. This step is theirs, not yours.
- Book the link yourself twice, from a logged-out browser, and confirm two different hosts were assigned.
- Share it — and put it somewhere you control, so switching anything later is one redirect rather than an audit.
Moving a team off another scheduler? There's no automated importer — the rebuild is manual and takes minutes. The switching guide has the timings, and the migration write-up covers keeping old links alive while you move.
What we don't do
The list that usually appears in a sales call, published instead. If any of these is a requirement, we're not your tool yet and it's cheaper for both of us to find that out now.
- No Apple or iCloud calendars. Google Calendar and Microsoft 365 both work, and a team can mix them; CalDAV is not supported.
- No auto-created Zoom meetings. Google Meet and Microsoft Teams links are created for you; for Zoom you can paste your own link on an event type and it rides every invite.
- No CRM routing or lead-qualification forms. Assignment decides who takes the meeting; ownership stays wherever your team already tracks it.
- No SMS reminders and no workflow builder. Email confirmations and reminders, on every plan.
- No automated importer from another scheduler, and no SOC 2 or HIPAA attestation today.
What we do instead: read only free/busy from your calendars — never your event titles, attendees, or descriptions. The head-to-head comparison puts the gaps and the wins side by side, and our evaluation framework is written to be useful even if you pick someone else.
A 10-person team: $960/yr here vs $1,920/yr on Calendly Teams.
List prices, annual billing, as of July 21, 2026. Same round-robin, shared pages, and collective scheduling.
See every plan and what's in it →Team scheduling questions
What's the difference between round-robin and collective scheduling?
Round-robin shows the union of your team's free time and assigns one host per booking — use it when the invitee doesn't need a specific person. Collective shows only the times when everyone is free and books all of them — use it for panel interviews and group calls. Same host pool, opposite behaviour.
Is team scheduling free?
A shared team booking link is included free for up to 3 hosts, using collective assignment. Round-robin assignment and host pools up to 50 people come with the Team plan at $8/seat/mo billed annually. We'd rather tell you exactly where the paid line is than let you find it mid-setup.
How many hosts can a team link have?
Up to 50 on the Team and Scale plans, and up to 3 on Free and Pro. Every host is conflict-checked independently, so pool size doesn't change how the assignment works — only how dense the available times get.
What happens if a host hasn't connected their calendar?
They contribute no slots. We can't verify when they're busy, so offering their time would risk booking over a real meeting — we show fewer times rather than wrong ones. The same applies if a previously working calendar connection is revoked or expires. Check that every host has connected a calendar before sharing a team link.
Do hosts in different timezones need separate links?
No. Each host's availability is computed entirely in their own timezone before anything is pooled, and the invitee sees the merged result in theirs. Worth knowing: a widely spread pool naturally specializes, because European-morning bookings land on European hosts. If you want a specific distribution, split the link by region on purpose.
Can teammates set their own hours?
Yes — and they should. Each host owns their own weekly availability, timezone, and date overrides; the team link reads from all of them. There's no central schedule an admin has to maintain, and no approval step between a teammate changing their hours and the booking page reflecting it.
Does it work with Outlook, Zoom, or Teams?
Outlook and Teams, yes. Zoom, partly. You can sign in with Microsoft and connect an Outlook or Microsoft 365 calendar for conflict-checking, and bookings get a Microsoft Teams link automatically — that last part needs a work or school mailbox, because personal Microsoft accounts can't create Teams meetings, and those bookings carry whatever location you set instead. Work, school and personal accounts can all sign in and connect a calendar. Google Calendar and Google Meet work the same way, and a team can mix both providers — conflicts are checked across every connected calendar, whoever hosts it. For Zoom, you can paste your own meeting link on an event type and it rides every invite, confirmation, and reminder, but we don't create the Zoom meeting for you.