Pillar 2 — Run the Office
Routes optimized.
Drive time recovered.
Emergencies rerouted.
Your techs get paid for time behind the windshield same as they get paid for time on jobs. Most shops accept that as the cost of doing business. Dispatcher doesn’t. Every route is calculated against the fastest path between every job, every morning — and recalculated the moment an emergency call lands. The windshield time that was always going to be there, finally turned back into time your techs can actually earn.
THE WINDSHIELD GAP
Home-services techs spend roughly 30%¹ of paid hours behind the windshield.
Your dispatcher schedules the day in the order calls came in. A 9 AM in Winter Park, a 10:30 in Kissimmee, a 12:15 back near Winter Park. The tech drives 45 minutes between two of those stops — even though there’s another job 10 minutes from Winter Park that could have been slotted in instead. Nobody flagged it. The dispatcher doesn’t have the cognitive room to optimize against every job on every truck in real time, so she doesn’t. So the truck drives. And the job that should have been done that day gets pushed to tomorrow — or, more often, never quoted.
The math you’re not running: a 5-truck shop with techs averaging 8 paid hours a day burns roughly 12 fleet-hours a day in windshield time — about 60 hours a week across the fleet.²Even a modest 15–20% reduction through optimized routing (industry-typical for AI dispatch) recovers ~2 hours of fleet windshield time per day — roughly the equivalent of one additional billable hour per truck per day. Same techs. Same trades. Same trucks. The drive time was always going to happen; some of it just doesn’t need to.
Windshield time is unbilled time. Most operators accept it because they have no instrument to measure it and no system to shave it. Dispatcher is the instrument and the system.
WHAT DISPATCHER DOES
Four steps from morning route to mid-day emergency to weekly digest.
Dispatcher runs three operations every day — morning optimization, real-time emergency response, end-of-day reporting — plus reroute-on-demand whenever the schedule moves. Your dispatcher (the person) gets her cognitive room back: closing inbound calls, selling work, managing techs. The route math runs in the background. The patterns surface every Friday.
- 1
Calculates optimal routes every morning.
Reads your full schedule from your CRM the moment the morning huddle ends. Calculates the fastest path between every job across every truck — accounting for traffic patterns, tech skill matching, and customer time-window constraints. The sequence your dispatcher used to draft by hand on Monday morning is now the sequence the techs see in their app before they leave the lot.
- 2
Dispatches techs in the optimized sequence.
Each tech sees their route in the existing app they already use (Jobber, Housecall Pro, ServiceTitan, GoHighLevel, FieldEdge, Service Fusion). No new tool, no separate login, no double-entry. The first stop, the second stop, the route between them — all calibrated for the fastest path, and the path the tech actually wants to drive.
- 3
Reroutes the closest qualified tech when emergencies land.
The moment an emergency call lands — no-heat in February, no-cool in July, water leak any month — Dispatcher identifies the 3 nearest techs with the right skill and equipment, picks the one with the lowest disruption to their day, and recalculates everyone’s afternoon. The displaced job (the routine one that just got bumped) auto-reschedules with a customer-friendly SMS. Total elapsed time: minutes, not phone calls.
- 4
Reports drive-time recovered + fleet-hours saved in a weekly digest.
Every Friday afternoon you see the digest: how much windshield time the fleet shaved, which tech routes ran ahead of schedule (and which ran behind), which job types are pulling longer drive times than expected, and how many emergencies got rerouted without your dispatcher touching the schedule. The patterns nobody sees day-to-day become obvious week-to-week.
THE PROOF (IN OPERATIONAL UNITS)
~2 hours of fleet windshield time recovered per day. 15–20% drive-time reduction. Emergency reroutes in minutes.
Dispatcher’s value doesn’t show up as a dollar number in your QuickBooks — it shows up as time. A 5-truck shop running an 8-hour day burns roughly 12 fleet-hours daily in windshield time. Optimized routing recovers 15–20% of that — about 2 hours a day across the fleet, roughly the equivalent of one additional billable hour per truck per day. Same techs, same trades, same trucks. The windshield time was always going to happen. Some of it just doesn’t need to anymore.
Emergency reroutes happen in minutes, not the 20–30 minutes a human dispatcher needs to manually recompute three trucks’ worth of afternoon routes. The closest qualified tech gets the call; the displaced job auto-reschedules. Your dispatcher gets her morning back to close inbound calls and sell work — instead of playing Tetris with truck routes.
~2 hr/day
fleet windshield time recovered
15–20%
drive-time reduction (industry-typical AI dispatch)
minutes
emergency reroute response
WHAT AN EMERGENCY REROUTE LOOKS LIKE
One no-heat call. Three nearest techs evaluated. One reroute. Three minutes elapsed.
Emergency dispatching is the moment Dispatcher matters most. Manual dispatch on an emergency = 20–30 minutes of phone calls and gut-feel routing. AI dispatch = the closest qualified tech rerouted in minutes, with zero operator-time spent.
Inbound call — Tuesday, 11:32 AM (no-heat emergency, outdoor temp 38°F)
“My furnace just stopped and the house is dropping fast. I’ve got a baby. Can someone come today?”
Dispatcher — Tuesday, 11:33 AM (evaluating fleet)
“3 nearest qualified techs evaluated. Tech 2 (Mike) finishing current job in 18 minutes, 12 minutes from emergency address, scheduled afternoon stop (HVAC tune-up, non-urgent) auto-bumps to Thursday. Best fit by drive-time + skill + customer impact. Selecting Tech 2.”
Dispatcher — Tuesday, 11:34 AM (tech notification + customer comms)
“Mike notified, route updated in his app — emergency stop inserted at 12:15 PM. Tune-up customer auto-rescheduled to Thursday 1–3 PM with customer-friendly SMS sent + reschedule link. Emergency caller texted: ‘Mike is on his way — ETA 12:15 PM. He’ll text 30 min before he arrives.’”
[Emergency dispatched in 3 minutes. Mike arrived 12:08 PM (7 minutes ahead of ETA). Furnace repair completed at 1:42 PM. Tune-up customer accepted Thursday reschedule. Operator hours on this thread: zero — the dispatcher (the person) was on a sales call the entire time.]
The dispatcher (the person) didn’t touch this thread. She was closing an inbound sales call the whole time the reroute happened. The capacity to handle emergencies didn’t come from adding staff — it came from giving the existing staff their cognitive room back.
THE BOUNDARIES
Routine routing. Automated. Anything custom or sensitive comes to you.
Standard dispatching work — daily optimization, emergency reroutes, mid-day reschedules — runs without operator touch. Anything involving custom commercial SLAs, tech preferences, overtime rules, or routes the optimizer isn’t confident about gets flagged so you can handle it personally.
✓Dispatcher handles
- Daily route optimization (every morning, all trucks)
- Real-time emergency rerouting (closest qualified tech, recalc in minutes)
- Mid-day reschedule handling (when a job runs over or a tech is late)
- Drive-time + mileage reporting (weekly digest)
- CRM calendar sync (Jobber, Housecall Pro, ServiceTitan, GoHighLevel, FieldEdge, Service Fusion)
- Multi-truck capacity balancing
- Same-day priority insertion (commercial emergencies)
- Tech-skill matching (the right tech for the right job, every time)
→Maximus flags for human approval
- Custom dispatching rules (commercial contract SLAs with negotiated response windows)
- Tech preference overrides (“Mike refuses jobs in zone X”)
- Repair dispatch overlaps with installation crews
- Cross-shift tech reassignment (4-day-week / weekend-only crews)
- Routes that would violate tech overtime rules
- Dispatcher manual override request (judgment call moments)
- Anything where the optimizer’s confidence score is below threshold
The judgment calls stay with you. The 12 fleet-hours of windshield time that needed to be shaved every day but never quite were — that’s the agent’s job now.
Who you’re buying from
Nirav DoshiOwner, Temperature Pros Orlando · CDP partner since 2012
Dispatcher was the agent I didn’t think I needed — until I realized my dispatcher was spending half her day chasing drive-time problems instead of selling work. Same techs. Same trades. Same trucks. Same dispatch board. But now my dispatcher’s job is actually closing inbound calls, not playing Tetris with truck routes. The drive time that was always going to happen just doesn’t take as long anymore. The capacity that was already there finally shows up on the schedule.
You’re not buying a one-man-show. Maximus is built and operated by Complete Data Products — a 35-year-old technology company my brother and I bought in 2012. We’ve shipped AI and data systems for Fortune 500 clients since long before AI was a buzzword. Tech lead Jason Darling has been at CDP for 22 years — predates my ownership; institutional memory you can’t buy. Operations lead Kait Kluz joined 8 years ago when we rebuilt around AI; she’s the person making sure the team ships what we sell. Founding 20 customers get me directly on application and during onboarding; the org is here for everything after.
Frequently asked
Questions contractors ask about Dispatcher.
How does it know which routes are actually optimal?
What about same-day emergencies — does it re-route mid-job?
Does it work with my existing CRM and scheduling?
Won't my techs get confused if the route changes mid-day?
What happens if a tech says 'I can't do that job route'?
When the drive time gets shorter.
Less time driving. More time earning. Every truck. Every day.
Dispatcher is included in every Maximus subscription — Founding 20 ($497/mo or 8% recovered, whichever’s higher) or Standard ($697/mo or 10%). The math has to work or you don’t pay. 90-day money-back guarantee on the entire team.
Founding 20 — limited·$497/mo or 8% recovered·90-day money-back·48-hour deploy
Same techs. Same trades. Same trucks. Same dispatch board. Just routes that math knows are faster than gut feel.
Footnotes
- ¹ Roughly 30% of paid hours behind the windshield. Aggregated from home-services fleet-utilization benchmarks (similar provenance to /agents v2.1 footnote ¹ + Build G/H/I/J footnote ¹). Windshield-time percentage varies by trade (plumbing higher, garage doors lower), service-area density (rural higher than urban), and dispatch discipline. The 30% midpoint reflects typical $1M–$5M residential home-services shops in mid-density metro service areas. Shops with unstructured dispatch discipline run higher (35–40%); shops with disciplined dispatch run lower (20–25%).
- ² 12 fleet-hours/day windshield-time calculation. Methodology: 5 trucks × 8 paid hours/day × 30% windshield-time fraction = 12 fleet-hours daily. 15–20% reduction via AI dispatch optimization (industry-typical range from published routing-optimization studies + AI dispatch deployments) recovers ~2 hours of fleet windshield time per day — roughly equivalent to one additional billable hour per truck per day at the conservative end. Per-shop variance depends on starting baseline + route density + emergency-call frequency.