Lost revenue from dispatch problems: what to find, fix, and track
Dispatch problems cost home-service companies money in ways that rarely show up clearly in a CRM report: jobs routed to the wrong tech, drive time that kills capacity, callbacks that erode margin, and revenue that slips out between booking and invoice. This page breaks down where that revenue goes and how real-time visibility changes what a dispatcher and owner can do about it.
The problem
The dispatch problem that costs money you cannot see in a report
Picture a Monday morning in a 10-truck HVAC shop. The dispatcher has 22 jobs queued, a tech calling out sick, and 4 emergency calls stacking up on hold. By noon, 3 callbacks from last Friday still have not been rescheduled, one high-value installation job got routed to the closest tech instead of the most qualified one, and two afternoon slots were left open because the board said capacity was full even though two service calls finished early. Nobody on the team knows how much revenue that sequence cost. The dispatcher made reasonable calls under pressure. But the information they were working from was incomplete, and there was no real-time view of what was slipping through.
Why dispatch revenue leakage is hard to see in normal reports
Standard CRM reports tell you what jobs were completed and at what revenue. They do not tell you which jobs should have been completed, which callbacks went unscheduled for three days, or how much capacity was sitting empty at 2pm while the morning queue was overloaded. The gap between what happened and what could have happened is where dispatch revenue lives, and it is invisible in any report built on completed data.
Most dispatch problems compound quietly. One poorly routed tech creates a callback. The callback takes a prime appointment slot. The slot that gets moved bumps another job. By month-end, the revenue looks short without an obvious cause. A post-hoc report shows completed jobs; it does not show the routing decision that started the chain.
The data to diagnose these problems usually exists across your CRM, dispatch board, and job history, but it lives in separate views. A dispatcher watching one screen does not have a live signal showing callback volume, average drive time, open capacity by time block, or tech utilization by hour. They are making decisions without a full picture, not because they lack skill but because the information is not in front of them in real time.
Common dispatch mistakes, the revenue they cost, and the KPI that reveals them
| Dispatch mistake | How revenue leaks | KPI that reveals it | What better visibility enables |
|---|---|---|---|
| Routing by proximity, not qualification | Wrong tech creates a callback; second visit costs labor with no new revenue | Callback rate by tech; first-call resolution rate | See callback rate by tech live and adjust future routing before it repeats |
| Leaving afternoon capacity empty after morning calls finish early | Booked revenue per available tech hour goes down; idle time erodes margin | Tech utilization rate; capacity by time block | Spot open slots in real time and move callbacks or same-day calls into them |
| Unscheduled callbacks aging 2-3 days | Customer cancels or calls a competitor; callback revenue is lost entirely | Open callback count; days-to-reschedule; cancellation rate | Live callback queue with aging clock forces same-day prioritization |
| Dispatching a senior tech to a minor diagnostic call | Senior tech is unavailable for the high-margin install; less experienced tech handles it poorly | Revenue per tech by job type; average ticket by tech | Rank techs by job type performance so dispatchers match qualification to job complexity |
| Excess drive time from poor geographic clustering | Fewer completed jobs per tech per day; higher fuel and labor cost as a percentage of revenue | Average drive time per tech; jobs completed per truck per day | Track drive time and jobs-per-truck daily to identify which routes need restructuring |
| High-value installs split across days when a full-day block is needed | Install job extends, tech overtime adds cost, customer satisfaction drops | Install completion rate; average install duration vs. estimated | Flag install jobs that consistently run over estimated time to adjust future scheduling |
Warning
Data visibility gap: your dispatch board and your revenue report are not connected
Most home-service companies track revenue in their CRM or QuickBooks and track dispatch in a separate scheduling board. Neither system shows you the relationship between a routing decision made at 8am and the revenue outcome at 5pm. The dispatcher cannot see the revenue impact of a choice in real time. The owner sees a soft revenue day at month-end but cannot trace it back to specific dispatch patterns. Closing that gap requires a layer that sits across both systems at once.
Dispatch KPIs to inspect when revenue is short
When monthly revenue comes in below target but booked job count looks normal, these are the dispatch metrics to check first. Each reveals a different layer of the same problem.
- Callback rateHigh callback rate usually signals routing or diagnosis problems, not just tech skillPoor
- Current
- Above 12%
- Target
- Below 8%
- Tech utilization (booked hours / available hours)Low utilization with a full board means capacity is being left on the tableWatch
- Current
- Below 70%
- Target
- 75% or higher
- Open callbacks aging over 24 hoursCallbacks sitting overnight are more likely to cancel or call a competitorPoor
- Current
- More than 5 per day
- Target
- Fewer than 3
- Jobs completed per truck per dayVaries by trade; lower numbers often reflect drive-time inefficiencyWatch
- Current
- Below 3.5
- Target
- 4 or more
- Average ticket by techLarge variance suggests mismatched routing, not just tech performance differencesWatch
- Current
- Wide variance across techs
- Target
- Consistent within trade and job type
- Cancellation rate on dispatched jobsPost-dispatch cancellations often reflect scheduling delay or poor expectation-setting on ETAPoor
- Current
- Above 6%
- Target
- Below 4%
| Metric | Current | Target | Status |
|---|---|---|---|
| Callback rateHigh callback rate usually signals routing or diagnosis problems, not just tech skill | Above 12% | Below 8% | Poor |
| Tech utilization (booked hours / available hours)Low utilization with a full board means capacity is being left on the table | Below 70% | 75% or higher | Watch |
| Open callbacks aging over 24 hoursCallbacks sitting overnight are more likely to cancel or call a competitor | More than 5 per day | Fewer than 3 | Poor |
| Jobs completed per truck per dayVaries by trade; lower numbers often reflect drive-time inefficiency | Below 3.5 | 4 or more | Watch |
| Average ticket by techLarge variance suggests mismatched routing, not just tech performance differences | Wide variance across techs | Consistent within trade and job type | Watch |
| Cancellation rate on dispatched jobsPost-dispatch cancellations often reflect scheduling delay or poor expectation-setting on ETA | Above 6% | Below 4% | Poor |
A 4-step action plan to reduce dispatch revenue leakage
01 1. Count the leaks before trying to fix them
Pull your callback rate, cancellation rate on dispatched jobs, and open callback aging for the last 90 days. If you cannot get those three numbers from your CRM in under ten minutes, the data is there but visibility is not. That gap is worth solving before anything else. For teams using ServiceTitan or Housecall Pro, the data exists in job history; it usually takes a custom pull or an external layer to surface it daily.
02 2. Track tech utilization in real time, not at month-end
Utilization by tech and time block is the clearest signal of unbooked capacity. A dispatcher who can see that three techs have open afternoon slots at 1pm can move aging callbacks into those slots the same day. A dispatcher who sees that information on a Friday review report cannot. The fix is visibility during the day, not a better end-of-month analysis.
03 3. Match techs to jobs by performance, not proximity
Build a simple routing rule: for high-value installs or complex diagnosis calls, dispatch by first-call resolution rate and average ticket rather than drive time. First-call resolution data is almost always in your CRM; it just is not surfaced in the dispatch view. Surfacing it changes the decision the dispatcher makes in real time.
04 4. Build a daily dispatch review into the management cadence
A 10-minute end-of-day review of that day's callback count, open aging callbacks, and utilization by tech is enough to spot the patterns quickly. Do this with a live dashboard rather than a spreadsheet export, and you can catch a dispatcher habit before it compounds across the month. Coaching the dispatcher on routing choices with live data is faster and less confrontational than reviewing a month of mistakes after the fact.
What a dispatch visibility board shows in real time
A dispatch board built on real operational data surfaces the metrics a dispatcher and ops manager need to catch revenue leaks during the day, not after it. The tiles below reflect the kind of view a 10-truck home-service company might configure for a busy Tuesday.
Figures are illustrative. Your live board reflects your own connected sources and the KPI definitions your team agrees on. Benchmarks vary by trade, season, market, and business model.
Info
Illustrative revenue impact: what one percentage point of callback rate represents
Consider a plumbing company running 400 dispatched jobs per month at a 480 dollar average ticket. A callback rate of 11 percent means roughly 44 jobs require a return visit. Each callback ties up one tech visit with no new revenue and risks the customer canceling or leaving a poor review. If better routing and real-time visibility reduced the callback rate to 8 percent, that is 12 fewer callbacks per month. At 480 dollars per job, those 12 slots could be filled with new revenue-generating calls instead. The specific numbers vary by trade, job mix, and season; the direction of the math is the point, not the precision. Callback rate is one of the highest-leverage metrics a dispatcher controls.
Where the data to diagnose dispatch problems actually lives
For teams using ServiceTitan, callback and job history data lives in job records and dispatch logs. Utilization and drive time often require a custom report or a third-party layer to surface in a usable format during the day. Housecall Pro users face a similar situation: the data is in the system but the dispatch view and the performance view are separate.
A platform designed to consolidate from 50 or more sources can pull dispatch job data, callback records, and tech performance together into one live view. When connected to a CRM and an accounting system, a dispatcher can see callback rate and utilization alongside revenue impact in the same board, instead of pulling three separate reports and reconciling them manually.
The related page on diagnosing a high callback rate covers that metric in more depth and explains the common root causes. Lost revenue from dispatch problems and callback rate are closely related, but dispatch problems extend further: into capacity, job mix, routing, and install scheduling.
What to take away from this page
- Dispatch revenue leakage is invisible in standard CRM reports because those reports show what was completed, not what capacity was left empty or what jobs were routed poorly.
- Callback rate, tech utilization, open callback aging, and jobs per truck per day are the four KPIs most likely to reveal a dispatch-driven revenue leak.
- The fix is real-time visibility during the day, not a better end-of-month analysis. A dispatcher who can see open afternoon slots at 1pm can act on them; one who sees idle time on a Friday report cannot.
- Routing by qualification (first-call resolution rate, average ticket by job type) rather than proximity is one of the highest-leverage changes a dispatch team can make.
- A 10-minute daily dispatch review with a live board, not a spreadsheet, is enough to catch patterns before they compound across the month.
Frequently asked questions about lost revenue from dispatch problems
Find out what your dispatch data is actually hiding
If your revenue comes in soft some months and the completed job count looks fine, dispatch visibility is worth a close look. In a live demo, we can show you what a dispatch board built on your sources would surface, including callback rate, utilization, and open capacity, so you can see the gaps before the month closes.
Keep exploring
Related
Go deeper