A customer calls your business, and she is done being polite. She says she has tried to reach you twenty times and not once did a real person pick up. Your first instinct is that she must be exaggerating, because you know your team. They are good. They are busy. They stay on top of things. So either she is wrong about what happened, or something is going on that you cannot see from where you sit.
I got pulled into a situation exactly like this. A support team was taking heat from a customer who said she had called over and over and only ever reached a voicemail prompt, in the middle of business hours, and she wanted to know what the organization was even doing. The team felt unfairly accused. From where they sat, they were slammed and working hard all day. Both of those things were true at the same time, which is exactly what made it worth a closer look.
The Complaint Checked Out
The first thing I did was pull the phone logs, and her story held up almost exactly. She had not called twenty times. She had called seventeen, and eight of those were on the single day she finally lost patience and complained. Not one of the seventeen had connected her to a live person. Every call had landed in voicemail during business hours. When a frustrated customer's account matches the logs that closely, you are not looking at an outlier who is hard to please. You are looking at a signal.
The logs had more to say than that. On the day of her complaint, the team's answer rate was zero percent. Across the whole month, during business hours, it averaged fifteen percent. And roughly one in five calls was a redial from someone who had been dumped to voicemail less than thirty minutes earlier. The phone was ringing constantly, and almost nobody was getting through to a person.
The Team Was Busy on the Wrong Thing
Here is the part that surprised me. The team was not idle, and they were not lazy. They were working hard the entire time. They were just working the wrong queue. Every missed call left a voicemail, the voicemails piled up into a backlog, and the team spent their days diligently triaging and returning those messages. The backlog was visible and it felt urgent, so that is where all the effort went.
Meanwhile the live calls, the customers actually holding a phone to their ear right then, kept rolling to voicemail and quietly became tomorrow's backlog. The team was chasing the symptom while feeding the cause. And because a missed call so often turns into a redial, the unanswered phone was inflating its own volume. They were busier than they needed to be, in part because they were not answering the phone.
The Fix Was a Number, Not a Phone System
The office did not need a new phone system, and it did not need more people. It needed to see the one thing nobody was tracking. So I set up a small daily job that read the previous day's call logs and sent the support team a short, friendly email every morning with a single figure: yesterday's answer rate. No dashboard to log into, no meeting, no lecture from a consultant. Just a gentle number in their inbox each day, telling them how they had actually done.
What Happened
Within a few days, the team was answering more than ninety percent of their calls. Over the following week they settled into a steady rhythm in the mid-seventies, up from the fourteen or fifteen percent they had been living at for who knows how long. As they answered more live calls, fewer rolled to voicemail, so the backlog they had been drowning in stopped growing and began to shrink on its own.
And because far fewer callers were hanging up and calling back, the total volume of calls coming into the business fell by more than a quarter in a single week. The telling part is where the drop landed. It was almost entirely in the calls that used to go unanswered, the voicemails and the hang-ups, while the number of answered calls actually went up. A slow week would have pulled all of it down together. This pulled down only the missed calls, which are the exact ones that had been turning into redials. The team had been generating a real share of its own workload without ever knowing it. Answering the phone did not add to their day. It gave them their day back.
What This Is Really About
A hardworking team can be pointed at the wrong work, and from the inside it is almost impossible to notice. The voicemail backlog was real, and clearing it felt like doing the job well. The number told a different story, and the moment the team could see it, they fixed the problem themselves. Nobody had to be managed into it.
That is usually what a good metric does. It does not push people to work harder. It shows a team that already cares where their effort is actually landing, so they can aim it at the thing the customer feels. The woman in this story did not care how many voicemails got returned. She cared whether a person picked up. Once the team could see that number every morning, so could they.
If your people are working hard and your customers still cannot reach you, the gap is worth finding, and it is usually not where the effort is already going. If that sounds familiar, it is worth a conversation.