Round robin, skill-based routing, panel bookings — and the automation gap that will send a follow-up to the customer who cancelled.
A team calendar answers “when is everyone free?” A team scheduling system answers a harder question: which of these eleven people should this appointment go to, and what happens if they say no?
Almost every team that outgrows a personal booking link outgrows it for that reason. Everyone has their own Calendly-style link, the prospect books whoever’s link they were sent, and half the team is idle while one person is triple-booked. The fix isn’t a bigger calendar. It’s routing.
| Model | How it works | Use it when |
|---|---|---|
| Round robin | The booking goes to whoever is next in rotation and available. | The staff are genuinely interchangeable. Inbound demos, first-line support, screening calls. |
| Skill-based routing | The booking only reaches staff qualified for that appointment type. | They aren’t interchangeable. Spanish-language sessions, enterprise deals, a specific product line, a licensed specialism. |
| Multi-user appointment | One customer, several staff, one slot that works for all of them. | Panels, joint consultations, the technical call where sales needs the engineer in the room. |
All three are on Bookafy’s Pro plan, $7/user/month billed yearly. Unlimited users on that plan; only calendars that take bookings count as users.
This is the part most teams get wrong, so it’s worth being blunt about.
Pure round robin optimises for even distribution. If the goal is speed — get the prospect into anybody’s calendar before they cool off — even distribution can cost you the meeting, because the next person in rotation has no slot until Thursday and the prospect takes the Tuesday demo from your competitor.
So decide what you’re optimising before you configure anything:
Every routing rule in the world depends on knowing when someone is actually free. If a rep’s dentist appointment is in their personal calendar and Bookafy can’t see it, the system will cheerfully book a client into it.
Two-way sync — Google, Outlook/Office 365, iCloud, on the Pro plan — is what stops that. It reads the busy blocks out of the personal calendar, not just writes bookings into it. One-way sync is how teams end up apologising.
If your team is in three time zones and your customers are in six, the only sane rule is that the person booking sees their own local time and your staff see theirs. Bookafy does the conversion. What it can’t do is stop a manager defining “working hours” in one office’s timezone and wondering why the Singapore rep is offered 3am. Set availability per person, not per company.
Teams love to wire the booking into everything: create the CRM activity, ping the Slack channel, start the follow-up sequence. That’s all fine, and Bookafy supports it through Zapier and Make on the Pro plan.
But there’s a real limitation you need to design around: Zapier has no cancellation or reschedule trigger for Bookafy. The triggers are New Appointment, New Customer, New Appointment Type and New User. So if you build “40 minutes after the meeting, send a follow-up”, that follow-up will go to the person who cancelled — because nothing told the Zap to stop.
Two honest workarounds:
Also worth knowing: Zapier polls every 15 minutes on its free plan. If your workflow needs to know about a booking in seconds, that’s not a Bookafy limit, it’s a Zapier one.
| Not available | Reality |
|---|---|
| Lead scoring, or routing by deal size | Not a feature. If you need “route enterprise leads to the AE”, the qualification has to happen before the booking — in a form, or in your CRM. |
| Capacity or quota-based distribution (“Sam has hit their limit this week”) | Round robin distributes evenly; it does not know about targets. |
| Shift rosters | Bookafy books into availability. It does not decide who’s working Tuesday. |
| Cancellation-aware automations out of the box | See above — no cancellation trigger in Zapier. Build it on the API or accept the gap. |
| Waitlists | A cancelled slot simply reopens. Nobody is promoted into it. |
Bookafy’s Free plan is $0 for one user with unlimited appointments. The 7-day trial of Pro+ needs no credit card.
Appointments are distributed in rotation across a group of staff who are all able to take them, so nobody gets buried while others sit idle. It is on the Bookafy Pro plan.
The booking is only offered to staff qualified for that appointment type — a specific language, product, or specialism. Use it when your team members are not interchangeable.
Yes. Multi-user appointments schedule one customer with several staff members in a single slot — panels, joint consultations, or a sales call that needs an engineer.
Not through Zapier — there is no cancellation or reschedule trigger. Build cancellation handling on the API and webhooks, or trigger follow-ups from your CRM instead of from the booking event.
$7/user/month on Pro (billed yearly), with unlimited users and unlimited appointments. Only calendars that take bookings count as users. Round robin, skill-based routing and multi-user appointments are all included on Pro.
Yes — the person booking sees their own local time and staff see theirs. Set availability per person rather than defining company-wide hours in one office timezone.
If you are still working out which tool you need, start with the overview: appointment scheduling software — what it does, what it costs, and when you should buy something else.
Also useful: every Bookafy integration, in three honest lists — what is native, what needs Zapier, and what we simply do not do. And the pricing page, where the feature matrix is the real answer to “is that on the free plan”.
