How Jobber Scheduling Works—and Where Territories Fit

Jobber can schedule work, assign team members, show visits on a map, and screen online-booking requests by ZIP code. The remaining gap for some multi-crew businesses is more specific: making a customer address choose the right territory owner before available times appear.

That distinction matters. Jobber is a field-service platform with a real schedule. Cartoply is not a replacement dispatch board or route optimizer. It is a territory-aware front door that can hand qualified bookings into Jobber.

What Jobber scheduling does today

Jobber's current scheduling workflow covers the core job lifecycle:

schedule jobs, visits, assessments, and tasks;
assign work to one or more team members;
view appointments on a calendar or map;
organize a day's route order in the mobile app; and
let customers request or book work online.

Online booking can also use service areas. A business can define areas by ZIP code, decide whether an outside-area request is blocked or collected for review, and show booking availability only after the customer's address is entered.

Jobber also offers efficient scheduling for online booking. You choose a drive-time limit, and Jobber uses the client address plus each team member's assigned work to determine who is available. If more than one team member qualifies, Jobber says the assignment is random among the eligible team members.

Those are meaningful capabilities. Any comparison that says Jobber cannot screen service areas, consider drive time, or schedule online work is out of date.

The narrower problem territories solve

Drive-time eligibility answers: Who can reach this address around this time?

Territory ownership answers: Which configured team should own this address?

Those are not always the same question. A company may divide a metro by franchise boundary, sales rep, branch, county, ZIP code, service radius, or a hand-drawn polygon. The owner may want every new lead from an address routed to the same group even when several crews happen to be nearby.

Cartoply resolves that rule before showing availability:

The customer opens the selected event type’s booking page and enters the service address.
Cartoply matches it to a ZIP, city, county, radius, polygon, or drive-time territory.
Cartoply filters eligible people by the selected event type, its routing rules and the matching service territory, then uses their availability to offer times.
The customer chooses a time from that territory owner's availability.
A configured booking creates a Jobber Request with a scheduled Assessment and matched Jobber user assignment when configured.

Use it when the address needs a separately configured territory owner. Overlapping coverage can still create an eligible pool; event distribution and availability rules apply.

Jobber and Cartoply are different layers

Need	Jobber	Cartoply
Run jobs, visits, and the daily schedule	Yes	No
Assign work and view it on a map	Yes	No
Screen online booking by ZIP code	Yes	Can add richer territory shapes
Consider drive time when showing availability	Yes	Can define drive-time territories
Express a separately configured territory boundary	Test native booking settings against your rule	ZIP, city, county, radius, polygon or drive-time territories; eligible rep/group assignment
Route optimization, live GPS, or a dispatch board	Native scheduling and route tools; verify the specific feature and plan	No

The honest positioning is simple: use Jobber to run the work. Add Cartoply only if your inbound-booking rules depend on territory ownership that Jobber's eligible-team-member flow does not express.

When Jobber alone is enough

You probably do not need another tool if:

one office or a small team serves the same area;
any qualified team member can take the next booking;
ZIP-code screening is precise enough;
the dispatcher wants to assign or adjust work after the request arrives; or
the main problem is day-of route optimization or GPS tracking.

Jobber already covers those workflows better than a territory-booking layer should try to.

When a territory layer may help

Consider a territory layer when:

different branches own different counties or ZIP groups;
reps have protected sales or service areas;
franchise or licensing boundaries must be enforced at intake;
an address should reach the configured eligible territory group; where coverage overlaps, assignment also depends on the event’s distribution and availability rules; or
customers should see only eligible people’s times for the selected event type and matching service territory.

The test is not “Do we use Jobber?” It is “Does address ownership need to be decided before the booking reaches Jobber?”

Frequently asked questions

Does Jobber support service areas?

Yes. Jobber's online booking can screen client addresses against service areas defined by ZIP code. It can block an outside-area booking or collect the request for follow-up, depending on the configured rule.

Does Jobber consider drive time?

Yes. Jobber's efficient-scheduling option can limit availability by drive time from the team member's assigned work to the new client's address.

Does Cartoply replace Jobber scheduling?

No. Cartoply does not replace the job schedule, dispatch board, route planning, or GPS workflow. It resolves an inbound address to a territory owner and then passes the booking to Jobber.

Can a Cartoply booking create work in Jobber?

A configured organization booking can create a Jobber Request with a scheduled Assessment and matched Jobber user assignment when configured. Territories are configured in Cartoply; Jobber service areas are not imported.

Decide at the address, then run the job in Jobber

If your team already knows that every north-side lead belongs to one branch and every western county belongs to another, the booking page can enforce that rule before anyone in the office reassigns the work.

Check your booking boundary. For setup details, read the territory guide and Jobber connection.