Dispatch Board Management + Optimization

Why this matters

The dispatch board is the operating system of a service business. Who's going where, when, in what order = the difference between a profitable 8-job day + a 5-job money-loser. Bad dispatch costs 30 - 50% of potential revenue through drive time + missed appointments + tech idle time. Modern field-service software automates most decisions, but the dispatcher's judgment + the underlying discipline still matter. This is the working framework.

The dispatch board's job

The dispatch board (physical OR software) shows:

• Today's scheduled jobs
• Which tech is assigned to each
• Job time window
• Job address + ETA
• Customer info + service type
• Job status (en route, on-site, complete)

Good dispatch maximizes:

• Tech billable hours per day
• Customer-promised time windows met
• Same-day-service capacity
• Geographic efficiency (route density)
• Skill match (right tech to right job)

Daily dispatch rhythm

Morning (5:30 - 7:30 AM):

• Review today's bookings
• Confirm tech availability (any sick/no-show)
• Plan routes per tech
• First job dispatched

Mid-morning (9:00 - 11:00 AM):

• Track tech progress
• Adjust as jobs run long / short
• Receive new emergency calls
• Slot them into routes

Afternoon (12:00 - 4:00 PM):

• Monitor on-site times
• Pre-plan tomorrow if today is light
• Handle customer reschedule requests

End of day (4:00 - 6:00 PM):

• Confirm all jobs complete
• Review what didn't go as planned
• Note adjustments for tomorrow

Route density math

The critical metric: stops per truck per day.

For residential service:

• High-density urban: 8 - 14 stops/day per tech possible
• Suburban: 6 - 10 stops/day
• Rural: 4 - 7 stops/day

What drives stops:

• Geographic clustering (jobs close to each other)
• Job complexity (simple repairs vs full installs)
• Drive time between stops
• Customer time windows
• Emergency calls (interrupt flow)

A tech running 10 stops a day produces two thirds more revenue than the same tech running 6, on the same wage, the same truck and the same overhead. Every one of those four extra stops is close to pure margin. Dispatch is the difference.

Geographic clustering

The single biggest dispatch lever: assign each tech a daily territory.

By zip code clusters: tech A serves [list of zips], tech B serves another set.

By neighborhood / route: tech A is "north side" today, tech B is "south side."

By drive-time clusters: software calculates ideal job groupings.

The math: 20 minutes drive between 2 jobs vs 5 minutes = 15 minutes saved × 6 transitions/day = 90 minutes recovered per day per tech = 1.5 extra jobs.

Skill matching

Not all jobs are equal:

• Senior tech: complex diagnostics, repeat-customer relationships, installs
• Mid-level: standard repairs, tune-ups
• Apprentice/helper: simple repairs, maintenance, route support

Dispatcher matches tech skill to job requirement. Sending senior tech to a filter change = wasted senior-tech time.

CRM systems with skill tags automate this.

Time windows

Customer-facing time windows:

• "8 - 12" (4-hour AM window)
• "12 - 5" (5-hour PM window)
• Same-day: emergency only

Customer expectation management:

• Confirm 24 hours before
• Text on arrival ("I'm 30 minutes out")
• Update if delayed
• Apologize + reschedule if needed

Tight windows: better customer satisfaction; harder dispatch. Trade-off matters per market.

Same-day service capacity

Reserve 1 - 3 slots per tech per day for same-day emergencies:

• Walk-in customers
• After-hours emergencies routed to next-day
• Membership-priority customers
• High-value commercial accounts

Without reserved capacity, every same-day request bumps a scheduled customer.

Emergency interruptions

Emergencies disrupt the route:

• Burst pipe customer
• AC dead in 95°F heat
• Lockout

Decision tree:

1. Severity assessment (true emergency vs urgent)
2. Membership status (members typically prioritized)
3. Revenue / margin (commercial customer with high LTV)
4. Distance from current tech's route (5 minutes away? 30 minutes away?)
5. Re-routing impact (which scheduled customer gets bumped?)

Document each emergency decision; track impact on scheduled customers.

Dispatcher's daily tools

Field-service software (the modern backbone):

• ServiceTitan, Housecall Pro, Workiz, Manuall
• Auto-scheduling + route optimization
• Real-time tech tracking
• Customer communication

GPS / telematics:

• Tech location visible in real-time
• ETA accurate
• Customer communication automated

CRM:

• Customer history at fingertips
• Skill tags + preferences
• Service history

Phone system:

• Inbound call routing
• After-hours coverage
• Customer hold music + scripting

Tech behavior + dispatch discipline

Tech's role:

• Communicate progress (clock in/out of jobs)
• Update status as jobs complete
• Don't reschedule without dispatcher
• Drive efficiently between stops

Dispatcher's role:

• Hold tech accountable to schedule
• Push back on tech requests that disrupt route
• Resolve conflicts at intermediate priority

This is a teamwork relationship. Dispatch doesn't dictate; tech doesn't ignore. Mutual respect + clear protocols.

Common dispatch mistakes

Over-promising customer windows

• "I'll have someone there in an hour" when realistic is 3
• Customer disappointed when window missed
• Better: realistic windows + early arrival surprise

Under-utilizing dispatch software

• Manual scheduling missing optimization
• Routing inefficiencies invisible
• Customer communications inconsistent

No emergency protocol

• Each emergency handled ad-hoc
• Scheduled customers bumped without reason
• Tech frustrated by constant re-routing

Forgetting customer communications

• Customer wonders where tech is
• Anxiety + complaint risk
• Auto-text on arrival prevents 80% of "where are you?" calls

Skill mismatch

• Senior tech doing simple work
• Apprentice doing complex work
• Productivity loss + customer mismatch

Dispatcher hire profile

For 1 - 3 truck operation: owner often dispatches.

For 4+ truck operation: dedicated dispatcher.

Good dispatcher traits:

• Calm under pressure
• Communicator (both to techs + customers)
• Operations-minded (efficiency + KPIs)
• Customer-empathetic
• Technically literate (software + CRM)

Pay. ROI: capturing 1 - 3 extra jobs/day across the fleet pays back many times over.

KPIs to track

Daily:

• Jobs scheduled
• Jobs completed (on time / late / cancelled)
• Tech utilization (billable hours / clock hours)
• Customer complaint count
• Same-day emergency count

Weekly:

• Average revenue per truck per day
• Average stops per truck per day
• Tech turnover / OT hours
• Customer satisfaction (NPS or similar)
• Dispatch-related complaints

Monthly:

• Trends across all of the above
• Comparison to prior periods
• Specific improvement targets

References

• ServiceTitan, Housecall Pro, Manuall dispatch documentation
• "The Service Manager Handbook" industry guides
• PHCC dispatch + customer service training
• Manuall internal: Optimize Field Service Routes, Customer Communication Standards