TL;DR
- Your dispatcher is the gatekeeper of revenue. Every inbound call either becomes a booked job or walks to a competitor — and in plumbing, a missed emergency call is gone in minutes.
- The metrics that matter: calls answered vs missed (especially after-hours), booking/conversion rate, speed-to-answer, dispatch efficiency (drive time, jobs per tech per day), emergency routing time, and first-call resolution.
- Dispatcher decisions directly drive revenue per plumber and average ticket — who gets routed where, and how fast.
- Most owners can't see any of this because the phone system, field software, and spreadsheets don't talk to each other.
- Don't chase published "industry averages." Measure your own baseline first, then watch what moves.
In a plumbing business, the dispatcher sits on top of the money. Every call that comes in is a fork in the road: it either becomes a booked, profitable job or it becomes revenue for the plumber down the street. Yet most owners can tell you their revenue and their tech count off the top of their head, and almost nothing about how well the person answering the phone is actually converting demand into work.
This is the plumbing-specific problem. Your call mix is emergency-heavy — burst pipes, no hot water, sewage backups — and those callers will not wait. A missed after-hours call doesn't go to voicemail purgatory; it goes to the next plumber they can reach. Measuring dispatcher performance is really about measuring how much of that urgent, high-intent demand you're capturing versus leaking.
Below are the metrics that matter, what each one means, why it matters for a plumbing operation specifically, and how to read it.
Calls Answered vs Missed (Especially After-Hours)
What it is: The share of inbound calls that a live person actually answers, versus calls that ring out, hit voicemail, or get abandoned. Break it out by time of day — normal business hours, after-hours, and weekends.
Why it matters: This is the single most important dispatcher metric in plumbing, because your emergency calls cluster exactly when your office is least staffed — nights, weekends, holidays. A homeowner standing in two inches of water is not leaving a voicemail. They're dialing the next result on their phone. Every missed after-hours call is very likely a job you handed to a competitor, often a high-ticket emergency job at that.
How to read it: Look at your missed-call rate as a percentage, then immediately segment it by time. An owner who sees "we answer 92% of calls" feels fine — until they discover that the 8% they miss is concentrated in after-hours emergency windows where the average ticket is highest. Track the raw count of missed after-hours calls week over week. Each one has a name and a dollar value attached. We break down that math in the true cost of a missed call in home service.
Booking / Conversion Rate on Inbound Calls
What it is: Of the genuine service calls your dispatcher answers, what percentage turn into a booked job on the schedule. This filters out wrong numbers, existing-customer questions, and vendor calls so you're measuring real demand conversion.
Why it matters: Answering the phone is necessary but not sufficient. A dispatcher who answers every call but only books half of them is quietly bleeding revenue you already paid marketing dollars to generate. In plumbing, booking rate also reveals call-handling skill: does the dispatcher create urgency, offer the next available slot, and close, or do they take a message and promise a callback that loses the customer?
How to read it: As a general guideline, strong plumbing offices book a large majority of legitimate service calls. Don't anchor on a specific published figure — establish your own baseline over a month, then watch the trend. If booking rate dips, look at what changed: a new dispatcher, longer answer times, more calls arriving during overlap when everyone's busy. A low booking rate on healthy call volume is one of the most fixable revenue leaks in the business.
Average Speed-to-Answer
What it is: How long a caller waits before a live person picks up — measured in rings or seconds.
Why it matters: Speed-to-answer and booking rate are tightly linked. An anxious homeowner with water spreading across the floor has a very short patience window. Every extra ring raises the odds they hang up and dial the next plumber. Fast, calm answering also sets the tone — it signals the caller reached a competent operation that can help right now.
How to read it: Watch your average, but pay even closer attention to the worst cases — the calls that rang eight or ten times before pickup or rolled to voicemail. Those long-wait calls are where abandonment and lost emergency jobs live. If speed-to-answer spikes at predictable times (lunch, shift change, storm-driven call surges), that's a staffing or overflow-routing problem, not a people problem.
Dispatch Efficiency: Drive Time and Jobs Per Tech Per Day
What it is: How well the dispatcher sequences the day — minimizing windshield time between jobs and maximizing the number of jobs each plumber completes. The two headline numbers are average drive time per job and jobs per tech per day.
Why it matters: A plumber sitting in a truck is earning you nothing. Smart dispatching clusters jobs geographically and matches the right tech to the right job, so more billable hours land on invoices instead of on the road. This is where the dispatcher's decisions turn directly into revenue per plumber: the same tech, same eight-hour day, can produce meaningfully different revenue depending purely on how their stops were routed.
How to read it: Track jobs per tech per day against your own history and by job type — a day of quick drain clears looks nothing like a day with a water-heater install, so don't compare them flat. Rising average drive time or falling jobs-per-tech usually means routing is drifting: techs crisscrossing town, gaps in the schedule, or emergencies inserted without re-optimizing the rest of the day.
Emergency-Call Routing Time
What it is: How long it takes from an emergency call landing to a plumber being dispatched and on the way. Distinct from speed-to-answer — this measures what happens after the phone is picked up.
Why it matters: Answering fast means little if the customer then waits an hour to learn when someone will actually arrive. For true emergencies, routing speed is the whole product. It's also a service-vs-installation judgment call: the dispatcher has to recognize a real emergency, decide who to pull, and weigh interrupting a scheduled install against the value and urgency of the emergency. Good routing captures the emergency without blowing up the rest of the day's revenue.
How to read it: Measure the gap between call time and dispatch time for jobs flagged as emergencies. If it's creeping up, the dispatcher may be hesitating on the service-vs-install trade-off, or lack the visibility to see which tech is nearest and freest. This is a routing-decision problem, and it's directly fixable once the dispatcher can see tech locations and schedules in one place.
First-Call Resolution
What it is: The share of jobs resolved in a single visit, without a return trip for parts, a second tech, or a reschedule.
Why it matters: The dispatcher influences this before the truck ever rolls. Asking the right questions on the call — what's leaking, the age of the water heater, the fixture brand, the symptoms — lets them send a tech who's equipped for the actual job. Poor intake sends a plumber who then has to leave for parts or hand off to someone else, which torches both efficiency and the customer's trust.
How to read it: A falling first-call resolution rate often traces back to weak call intake, not weak technicians. Listen to a sample of calls: is the dispatcher gathering enough detail to route and equip correctly? Every return trip is drive time and labor you can't bill, and a job that should have been one stop becoming two.
How Dispatcher Decisions Drive Revenue and Average Ticket
Step back and the pattern is clear: nearly every metric above rolls up into two numbers owners actually care about — revenue per plumber and average ticket.
Revenue per plumber is a function of how many good jobs each tech runs and how little time they waste. That's dispatch efficiency and routing. Average ticket is shaped by which jobs the dispatcher prioritizes and how they classify demand — routing a high-value install or emergency to the right tech at the right time versus letting it slip. A dispatcher who consistently captures emergencies, minimizes drive time, and books the right jobs to the right people is, in plain terms, printing money for the business. One who misses after-hours calls and routes poorly is doing the opposite, invisibly.
That word — invisibly — is the real problem.
Why Most Owners Can't Actually See Any of This
Here's the frustrating part. Every metric above is measurable in theory. In practice, almost no plumbing owner can see them, because the data lives in three systems that don't talk to each other:
- The phone system knows who called, when, how long they waited, and whether anyone answered — but knows nothing about whether the call became a job.
- The field software (your CRM or scheduling tool) knows what got booked, who was dispatched, and what was billed — but knows nothing about the calls that never converted.
- Spreadsheets are where owners try to stitch it together by hand, always a week behind and never quite complete.
Because these three never connect, the most important question — how many calls did we get, and how many became jobs? — has no single source of truth. You can see calls in one place and jobs in another, but never the conversion between them. The missed after-hours emergency that went to a competitor leaves no trace in your field software at all, because it never became a job. It's a leak you literally cannot see with your current tools.
This is exactly the gap a unified operations dashboard closes. When your phone system and field software feed one view, dispatcher performance stops being a mystery: calls answered, booking rate, speed-to-answer, drive time, and emergency routing all sit on one screen, updating in real time. We built a plumbing operations dashboard specifically to make dispatcher performance and lost-call revenue visible without the weekly spreadsheet ritual.
Where to Start
You don't need to boil the ocean. Start with the two metrics that leak the most money in plumbing:
- Missed after-hours calls. Pull your phone logs, filter for nights and weekends, and count the calls that went unanswered with no callback. Attach an average-ticket value to each one. That number tends to get owners' attention fast.
- Booking rate on inbound service calls. Compare answered service calls against booked jobs for the same period. Set your baseline, then watch it.
You can do both by hand this week with a spreadsheet. The moment you do, the case for connecting your phone and field data usually makes itself — because the manual version is always stale, and dispatcher performance is a live problem that deserves a live view.
Related reading: