How to Turn Your Jobber Service Areas Into Automatic Booking Routing

If you've already mapped out who covers what in Jobber, you've done the hard thinking. What Jobber doesn't do is use those service areas to route inbound bookings: a prospect lands on your booking link, enters their address, and nothing automatically asks “which tech covers this ZIP?” You end up dispatching manually — or double-booking a zone. The fix is to rebuild your service areas as routing territories in a scheduling layer that sits in front of Jobber. It takes about 15 minutes, and this post walks through it.

One thing to be clear about up front: Jobber has no native export for service areas, and no scheduling tool — Cartoply included — can pull them out automatically. You'll recreate each area by hand. That sounds tedious, but because territory builders work in ZIP codes, counties, cities, and radii (the same vocabulary you used in Jobber), it's a few clicks per territory, not a mapping project.

What Jobber Service Areas Actually Give You (And What They Don't)

Jobber lets you define service areas per tech — typically by city, county, or a drawn radius. That data drives a lot of your operational logic: which jobs appear on which tech's schedule, what work order gets created, how invoicing is tracked.

What Jobber doesn't do is intercept an inbound booking request and automatically assign it to the tech who covers that address. That handoff — from prospect entering an address to the right tech's calendar getting blocked — requires a layer Jobber wasn't built for. It's not a criticism; Jobber is excellent job management software. But if you're growing inbound volume, or techs are still driving past each other's jobs because dispatch is ad hoc, you need territory-aware scheduling sitting in front of Jobber, not alongside it. (See our breakdown of what Jobber scheduling does and what's still missing for the full picture.)

How to Rebuild Your Jobber Service Areas as Routing Territories

1. List your service areas from Jobber — open each tech's service area in Jobber and note how it's defined: which ZIPs, which county, or what radius around which address. This list is your blueprint.
2. Recreate each area in Cartoply's territory builder — territories can be drawn by ZIP code, county, city, state, or a radius around a point, so each Jobber area translates directly. A typical area takes a minute or two. (You can try the free territory builder before signing up.)
3. Assign techs to territories — link each territory to the tech who owns it, matching your Jobber assignments.
4. Connect your Jobber account — go to Settings → Integrations → Jobber and authorize the OAuth connection. This is what makes confirmed bookings create Jobber Requests automatically. Takes about 60 seconds.
5. Enable auto-routing on your booking link — turn on territory-aware routing so that when a prospect enters their address, the right tech is resolved and only that tech's available slots are shown.
6. Test with a live address from each territory — submit a test booking from an address in each zone and confirm the right tech's calendar is hit and a Jobber Request is created.

The whole process takes about 15 minutes if your Jobber service areas are already clean. If they're not — overlapping zones, techs covering each other's territory informally — budget another 20–30 minutes to tighten the boundaries first. It's worth doing right once rather than debugging misfired bookings later.

What Happens After a Booking Comes In

Once routing is live, the workflow is fully automated. A prospect visits your website, enters their address in the booking widget (embed it as a popup or inline iframe — takes two lines of code), and Cartoply resolves which territory that address falls in. The prospect only sees the available slots for that tech. When they confirm, Cartoply creates a Jobber Request automatically — no copy-paste, no manual dispatch, no “which tech should I send this to?” conversation in your group chat.

If you want to add a payment gate before that confirmation, Cartoply's Stripe integration lets you collect a deposit or full payment upfront. That's a meaningful no-show reducer for service estimates and diagnostic visits. If you haven't decided whether a deposit or full prepayment makes more sense for your business, the deposit vs. full prepayment breakdown is worth a read before you configure that step.

Automated email reminders go out on your schedule — typically 24 hours and 2 hours before the job — so you're not manually chasing confirmations either.

Getting Territory Boundaries Right Before You Rebuild

Your new routing territories are only as good as the service-area logic you bring over. Before you rebuild, do a 10-minute audit of what's in Jobber:

• Check for ZIP code overlap. If two techs both cover the same ZIP, you'll get conflicting routing logic. Assign each ZIP to exactly one tech. Our post on fixing territory overlap between techs covers the fastest way to resolve this.
• Check for coverage gaps. ZIP codes that don't belong to any tech will fall through the routing logic — the system can't assign what it doesn't know about. Map them intentionally.
• Validate drive-time logic. A territory that looks clean on a map can still generate 45-minute drives if the boundaries don't follow natural routing corridors. If you're unsure what a reasonable territory size looks like, the right territory size for a tech doing 4–6 jobs a day gives you concrete benchmarks.
• Note techs who cover multiple zones. Cartoply supports assigning one tech to multiple territories — useful for coverage during PTO or for senior techs who flex across zones. Set these up after the base territories are in, so you don't muddy the initial assignments.

If your territory map needs a more structural rethink before you rebuild, the full Cartoply features overview walks through how to draw territories by ZIP, county, city, or radius from scratch — which gives you a clean baseline you can mirror back into Jobber.

Related reading: Drive Time vs City Limits: How to Build Smarter Service Areas.

When One Booking Link Covers Your Whole Team

One thing that trips up owners during setup: you only need one booking link for your whole company. You don't create a separate link per tech. The single company link handles the routing decision internally — the prospect enters their address, the system resolves the territory, and only that tech's availability is shown. Each tech only ever sees their own jobs. This keeps your website clean (one “Book Now” button) and eliminates the operational mess of managing per-tech links whenever someone joins or leaves the team.

Related reading: How to Connect Jobber With an Online Booking System for Automatic Job Creation.

Frequently Asked Questions

Can I import Jobber service areas into another scheduling tool?

No. Jobber does not have a native export for service areas, and no scheduling tool can pull them out automatically — including Cartoply. The practical path is to rebuild them: in Cartoply's territory builder each area is a few clicks (ZIP codes, county, city, or radius), so a typical team's full map takes about 15 minutes to recreate.

Does Cartoply sync with Jobber in real time?

Bookings do. When a booking is confirmed in Cartoply, a Jobber Request is created automatically and in real time — client, property, and a scheduled assessment assigned to the matching team member. Territory definitions are not synced between the systems; you maintain those in Cartoply's territory builder.

What happens if a prospect books from a ZIP code not assigned to any tech?

Cartoply will not show availability for an address outside your covered territories — the prospect sees that the address isn't in a covered service area instead of a broken booking flow. Auditing for coverage gaps before you rebuild (described above) prevents most of these cases.

Do I need to keep maintaining service areas in Jobber after I set up Cartoply?

You can maintain territory logic in either system. Most owners keep Jobber as the source of truth for job management and let Cartoply own the inbound routing layer. If you restructure a service area in Jobber, mirror the change in Cartoply's territory builder — it's a few clicks. The two systems are complementary — Cartoply handles who gets the booking; Jobber handles everything after the job is created.