Why customers say they couldn't reach you when you answer every call

By Stacey Tallitsch | August 3, 2026

You ran into him at the parts counter, friendly enough, and he mentioned it in passing: he called you back in the spring, never heard anything, so he went with the other outfit. You felt the heat go up the back of your neck, because you answer your phone. You answer it in the truck, at the counter, at the dinner table. You have never once let a call ring out on purpose. And here is a man who paid somebody else, certain he could not reach you. He is not lying. Neither are you. Both of those things are true at the same time, and the space between them is where a real amount of your money goes every year.

That space is the whole problem, so let me name it plainly. "We answer every call" is a claim about the calls you saw. "I couldn't reach you" is a claim about a call you didn't. Those are two different phones, and only one of them is in your memory. The phone you remember answered everything. The phone you are being judged on is the other one, and by its nature you have never seen what is on it.

So this is not a post about answering the phone faster. You already believe you answer the phone. This is about finding the calls you are certain you never missed. There are four places they hide.

The call behind the call you're on

Start with the simplest. One line, one person, and often that person is you. While you are talking to the customer in front of you, a second homeowner dials. He does not get a ring you will remember later. He gets a busy signal, or he rolls straight to voicemail, or the call just quietly dies. You never saw it. You could not have. You were on the phone.

Now notice when this happens. Not on a slow Tuesday. It happens on the first hot day of summer, the first hard freeze, the morning after a windstorm, when every call is worth the most and all of them arrive inside the same twenty minutes. The busier you are, the more of these you stack up, and the more sure you are that you caught everything, because you were on the phone the entire time. Volume hides the overflow. I have written about the same leak from the other direction, when a rep wants to sell you more advertising to pour into it, in why more ad spend won't fix a phone you don't answer fast. Same crack, seen from upstream.

"During the day" is not when they call

Second. You answer every call between 8 and 5. Good. The trouble is that a large share of home-services calls do not happen between 8 and 5. The homeowner is at work when you are at work. He finds the water under the sink at 7pm. He notices the air conditioning is dead the evening he gets home in July. He deals with the roof on a Saturday morning because that is the first time he is home to stand in the yard and look at it. Industry call data puts the after-hours share of service calls somewhere between a third and a half, and those late calls are the urgent ones, because nobody calls a plumber at 9pm to price a job for next spring.

So you can answer every single call you receive during business hours and still miss the highest-intent calls of your week, because they land after you have forwarded the line to voicemail and gone home to dinner. What to actually do with that 7pm emergency is its own subject, and I laid it out in how to handle the after-hours emergency call. The narrow point here is different. If "we answer every call" quietly means "every call during business hours," you have defined the misses out of existence without fixing one of them.

The phone that rang where nobody could pick it up

Third. Plenty of owners forward the business line to the cell they carry into the field. That feels like coverage. It almost is. But the phone rings on a roof, in a crawlspace, over a running compressor, both gloves on and both hands full. It rings inside a customer's kitchen while you are mid-sentence explaining a repair and cannot step away. You see it 40 minutes later as a missed call and you mean to get back to it. To you, that was a call you were available for. To the homeowner, the phone rang eight times and no one answered. That is a missed call on the only scorecard that pays you, which is his, not yours.

The voicemail nobody leaves and the callback that looks like a scam

The fourth cause is the one almost no owner sees, because most of it happens on the customer's phone where you are not standing. Two things stack up, and together they explain most of the "I called and never heard back" complaints that leave you baffled.

First, when a homeowner reaches your voicemail, the odds are heavy that he hangs up without leaving anything. The research firm BIA/Kelsey has put the share of callers who reach a business voicemail and refuse to leave a message at roughly two-thirds. No message, no entry in your log with a name, no number written down. As far as your voicemail box is concerned, that call never happened. He simply thumbed back to the search results and dialed the next name on the list, and you never knew he existed.

Second, and this one is new enough that most owners have not caught up to it, your callback may be getting labeled a scam before it ever rings through. You return a call from your cell or from a tracking number, and the homeowner's screen shows "Spam Likely" in gray letters over your name. Here is why. The federal caller-ID authentication framework, the one built on the SHAKEN/STIR standards, verifies only that your number is not being spoofed. It proves the call is really coming from you. It does not decide whether your call is wanted (FCC, Combating Spoofed Robocalls with Caller ID Authentication). That second judgment, the label, is made separately by the carriers' own analytics, and an ordinary mobile or tracking number that suddenly starts placing a lot of outbound business calls fits the exact pattern those systems flag. So you call a real customer back, in good faith, and his phone tells him you are a robocall. He declines it without a thought. You both walk away certain you could not reach each other, and you are both right.

What the complaint is actually telling you

Here is the turn, and it is the whole point of writing this down. When a customer tells you he could not reach you, your instinct is to defend the thing you know is true, that you answer your phone. Stop defending it. It is true and it is beside the point. The calls you answer are not the ones costing you. The ones costing you are, by definition, the calls your phone never showed you: the overflow behind a call you were on, the 7pm call you forwarded away, the ring you could not get to on a roof, the voicemail nobody left, the callback that landed as spam. You cannot manage what your system never recorded. Right now you are grading yourself on a scoreboard that counts only the points you scored and none of the ones you gave up, and then you are surprised the final score does not match.

This is the same error underneath a lot of "my phone is just quieter this year" worry, which I worked through in why your phone is quieter this year. The owner reads the calls he can see and draws a firm conclusion about the calls he cannot. So the first job is not to hire an answering service or buy a new phone system. The first job is cheaper and comes first: make the misses visible. Until you can see them, every fix is a guess.

Do this today

Give it an hour. Pull the call log from your carrier or your tracking line for the last 30 days, and count three numbers. Calls that came in while another call was already active. Calls that arrived outside your business hours. Calls with a zero-second or unanswered duration that you never returned the same day. You do not need to buy software; the log is already sitting on your account. Those three numbers are causes one, two, and three, measured inside your own business, in about 20 minutes.

Then do the fourth by hand, because it is the one the log will not show you. From a phone that is not saved in your contacts, call your own business number at 7pm and let it run. Does it ring through, roll to a mailbox, or die on the third ring? Leave yourself a message, then make the callback and watch your own screen. Does your number show up clean, or does it come through gray and flagged? That is the entire diagnosis, done in an evening, for nothing. Once you can see the misses, you get to choose which one is worth fixing first. Until you can, you are losing an argument to a customer who was right the whole time.

— Stacey Tallitsch, Stronghold CMO

---

About the Author

Stacey Tallitsch builds marketing and answering systems for home-services and trades businesses at Stronghold CMO, part of Talisman Capital, Inc. He is a 30-year technology veteran and the author of 21 books, with more than 30,000 students across his course catalog.

• LinkedIn: linkedin.com/in/stacey-tallitsch
• Books on Amazon: Stacey Tallitsch on Amazon
• Courses on Udemy: Stacey Tallitsch on Udemy

Quick reference

A customer swears he called and I never called back, but I answer every call. How is that possible? Because you only see the calls that reached you. A second caller while you were on the line, an after-hours call, a ring you missed on a job, or a voicemail nobody left never shows up on your phone. You are counting answers; he is counting the one that failed.

Why would my own callback show up as "Spam Likely" on a customer's phone? Caller-ID authentication proves your number is not spoofed, but a separate carrier system decides the label, and a mobile or tracking number placing lots of outbound calls gets flagged. Your real callback can reach the customer marked as a scam, and he declines it.

How do I find calls I don't remember missing? Pull your call log for the last 30 days and count calls that came in during another call, calls outside business hours, and unanswered calls you never returned the same day. Then call your own number at 7pm from an unsaved phone and see what a customer sees.

Do I need to buy a phone system to fix this? Not to diagnose it. The audit above costs an hour and nothing else. Only after you know which of the four causes you actually have does it make sense to spend on a fix, and often the fix is a callback habit, not hardware.