From dispatch to invoice
Field service automation,
from intake to invoice
Field-service work is not lost on site. It is lost in the four handoffs around it. Intake, dispatch, proof of work, invoicing: every one of those is a place where information changes hands, and every handoff is where hours and money go missing. Here is what each one costs and what it looks like once it is built, from systems that are running rather than proposed.
Want to know what this costs in your shop?
I will work out your three biggest time sinks, in hours and dollars. Free, in writing, within 72 hours.
No newsletter, no sequence. You keep the analysis either way.
Tim Muenzel
builds and runs the systems himself
Gap one: intake, where automated field service starts
Orders arrive through portals, email and phone, and somebody re-enters them into the dispatch system every morning. Forty orders a day at four minutes each is over 600 hours a year spent on typing. Built version: orders are parsed, converted into the exact format the destination requires, transferred, verified and logged individually, with anything ambiguous routed to a person rather than guessed.
Gap two: dispatch, and why field automation is really a visibility problem
The schedule lives in one place, the reality lives in the technicians’ phones, and the gap between them is filled by phone calls. What helps is not a bigger scheduling tool but a single view of what is actually happening: metrics, incidents and attendance in one dashboard with an admin area, which is exactly what I built for a facilities-services company. The value is not the chart. It is that a supervisor stops calling people to find out where things stand.
Gap three: proof of work
Photos in a messaging app, times on paper, completions reported by phone. At the end of the month this becomes an archaeology exercise, and anything that cannot be evidenced quietly does not get billed. That loss appears in no report, and it is usually larger than the administrative time it takes to reconstruct. The fix is structural: time, materials and photos attach to the job rather than to a channel.
Gap four: invoicing, where the field service workflow finally pays
When times sit in one system and jobs in another, invoicing becomes a manual reconciliation, and reconciliations lose line items. Once the job carries its own evidence, the invoice is generated from data rather than memory, and a disputed item is settled in minutes instead of days. This is the gap with the shortest payback, because it converts directly into revenue that was already earned.
What "AI field service software" actually means, and when it does not
Most of what gets sold under that label is ordinary automation with a language model somewhere in the middle. That is not a criticism: reading an inbound email and pulling out the address, the fault description and the requested date is a genuinely good use of one, and it is the single highest-return AI step in this whole workflow. What does not need a model is scheduling, dispatch logic, or anything with a rule you can write down. If a vendor describes deterministic routing as AI, you are paying for a label. The honest split is simple: language and judgement get a model, everything else gets code that behaves the same way twice.
Where to start, in order of what it returns
Automated work orders first, because intake is pure typing and the arithmetic is unambiguous. Proof of work second, because that is where unbilled revenue hides. Dispatch visibility third, because it removes phone calls rather than hours. Invoicing last only because it depends on the other three being in place, not because it matters least; it is usually the one with the shortest payback once the evidence attaches to the job.
What the four gaps cost a 20-person operation
Rough but honest, with every assumption visible. Adjust any line to your own numbers:
| Intake, 40 orders a day at 4 minutes | about 610 hours a year, roughly $30,500 |
|---|---|
| Proof of work, reconstructed monthly | about 176 hours a year, roughly $8,800 |
| Dispatch calls, one hour a day | about 230 hours a year, roughly $11,500 |
| Unbilled work nobody could evidence | unmeasured, and usually the largest of the four |
| First fixed scope | from $6,900, typically intake first |
| Payback on intake alone | roughly four months |
The fourth line has no figure on purpose. It is real and it is usually the biggest, but it is not measured in your business, and an invented number in a total destroys the credibility of the measured ones.
Common questions, answered straight
Do we have to replace our field-service software?
Almost never. The normal shape is that your system stays as the system of record and the manual work in front of and behind it disappears. I build at the edges, not into the core, because core changes are expensive and tie you to one vendor.
Our technicians are not technical.
That is an argument for automation, not against it. The goal is fewer inputs, not more. Anything that can be captured without a person doing something should be, and interfaces get built only where a human genuinely has to decide.
Which gap should we start with?
The one that costs the most, which is not always the most annoying one. Intake usually wins on hours, invoicing usually wins on money. The free teardown puts a number on both so the decision is arithmetic rather than instinct.
How do we know it keeps working?
Because monitoring is part of the build rather than an upsell: every run is logged, failures are reported, and someone finds out before your customer does. That is what an operator retainer covers, from $2,900 a month, cancel monthly.
Related reading
Which of the four gaps is worst at your company?
Free systems teardown: all four priced from your own numbers, with visible assumptions, plus which one to close first. In writing, within 72 hours.
Get your free systems teardown