Key takeaways
- Revenue alone hides too much in a home services business — two companies with identical monthly revenue can have completely different problems underneath it.
- Four metrics matter most: booked-call rate, average ticket, technician utilization, and callback rate — each isolates a different part of the business.
- This guide defines each metric precisely and shows how to calculate it. It does not hand you an industry benchmark number, because trade, region, and call mix vary too much for one figure to apply.
- The right move is tracking your own number consistently over time and treating your own trend as the benchmark to beat.
- Most of the raw data for all four metrics already exists in your phone system, scheduling software, and invoicing records — the work is pulling it into one place, not collecting new data.
A home services business — HVAC, plumbing, electrical, landscaping, pest control — can hit its revenue number for the month and still be quietly bleeding in a way revenue doesn't show. Maybe half the calls coming in never turn into a booked job. Maybe technicians are driving between calls more than they're working them. Maybe the average job is worth less than it was a year ago, even though there are more jobs total. Revenue is the outcome. These four numbers are what actually produce it.
Why revenue alone doesn't tell the whole story
Two companies can post the exact same monthly revenue and have completely different underlying businesses. One might be running fewer, higher-value jobs efficiently. The other might be running twice as many low-value jobs, burning through technician hours and marketing spend to get there. From the outside — and from a bank statement — they look identical. The four metrics below are how you tell them apart, and how you find out which lever actually moves your specific business forward.
This guide defines each metric clearly so you can calculate it accurately. It intentionally does not give you an industry-average number to compare against — trade, region, call source mix, and job type vary enough that a generic benchmark usually does more harm than good. Track your own number consistently, and treat your own past performance as the benchmark.
Booked-call rate
Definition: The percentage of incoming calls that result in a booked job. Calculated as booked jobs from calls ÷ total incoming calls, for a given period.
This metric isolates the front door of the business. A low booked-call rate can come from several different places — calls going unanswered, a scheduling gap that turns away a caller who wanted a same-day slot, or a pricing conversation that loses the job before it's booked. Tracking booked-call rate separately from total call volume tells you whether a marketing push that's generating more calls is actually turning into more work, or just more phone traffic that goes nowhere.
To calculate it accurately, you need two numbers most phone systems or call-tracking tools already capture: total inbound calls and the count of those calls that became a scheduled job. If those two numbers don't currently get compared to each other, that gap — not the rate itself — is usually the first thing worth fixing.
Average ticket
Definition: The average dollar value of a completed job, calculated as total service revenue ÷ number of completed jobs, for a given period.
Average ticket answers a different question than total revenue does: is each individual job getting more or less valuable over time? A business can grow total revenue purely by running more jobs while average ticket quietly declines — which usually points to underselling, scope creep on quotes, or pricing that hasn't kept pace with cost. Watching average ticket alongside job count separates a volume problem from a value problem, and each one has a different fix.
This number is also one of the easiest to segment usefully — by service type, by technician, or by lead source — once you're tracking it consistently. A dip that looks small company-wide might be concentrated in one service line or one crew, which is far more actionable to address.
Technician utilization
Definition: The percentage of a technician's scheduled working hours actually spent on billable job time, calculated as billable hours ÷ total scheduled hours, for a given period.
Utilization measures how much of the day a technician spends doing the work that generates revenue, versus driving, waiting, or sitting idle between calls. It's the metric most directly tied to how efficiently a schedule is built — a poorly routed day full of backtracking across town shows up here just as clearly as an empty afternoon with no calls booked.
| Metric | Formula | What it isolates |
|---|---|---|
| Booked-call rate | Booked jobs ÷ total incoming calls | Whether calls are converting into work |
| Average ticket | Total service revenue ÷ completed jobs | Whether each job is worth more or less over time |
| Technician utilization | Billable hours ÷ scheduled hours | How efficiently the schedule uses technician time |
| Callback rate | Callback visits ÷ total completed jobs | Whether work is being done right the first time |
A word of caution on this one, though: pushing utilization toward its theoretical maximum isn't automatically the goal. A schedule packed with zero slack has no room for an emergency call, a job running long, or unpredictable drive time, and it tends to wear down even a good technician over time. Most businesses find a sustainable target somewhere below full capacity, set based on their own call volume and job-length patterns rather than an outside number.
Callback rate
Definition: The percentage of completed jobs that require a follow-up visit to address the same issue, calculated as callback visits ÷ total completed jobs, for a given period.
Callback rate is the closest thing to a direct read on work quality that most home services businesses can measure without a customer survey. Some callbacks are unavoidable — a part fails on its own timeline, unrelated to the original job — but a callback rate that trends upward over several months, or that clusters around a specific technician or service type, is a real signal worth investigating. The underlying cause could be training, parts quality, or technicians rushing jobs under time pressure, and each has a different fix.
A callback costs twice: the direct cost of the return visit, and the quieter cost of a customer whose confidence in the job took a hit — which shows up later as a lower callback rate on referrals and repeat bookings, not on this month's numbers.
Pulling these four numbers into one view
Most of the raw data behind all four metrics already exists somewhere in the business — a phone system or call-tracking tool for booked-call rate, invoicing software for average ticket, a scheduling tool for utilization, and a dispatch or work-order system for callback rate. The work isn't collecting new data; it's pulling what already exists into one place so the four numbers can be reviewed together, on a consistent schedule, instead of living in four separate systems nobody checks side by side.
Once that's in place, the real value shows up in how the numbers interact. A rising booked-call rate paired with a falling average ticket might mean a marketing campaign is bringing in smaller jobs. A high utilization number paired with a rising callback rate might mean technicians are being scheduled too tightly to do the job right. Looking at any one metric alone tells you less than watching how they move together.
How the mix shifts by trade
The four metrics apply across home services broadly, but which one deserves the closest attention shifts depending on the trade. An HVAC company with strong seasonal swings often finds tech utilization the most volatile number to manage — a slammed July and a quiet April both need a different staffing approach, and utilization is what shows whether the schedule is actually adjusting to that swing rather than staying flat all year. A plumbing business built more on emergency and same-day calls tends to live or die by booked-call rate, since a caller with a burst pipe rarely waits for a callback. A landscaping or lawn-care business, with more predictable recurring routes, often gets the most value from average ticket, since upsells and service add-ons on an existing route are usually more available than winning entirely new customers.
None of this changes the definitions — the formulas stay the same across every trade. It just means the order you tackle them in, and which one gets the closest weekly attention, should follow where your business's specific pressure actually sits.
Getting started without an analytics project
None of the four metrics require new software to start tracking. Most phone systems already log call counts, most invoicing tools already total revenue and job counts, and most scheduling software already tracks technician hours. The first step is simply pulling those existing numbers into one spreadsheet, calculated the same way every week, so a trend actually becomes visible instead of living as a vague impression in a manager's head.
Once that habit is in place for a month or two, it becomes far easier to decide whether a dedicated dashboard is worth setting up, and which of the four numbers deserves the most attention for your specific business. Starting with a spreadsheet also means the eventual dashboard gets built around metrics you already know are useful, rather than whatever a default template happens to include.
Mistakes to avoid
- Chasing an outside benchmark instead of your own trend. A number pulled from a different trade or region tells you less than three consistent months of your own data.
- Optimizing utilization to the maximum. A fully packed schedule with no slack tends to produce more callbacks and more burned-out technicians, not more profit.
- Watching revenue and ignoring average ticket. Revenue can grow while each job quietly gets less profitable — average ticket is what catches that early.
- Treating every callback the same. A callback tied to an unrelated part failure isn't the same signal as one tied to the original job being done incompletely — separate the two when you can.
- Tracking these numbers once and stopping. A single snapshot tells you where you stand; a consistent weekly or monthly cadence is what tells you whether you're improving.
◆ Small Business AI Kickstart
Get AI ready today.
Before it's too late.
yforest AI Labs comes to your company, trains your team, and ships your first tools.
FAQ
What's a good booked-call rate for our business?
This guide won't hand you a number, because it varies too much by trade, call source, and how calls are answered — a rate built from paid-lead calls looks different from one built from repeat-customer calls. Track your own rate for a few months first, then treat that as your baseline to improve against.
How is average ticket different from just tracking total revenue?
Total revenue can grow just because you ran more jobs, even if each one is worth less. Average ticket isolates whether each individual job is getting more or less valuable — which points to a very different fix (upselling, pricing, scope) than a volume problem does.
Should tech utilization be as close to 100% as possible?
Not necessarily. Very high utilization leaves no slack for emergency calls, drive-time variance, or a job running long, and it can burn out a good technician. Most businesses find a livable target somewhere below full capacity, based on their own call volume and job lengths.
Does a high callback rate always mean bad work?
Not always, but it's the first place to look. Some callbacks are unavoidable (a part fails on its own), but a callback rate trending upward over time is a real signal worth investigating, whether the cause is training, parts quality, or job time pressure.
How often should we review these four numbers?
Weekly for booked-call rate and tech utilization, since both shift with daily call and schedule volume. Monthly is usually enough for average ticket and callback rate, since both need a slightly longer window to show a real trend instead of noise.
Sources
This guide is general information, not legal advice. Have a qualified attorney review any policy before you adopt it.