How to Import Jobber Service Areas Into a Territory Routing System

If you've already mapped your service areas in Jobber, you don't need to start from scratch. Cartoply's Jobber integration pulls your existing service areas in as territories — so every new booking automatically routes to the right tech, and completed bookings create Jobber Requests without any manual data entry.

This matters because Jobber's scheduling tools don't do inbound territory routing. A prospect lands on your booking link, enters their address, and Jobber has no way to automatically assign that job to the tech who covers that ZIP code. You end up dispatching manually — or worse, double-booking a zone. The import process described here closes that gap in under 10 minutes.

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 lives in your Jobber account and 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 ask "which tech covers this 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 your inbound volume, or if 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 Import Your Jobber Service Areas Into Cartoply

1. Connect your Jobber account — go to Cartoply Settings → Integrations → Jobber and authorize the OAuth connection. Takes about 60 seconds.
2. Trigger the service area import — click "Import Jobber Service Areas." Cartoply pulls each tech's defined area and maps it to a territory automatically.
3. Review and adjust territory boundaries — inspect each imported territory on the map. Add or remove ZIP codes, counties, or radius adjustments that don't match how your team actually works today.
4. Assign techs to territories — each imported area links to the tech who owns it in Jobber. Confirm the assignments are correct before going live.
5. Enable auto-routing on your booking link — turn on territory-aware routing so that when a prospect enters their address, Cartoply resolves the correct tech and only shows that tech's available slots.
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 10–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 before you go live. 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 Import

The import is only as good as the service areas already in Jobber. Before you connect the integration, do a 10-minute audit:

• 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 or set a fallback assignment.
• 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 import rather than before, so you don't muddy the base assignments.

If your territory map needs a more structural rethink before import, 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 to sync back to Jobber.

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.

Frequently Asked Questions

Can I import Jobber service areas into another scheduling tool?

Jobber does not have a native export for service areas in a format most scheduling tools can read. Cartoply is the only scheduling tool with a dedicated Jobber service area import — it pulls territories directly via the Jobber API. For other tools, you'd need to manually recreate each zone from scratch, which takes significantly longer and introduces transcription errors.

Does Cartoply sync with Jobber in real time?

Yes. When a booking is confirmed in Cartoply, a Jobber Request is created automatically and in real time — no batch sync, no delay. You can also import updated service areas from Jobber at any time if you restructure territories. Calendar availability syncs bidirectionally with Google Calendar and Outlook, so Jobber job blocks won't cause double-bookings.

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

Cartoply will not show any availability for an unassigned ZIP — the prospect will see a message that the address isn't in a covered service area. You can configure a fallback: either a catch-all tech who handles out-of-territory requests, or a custom message directing the prospect to call your office. Auditing for coverage gaps before import (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 update a service area in Jobber, you can re-import it to Cartoply with one click. The two systems are complementary — Cartoply handles who gets the booking; Jobber handles everything after the job is created.