Getting the right booker to the right calendar
Scheduling links are simple until you have more than one team. Routing forms turn a single entry point into a smart dispatcher — the booker answers a few questions and lands on the right event type.
Every scheduling tool starts with the same clean primitive: one link, one calendar, one meeting. That works beautifully until your company grows a second team. Now marketing wants inbound demos triaged by company size. Sales wants enterprise leads pulled out before they hit an SDR. Support wants existing customers routed away from the sales funnel entirely. Suddenly the single link is the wrong abstraction.
We kept seeing customers solve this by hand — publishing a decision tree in a Notion doc, or worse, hoping the prospect picked the right link from a menu of five. It works about as well as you'd expect.
One entry point, many destinations
Routing forms fix this by inverting the model. Instead of asking the booker to pick the right link, you give them one link and ask them a few questions. Their answers determine which team or event type they land on Route a Booker with the Routing Form. The booker never sees the decision tree; they just see a form, and then the right calendar.
The interesting design choice here is where the routing logic lives. It's not in your CRM, not in a Zap, not in a landing-page redirect. It's attached to the scheduling primitive itself, which means the person who owns the meeting also owns how bookers reach it. No ticket to marketing ops.
Why this unlocks more than triage
Once routing is a first-class concept, a lot of workflows collapse into it. Qualifying inbound leads is just a routing form. Sending existing customers to their account manager instead of a generic queue is a routing form. Splitting a shared "Contact us" link between sales, support, and partnerships is a routing form. The pattern is the same: ask, then route.
It also gives you a clean place to capture context before the meeting exists. By the time the booker lands on the event type, you already know who they are and why they're here — which means the person taking the meeting does too.
What's next
This is the foundation. The obvious next steps — richer conditional logic, deeper CRM lookups, routing based on data the booker doesn't have to type — are what we're building on top of it. If you're still maintaining a spreadsheet that maps prospect attributes to Calendly links, this is the feature to try first.