FOR DISPATCHERS

One clear view of the whole day.

Dispatchers juggle people, places, times, emergencies, and customer calls. The goal is to make those decisions easier to see and explain.

Something to build on · 01

Know who is available

Start with actual working hours, scheduled appointments, time off, expected duration, and technician skills. An empty-looking space is not useful if the technician is too far away or unavailable for that work.

Something to build on · 02

Handle the schedule that changes

A missed part, urgent repair, or sick employee can disrupt several appointments. The dispatcher needs to move work, understand conflicts, and see which customers must be contacted.

Something to build on · 03

Keep job details close to the calendar

When a customer calls for an update, dispatch should be able to open the job directly from the schedule. The answer should include assigned crew, current status, address, and any known problem without reading an entire activity log.

Something to build on · 04

Make handoffs calm

The next shift needs to know what is still open, why a job moved, and which commitments were made. Clear notes and ownership are more valuable than a crowded board of flashing alerts.

Example to try: A 2 p.m. repair becomes a four-hour job. Dispatch should see the 4 p.m. conflict and know who must be notified.

Something to build on · 05

A practical checklist

  • Find an alternative worker when the scheduled technician calls out.
  • Show travel time and required job skills without guessing real-time traffic.
  • Open the job from a calendar item and find the current customer promise.
  • Hand unresolved appointments to the next shift with an owner and next action.

Good questions

What else would
you like to know?

Does the platform suggest available technicians?

Availability matching is a planned feature to verify in a working build.

Can I filter by installer or apprentice?

Worker types and assignment rules must be tested against actual accounts.

Can dispatch see jobs by branch?

Branch permissions and views are part of enterprise evaluation, not a blanket released claim.

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