- Get link
- X
- Other Apps
- Get link
- X
- Other Apps
By Dan Miller · Last updated November 2, 2026 · Prices checked November 2, 2026
Most home service shops do not have a phone problem. They have a phone blind spot. Calls come in, jobs get booked, the week moves on, and nobody checks what happened to the calls that did not turn into work. Then, one slow month, someone says the phones are dead — when the phones were fine and the follow-up was not.
This post is the fix: a missed-call audit you can run in one afternoon, with the logs you already have. No new software, no consultant, no guessing. By the end you will know which kind of missed call is costing you jobs, and which fix to do first.
The audit in 60 seconds
Pull two weeks of call records and your booking list. Sort every call that did not book into one of four buckets. Put a dollar figure on each bucket using your own average job value. Fix the biggest bucket first, and leave the rest alone until it shrinks. That is the whole audit — the rest of this post is how to do each step without fooling yourself.
Step 1: Pull three lists, and nothing else
You need three things, and you probably already have them. First, your phone log for the last two full weeks — from your phone system, carrier, or answering service. Second, your booking list for the same two weeks — from your CRM, calendar, or paper diary. Third, your message list: voicemails, missed-call texts, and notes from whoever answers the phone.
Two weeks is deliberate. One week is too noisy — a holiday or a storm skews everything. A month is too stale to check properly. If your shop takes fewer than 50 calls in two weeks, stretch it to four weeks so the buckets are not decided by three calls either way.
Match the lists by phone number and time, not by memory. A call counts as booked only if a job actually went on the schedule — a promise to call back is not a booking, and a quote sent is not a booking. Be strict here: every soft count becomes a wrong fix later.
Step 2: Sort every unbooked call into four buckets
Almost every unbooked call falls into one of four buckets. Sorting matters more than counting, because each bucket has a different fix — buying the wrong fix is how shops spend money and keep losing the same jobs.
| Bucket | What happened | What it usually means |
|---|---|---|
| 1. Never answered | No one picked up, no message left, no callback made | Coverage gap: busy lines, lunch, after hours, everyone on jobs |
| 2. Answered, never booked | Someone talked to the caller, but no job was scheduled | Booking problem: price given and lost, no slot offered, caller put off |
| 3. Message, late or no callback | A message was left, but the callback came too late or never came | Follow-up problem: messages sitting in a inbox nobody owns |
| 4. Not a job at all | Wrong number, supplier, spam, job seeker, existing customer with a question | Noise — do not count this as lost work, whatever your phone report says |
Bucket 4 is the one most shops skip, and it ruins the math. Count every missed call as a lost job and your leak looks enormous and every tool looks worth buying. Pull the noise out first: the audit is about real callers who wanted work and did not get it.
Bucket 2 surprises most owners. It is often the biggest bucket, and no answering service can fix it — because the phone was answered. The caller talked to a human, heard something that did not close the job, and went elsewhere. That is a greeting, pricing, or scheduling problem, not a coverage problem. Our guide to writing an after-hours greeting that actually books jobs covers the wording side, and the first-five-minutes breakdown shows how fast these callers move on.
Step 3: Price the leak with your own numbers
Counting buckets tells you where the leak is. Pricing them tells you whether it is worth fixing this week or next quarter. Use your own average job value — not an industry average or a vendor's sales-page number. Take the last 20 completed jobs, add up what customers paid, divide by 20.
Here is a worked example, using made-up numbers for an illustrative three-person shop so you can see the arithmetic. It is not a real shop's log — plug in your own figures and the method still works.
| Bucket (two weeks, 214 calls) | Calls | If 1 in 4 books, at $285 a job |
|---|---|---|
| Booked | 148 | — |
| 1. Never answered | 22 | About 6 jobs, about $1,710 |
| 2. Answered, never booked | 26 | About 7 jobs, about $1,995 |
| 3. Message, late or no callback | 18 | About 5 jobs, about $1,425 |
| 4. Not a job at all | 18 | $0 — noise, not lost work |
Two things jump out. First, the total that matters is not 66 unbooked calls — only a share of the real lost callers would ever have booked. Second, bucket 2 is the biggest single prize here, yet most shops never measure it, because their phone report only shows missed calls. If your audit looks like this one, buying more coverage before fixing booking is spending money on the smaller problem.
Be honest about the "1 in 4" assumption. Some callers were shopping around, some wanted a price you cannot match, some called three shops at once. If 1 in 4 feels generous, use 1 in 5. The point is ranking the buckets, not a precise forecast. Our missed-call cost guide walks through the same calculation with your own inputs.
Step 4: Fix the biggest bucket first — and only that one
Pick the bucket with the largest dollar figure from Step 3 and fix only that one this month. One fix, done properly, beats three half-started fixes. Here is the usual fix for each bucket.
If bucket 1 wins — never answered: cover the specific hours where the calls cluster, not the whole day — lunch, one weekday, or after 5 p.m. A text-back on missed calls often closes this gap faster than a new hire, because the caller gets an answer while still deciding.
If bucket 2 wins — answered, never booked: read the call notes. The usual culprits are a price quoted with no next step, no slot offered, or a caller told to "call back later" — which they will not do. Fix the script first: offer two specific times, confirm the booking before hanging up, and record the reason when a caller declines. You cannot fix a reason nobody recorded.
If bucket 3 wins — late or no callback: give messages one owner and one deadline. A shared inbox with no owner is where callbacks go to die. The rule that works for most small shops is simple: every message gets a callback attempt within one business hour, and the owner checks the list twice a day. That routine echoes the morning check in our fix-it playbook for wrong bookings.
Then re-run the audit in four weeks, on the same method, and compare bucket by bucket. If the biggest bucket shrank, move to the next one. If it did not, your fix was wrong or was not actually done — both are cheaper to learn from a second audit than from a year-long contract.
What not to do with the results
Do not turn the audit into a blame exercise. If bucket 2 is full of calls your dispatcher handled, the problem is usually the script, the schedule, or the price policy — not one person's effort. Shops that scold staff over it get cleaner-looking notes and worse data next time, because people stop writing down the awkward calls.
Do not buy a tool to fix a bucket you have not priced. An answering service is a good fix for bucket 1 and a poor fix for bucket 2. A review tool will not fix bucket 3, and a CRM will not fix any bucket if nobody owns the follow-up list. The audit earns its keep by stopping the purchase that feels productive and is not.
And do not audit once and file it away. Call patterns change with the season, crew size, and whoever answers the phone. One afternoon a quarter is enough to catch a bucket growing before it becomes a slow month.
The shops that lose the fewest jobs are not the ones with the fanciest phone setup. They are the ones that know, from their own logs, where jobs actually go missing — and fix that one place first.
Want the dollar figure for your own shop?
Calculate my true cost →FAQs
How long does the audit really take?
About two to three hours for a small shop: an hour to pull and match the lists, an hour to sort the calls, and the rest to price the buckets and pick the fix. If it takes a full day, your lists are scattered — fixing where the lists live is the first job.
What if my phone system does not show missed calls clearly?
Use what you have: carrier logs, voicemail timestamps, and your booking list, and work backwards. A call in the phone log that never becomes a booking is an unbooked call, even if your system does not label it missed.
Should I count calls from existing customers?
Yes, but in their own note, not in the job buckets. A repeat customer calling about a warranty is not a lost new job, but a slow answer still costs goodwill. If these calls are a large share of your unbooked calls, fix that service problem separately.
How often should I repeat the audit?
Quarterly is enough for most shops, plus once more after any big change — a new answering service, a new dispatcher, or a new phone system. Re-auditing after a change shows whether it worked, instead of assuming it did.
Does this audit replace an answering service or AI receptionist?
No — it tells you whether you need one, and for which hours. If bucket 1 dominates, coverage is the fix and an answering tool may be it. If bucket 2 dominates, fix booking first and let the tool wait. The audit decides; the tool follows.
Prices checked November 2, 2026. This post makes no price claims and contains no affiliate links; it recommends no specific vendor, so there is nothing here to buy through us.
FREE 60-SECOND TEST
Is your shop leaking money?
Missed calls, estimates nobody followed up, invoices nobody chased — add yours up, get your grade, and copy the messages that fix the biggest leak.
Take the Shop Leak Test →Disclosure: Some posts on TradeAI Tools contain affiliate links. This post does not. If you buy through an affiliate link elsewhere on this site, we may earn a commission at no extra cost to you.


Comments
Post a Comment