The Right Way to Use Booking Links With Multiple Techs
The Problem With One Booking Link and Multiple Techs
If you have more than two or three technicians, you've probably already run into this: a customer books online, the job lands in your calendar, and then someone — usually you or your office manager — has to figure out which tech should actually take it. That manual step is where things break down. The wrong tech gets assigned. A job gets booked in a ZIP code that's 45 minutes outside their area. Two techs end up on opposite sides of town when they could have been working the same neighborhood all day.
The right way to use booking links when you have multiple technicians is to make the address do the work. When a customer enters their location, the system should already know which tech covers that area — and route the job to them automatically, without anyone touching it. That's not a luxury feature. For a company with 5 or more techs, it's the difference between a tight, profitable schedule and a day full of wasted windshield time.
Why Most Companies Get This Wrong
The default setup most businesses fall into is this: one shared calendar, one booking link, everyone sees everything. It feels simple until it isn't. Here's what goes wrong:
- Customers pick the wrong tech. If you give customers a choice of technician at booking, they'll pick whoever sounds familiar — not whoever is already working nearby.
- No one owns their territory. When any tech can pick up any job, nobody has a real service area. Route density disappears. Drive time goes up.
- Dispatch becomes a second job. Every booking requires a human decision. That's fine when you have two techs. It doesn't scale to eight.
- Techs see jobs that aren't theirs. When everyone can see the full calendar, you get confusion, double-booking attempts, and techs calling in to ask "is that one mine?"
The Right Structure: Zones First, Then Booking
Before your booking link can do any real work, you need defined service areas for each technician. Not a rough idea of who covers the north side — actual mapped zones. ZIP codes, counties, city boundaries, or a radius around a home base. Once those zones exist, every customer address has a clear answer: this tech, not that one.
Here's how to build the right setup, step by step:
- Map each tech's territory. Start with what you know — where each tech lives, where they're already doing most of their jobs, and where the work is densest. Draw zones that minimize overlap. Overlap creates the exact dispatch confusion you're trying to avoid.
- Use a single company booking link. Don't give each tech their own separate booking link. One link means one consistent customer experience, one place to send your Google Ads traffic, one URL on your website. The routing happens behind the scenes.
- Let the customer's address decide the tech — not the customer. When someone fills out your booking form, their address matches against your territory map. The job goes to the right tech automatically. The customer never picks a name from a dropdown.
- Give each tech a view of only their own jobs. Once zones are set and auto-assignment is running, each tech should see only the jobs in their territory on their calendar. Less noise, fewer questions, cleaner days.
- Sync to the calendar they already use. If your techs live in Google Calendar or Outlook, the booking needs to show up there — not in some separate app they have to remember to check. Calendar sync is what makes auto-assignment actually stick in daily operations.
Cartoply is built around exactly this structure. You draw territories by ZIP code, county, city, or radius. A customer enters their address at booking, and Cartoply routes them to the right tech automatically. Each tech gets their own calendar view — they see their jobs, not everyone else's. The whole company runs off one booking link.
Concrete Benchmarks: How to Know Your Setup Is Working
Once you have zones and auto-assignment in place, here are the numbers worth tracking to confirm it's actually working:
- Average drive time per job should drop below 20 minutes once techs are consistently working their zone. If you're still seeing 35–45 minute drives regularly, your zones may be too large or overlapping.
- Aim for 5–7 jobs per tech per day in a tight territory. If route density is good, techs aren't burning time in the truck between stops.
- Manual reassignments should be under 5% of bookings. If you're manually moving jobs more than that, the zones need to be redrawn or the auto-assignment logic has gaps (usually unassigned ZIP codes or boundary issues).
- Booking-to-confirm time should be under 2 minutes. With auto-assignment working, no human should need to touch a booking before it's confirmed and on the right tech's calendar.
One More Thing: Collect Payment at Booking
While you're fixing the routing problem, fix the payment problem at the same time. A booking link that auto-assigns the right tech but doesn't collect a deposit is still leaving money on the table — and setting you up for no-shows. Requiring a deposit or full payment before confirming a job means you're not chasing anyone down after the visit. It also filters out low-intent bookings before they clog up your schedule.
If you're running Jobber as your field service software, the integration between Cartoply and Jobber closes the loop entirely: a booking through your Cartoply link automatically creates a Jobber Request, with the customer's address, contact info, and service details already filled in. Your service areas in Jobber import directly as Cartoply territories. Nothing gets re-entered. Nothing gets missed.
Start With Your Zones Today
The fastest way to fix booking chaos with multiple techs is to stop treating territory as an afterthought. Draw your zones this week — even rough ones — and build your booking link on top of them. You can refine boundaries over time as you see where the jobs actually land.
If you want to see how Cartoply handles territory setup and automatic tech assignment, start a free trial and build your first zone in about 10 minutes. Bring your ZIP codes and your tech list. That's all you need to get started.