Skip to content

Routing

Planned

The right person, not the next person.

Territory, segment, language, deal size and account ownership — evaluated in order, with weighted distribution, per-person capacity caps and a fallback chain that catches what nothing else matched.

Routing is specified and not yet built. This page describes what it will do and what blocks it.

Four hard courts photographed from directly overhead, blue playing surfaces marked out on a green surround, with floodlight masts, benches and a shade canopy between them. Nobody is playing.

Routing is priced at roughly twice scheduling by everyone who sells both.

The scheduling seat is a commodity. Every vendor that publishes both prices charges about double for the step that decides who the meeting goes to. And the vendors that do routing properly refuse to sell to a team of twelve.

Published scheduling and routing list prices at three vendors that sell both.
VendorSchedulingRoutingMultiple
Calendly$10 per seat per month$16 per seat per month1.6×
OnceHub$10 per seat per month$19 per seat per month1.9×
Chili Piper$12 per seat per month, 200-seat minimum$83 per seat per month effective at 15 seats6.9×

Published list prices, annual billing, checked 2026-08-17 · calendly.com/pricing · oncehub.com/pricing · chilipiper.com/pricing

Chili Piper’s effective per-seat price falls as you grow — $83 at 15 seats, $64 at 30, $55 at 60 — because it is a platform fee wearing a seat costume. Below fifteen seats it is not buyable at all.

Three ways to distribute, not one

Round robin
Equal rotation, availability-aware, timezone-aware
Maximum availability
The person with the most open time takes the meeting
Weighted and priority
Explicit weights and priority order, with per-person capacity caps
Hold for the owner
An existing account goes back to the person who owns it, even if they are busier
Fallback chain
An ordered list of who catches what nothing else matched — never a dropped lead
Out of hours
Holiday calendars and after-hours rules with an explicit destination, not silence

Fair means auditable, not “roughly even”

Distribution will be recorded as an append-only ledger rather than a counter on a row, so every assignment can be explained after the fact. Two details most implementations get wrong, that we are building in from the start: assignment happens under a row lock inside the booking transaction, because two simultaneous bookings will otherwise both pick the same “least recently booked” person; and a new host joins the rotation seeded to the existing average rather than at zero, because starting at zero buries them under every lead on their first day.

Order
Weight debt, then priority, then least recently booked, then a random tiebreak
Scope
Shares computed over the candidates who were actually eligible for that lead
Window
A rolling fairness window, so an absence does not create permanent debt
Record
Every assignment and every manual reassignment written to the ledger

Qualify and book in the same session

A routing form asks what determines the answer — company size, region, product, language, existing account — then evaluates the rules and shows live availability for the person it chose, without a redirect and without a second page load. The answers stay attached to the booking and to the conversation that follows it.

Why we are writing this from scratch

Bookesto’s scheduling foundation is a fork of Cal.diy, which was relicensed to MIT in April 2026. Routing forms, workflows and organisations were removed from that MIT tree, and the pre-relicense history is under a different licence that we will not use. So every part of routing is written by us. It is the most expensive decision in the build and it is not negotiable.

Get the build log and first access

The booking core is live and merchant access is invite-only. Get the changelog as it happens and an invitation when the private beta is ready for your business.

No card. Merchant access is invite-only — you get the build log and first access.