What can dispatch data tell me that revenue reports can't?
Dispatch data shows whether you could have taken the work. It carries appointment times, arrival windows, travel, reschedules, cancellations and unassigned backlog. Revenue reports only show the jobs that happened. When demand rises and revenue does not, dispatch data is where you find out whether the problem was lead quality or simply that there was nowhere to put the job for nine days.
Revenue reports only contain survivors
Every completed job is evidence of demand that made it all the way through. The jobs that never happened — the caller who would not wait until Thursday, the appointment cancelled after two reschedules, the emergency that went to a competitor — leave almost no trace in revenue reporting.
Dispatch data is where those losses are visible. It is the closest thing most service businesses have to a record of demand they failed to serve.
The signals worth pulling out
- Days to first available. Measured per business unit, per day. When this stretches, booking rate falls for reasons that have nothing to do with how the phone is answered.
- Reschedule count per job. Two reschedules is a strong predictor of eventual cancellation and of a poor review.
- Unassigned and unscheduled backlog. Work sold and not yet on a board. Ages quietly and cancels loudly.
- Jobs per technician per day and on-site versus travel time. The difference between a capacity problem and a routing problem.
- Cancellation reason, where captured. Usually the worst-maintained field in the system and the most valuable one when it is maintained.
The diagnostic that settles a common argument
Marketing says the leads are fine. Operations says the leads are junk. Put booking rate and days-to-first-available on the same timeline. If booking rate falls in the same weeks the schedule fills, the constraint is capacity, and buying more demand makes the customer experience worse rather than the revenue better.
If booking rate falls while the schedule has room, the constraint is intake or lead quality, and that is where call analysis tells you which. The two explanations look identical in a monthly summary and completely different on a daily overlay.
Capacity should feed the media plan
Most service businesses run marketing and scheduling as separate universes. They are the same system with a delay in between. When the board is full for two weeks, the marginal ad dollar buys frustration; when a crew is open on Tuesday, it buys a job.
Wiring capacity signals into demand decisions is one of the more concrete things operational AI does in a service business, and it needs dispatch data joined to media data to work at all. It is also a good test of whether an integration is real, because it requires both sides to be current, not monthly.
Topics: dispatch · capacity · scheduling · utilization
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.