How to Connect Jobber With an Online Booking System for Automatic Job Creation

You can connect Jobber with an online booking system by using a tool like Cartoply, which has a native Jobber integration: when a customer books online, Cartoply automatically creates a Jobber Request — complete with client details, property address, and the assigned technician — with zero manual entry. The setup takes about 15 minutes.

If you're still copying booking form submissions into Jobber by hand, or relying on staff to forward emails into a job, you're one busy afternoon away from a dropped job. Here's the full setup process, and what to look for in a booking system that actually talks to Jobber.

What a Jobber Booking Integration Actually Does

A proper integration does three things the moment a customer books:

• Creates a Jobber Request with the client name, address, and contact info pre-filled
• Assigns it to the right tech based on service area — not whoever picks up the phone first
• Locks in a scheduled time that syncs with your team's calendars so there are no double-books

What it does not do — at least with Cartoply — is import your existing Jobber service areas. You build your territories inside Cartoply itself, using ZIP codes, cities, counties, or a radius. That takes 10 minutes and gives you more precision than Jobber's native service area settings anyway.

If you want to understand the gaps in Jobber's built-in scheduling before you set this up, Jobber Scheduling: What It Does and What's Still Missing is worth a quick read first.

How to Set Up Automatic Job Creation From Online Bookings

1. Connect your Jobber account — authorize the Cartoply ↔ Jobber OAuth connection in Settings.
2. Draw your service territories — assign each ZIP code, city, or radius zone to one technician.
3. Map each territory to a tech's calendar — set their working hours and buffer time between jobs.
4. Enable the Jobber Request trigger — toggle "Create Jobber Request on new booking" in the integration panel.
5. Embed your booking link — add the popup or inline iframe to your website's "Book Now" button.
6. Test with a live address — book a job yourself to confirm the right tech is assigned and a Request appears in Jobber.

That's the entire flow. The customer enters their address, Cartoply matches it to the correct territory, shows only the availability for that tech, and fires a Jobber Request the instant they confirm. Your dispatch board stays clean. Your techs only see their own jobs.

Why Generic Booking Tools Fall Short for Multi-Tech Teams

Calendly and Acuity are excellent for single-person businesses. They fall apart the moment you have three or more techs covering different parts of a city. Without territory logic, every inbound booking hits a round-robin queue or lands on whoever has an open slot — regardless of whether that tech is 40 minutes away from the job. You end up with the exact problem most home service owners know too well: techs driving past each other's jobs.

The other failure mode is data fragmentation. A booking tool that doesn't connect to Jobber means someone has to manually create the job, enter the client, set the address, and assign the tech. That's four steps that can each go wrong on a busy day. An automated lead assignment system for HVAC and plumbing companies eliminates all four.

For teams with 3–20 techs, the core requirement is simple: the booking system has to understand geography. If it doesn't know that Tech A covers the north side and Tech B covers the south, it can't route correctly — and Jobber can't fix that gap on its own.

What to Look for in a Jobber-Compatible Booking System

Before you commit to any integration, check for these five things:

• Native Jobber connection — not a Zapier workaround that breaks when field names change
• Territory-based assignment — routes by address, not just availability
• One public booking link — customers book without knowing which tech they'll get; each tech only sees their own jobs
• Deposit collection — Stripe integration to collect payment or a deposit before confirming the job (this alone cuts no-shows significantly — see Deposit vs Full Prepayment: Which Reduces No-Shows More?)
• Calendar sync — two-way sync with Google Calendar or Outlook so your techs' personal blocked time is respected

Cartoply's location-aware scheduling features were built specifically for this workflow — one booking link, territory routing, Jobber Request creation, and optional deposit collection, all in a single setup.

Common Setup Mistakes to Avoid

These are the four issues that cause the integration to misfire:

• Overlapping territories — if two techs share a ZIP code with no tiebreaker rule, bookings will land randomly. Assign every ZIP to exactly one tech, or use a round-robin rule explicitly for shared zones.
• Stale calendar availability — if a tech blocks a day in Google Calendar but Cartoply hasn't synced, customers can book into that gap. Keep two-way sync on and test it monthly.
• No buffer time between jobs — back-to-back bookings with no travel buffer create late arrivals that cascade all day. Set at minimum a 30-minute buffer for most residential service calls.
• Skipping the test booking — always submit a test booking from a real customer address before going live. Confirm the Jobber Request appears, the correct tech is assigned, and the calendar event blocks properly.

Frequently Asked Questions

Does Jobber have a built-in online booking system?

Jobber has a client hub where existing clients can submit work requests, but it's not a public-facing booking page that new customers can discover and self-schedule on. For inbound bookings from your website — with time slot selection and automatic job creation — you need a third-party booking tool integrated with Jobber via the API.

How does Cartoply create Jobber jobs from online bookings?

When a customer completes a booking in Cartoply, the integration immediately creates a Jobber Request with the client's name, contact details, property address, and the scheduled date and time. The Request is assigned to the technician whose territory matches the customer's address. No manual entry is required on your end.

Can I use Zapier to connect a booking tool to Jobber?

Yes, but it adds a layer of fragility. Zapier workflows break if field names change, if a zap hits its task limit, or if the trigger fires before Jobber's API confirms the Request was created. A native integration like Cartoply's handles error handling and field mapping internally, which is more reliable for production use.

What happens if a customer enters an address outside my service area?

With territory-based booking, Cartoply won't show available time slots for addresses that fall outside your defined zones. The customer sees a message that their address isn't currently served — which is better than taking a booking you can't fulfill or sending a tech on a two-hour round trip.