Scheduling & dispatch

The right tech. The right job.

Make room for the work, the travel, and the unexpected. Explore how ServiceCanopy is designing scheduling around the needs of dispatchers and crews.

In development · workflows described here are planned. Availability, supported devices, and limits have not been verified.

Illustrative workflow · example data
A clearer working day

The right next step.

Today’s plan
08:30
HVAC · Service visitUpstairs system not coolingReview unit history → inspect
10:00
Plumbing · DiagnosticWater heater leakingCheck access → confirm scope
13:00
Office · Follow-upSend the revised estimateExplain options → request approval
One job story. Office to field.

Something to build on · 01

See the real shape of the day

A calendar is useful when it shows who is working, which jobs are booked, how much time they need, and where there is still room. A simple list of appointments is not enough when a technician has two long calls on opposite sides of town. Include travel, breaks, time off, and job duration in the scheduling discussion.

Something to build on · 02

Move work without losing the details

When an appointment changes, the new technician needs the right customer address, notes, equipment history, and expected work. The old assignment should not remain on someone's phone. The office should see the new plan clearly before confirming it with the customer.

Something to build on · 03

Make the schedule understandable

Different people need different views: dispatch wants the whole team, a manager may need capacity for next week, and a technician wants today's ordered stops. Keep labels clear and show conflicts in words, not color alone.

Something to build on · 04

Test an ordinary scheduling problem

Ask for a demonstration of moving a three-hour installation after its assigned technician calls in sick. Can the office find another qualified crew, see the extra travel, avoid an overtime conflict, and update the job without re-entering it?

Example to try: At 8:45 a.m. a technician calls out. The dispatcher needs to protect a noon repair, move the first appointment, and tell the customer what changed. Use this exact scenario as an acceptance test.

Something to build on · 05

A practical checklist

  • Schedule a three-hour install beside a two-hour repair and include realistic travel time.
  • Move the installation and check for conflicting promises to the next customer.
  • Verify whether staff time off and skill restrictions block unsuitable assignments.
  • Confirm calendar dates and time zones remain correct around daylight-saving changes.

Good questions

What else would
you like to know?

What should scheduling software show?

At minimum: appointment, customer, address, assigned technician, status, expected duration, and conflicts that matter.

Can customers reschedule themselves?

Self-service rescheduling is a separate workflow and needs explicit availability confirmation.

Does it account for traffic and travel?

Travel awareness is an evaluation requirement; do not assume real-time traffic optimization is already available.

Your next chapter

Start with one job.
See the whole picture.

Follow an illustrated service call, from the first request to closeout.

See how it works