Routing
Every lead meets the right rep.
A few questions on your site decide who a lead books with. Big accounts reach their region's rep, the rest the next free one, and support questions skip sales.
Same form, three leads.
Acme's "Talk to sales" form, filled in three times this morning. Pick a lead to see the route it took.
Routes you can read out loud.
If the company has over 500 people and sits in EMEA, send them to the enterprise link and only to reps tagged EMEA and Enterprise. Otherwise, the demo link.
Customers get their own rep.
When the email belongs to an account in Salesforce, the account owner takes the meeting. Northwind is Martin's, so Martin's calendar opens.
See where leads went.
Every response, where it was routed and whether it booked. Spot the questions people drop on and who's carrying the queue.
A short form people fill in before they book. Their answers decide where they go next: a booking link, a team member, an external page or a message of your own.
No. You build the questions and the routes in Cal.com, then share the form's link or embed it on your site.
Open Routing in Cal.com, create a form, add your questions, then add routes that say where each set of answers goes. Test it with the preview before you share it.
Yes. Routing works with external forms such as Typeform, so you can keep the form you have and let Cal.com do the routing.
Yes. Give your team members attributes like region, segment or language, and a route can send a lead only to the people whose attributes match.
Yes. With Salesforce connected, a route can look up the lead's account and book the owner, with a fallback when the owner isn't free.
Routing is part of Organizations, at $37 per user per month. It covers what teams buy Chili Piper's Concierge, Distro and Handoff for.
Put the right rep on every call.
Build a form, write a route, and test it before a lead ever sees it.
Get startedTalk to sales