Listen to ten real calls every week

A phone agent that answers for a service business can pass every test before launch and still drift once real callers show up. People mumble. They call from the highway. They ask two questions at once, or start with the wrong one. A customer says "the thing under the sink" and means the garbage disposal. None of that shows up in a test script written by the people who built the agent.

The dashboard will not tell you much either. Call counts, average length, and how many calls ended in a booking are useful numbers, but they describe the outcome, not the conversation. A call can end in a booking and still have gone badly. The caller repeated their address three times, the agent offered a time the tech could not make, or the caller got annoyed and booked anyway because they had no other option.

The cheapest fix we know is also the most boring one. Every week, someone who knows the business listens to ten real calls from start to finish and writes down what they hear. This post covers how we set that up for the businesses we build voice reception for, what to listen for, and what to do with the notes.

Why ten, and why every week

Ten calls is small enough that one person can get through them in under an hour, even while taking notes. It is large enough that patterns start to show by the second or third week. If the same confusion turns up in three of ten calls, that is not a fluke.

The weekly part matters more than the number. Callers change with the season. A heating company gets different questions in October than in June. Promotions, price changes, new service areas, and staff changes all shift what people ask about. A review done once at launch tells you how the agent handled launch week. A weekly habit tells you how it is handling things now.

It also keeps the review from turning into a project. Nobody has to block off a day. It fits into a Monday morning or a Friday afternoon, and it gets skipped less often because it is short.

How to pick the calls

If you only listen to calls that came up in a complaint, you will only hear the worst ones. If you let the system pick for you, you may only hear the easy ones. We split the ten roughly like this:

• Four picked at random. These show you a normal day. Most of what you learn comes from these.
• Two of the longest calls. Long calls usually mean something went sideways: a misheard detail, a loop, or a question the agent could not answer.
• Two of the shortest calls. Very short calls are often hang ups. Some are wrong numbers. Some are callers who gave up in the first few seconds, and you want to know why.
• Two that ended in a transfer or a message for staff. These show where the agent hands off, and whether the handoff carried the details your team needed.

If your system can tag calls by outcome, use that to pull these groups. If it cannot, a random sample plus a quick sort by call length gets you most of the way.

What to listen for

Listen to the audio, not only the transcript. Transcripts are useful for skimming, but they hide tone, long pauses, and the moment a caller sighs and repeats themselves. For each call, we write a line or two answering a few questions.

Did the caller get what they called for? Booked, answered, transferred, or told clearly what happens next. If not, where did it stall?

Did they have to repeat anything? Names, addresses, and phone numbers are the usual suspects. One repeat is normal. Three on the same detail is a problem worth fixing.

Did the agent say anything wrong? Hours, prices, service areas, and what the business does or does not offer. A wrong answer delivered with confidence is worse than "let me have someone call you back."

Did the agent promise something the team cannot deliver? A same day visit when the schedule is full, a callback time nobody is watching for, or a discount that does not exist.

What did the record look like afterward? Open the booking, ticket, or message the call created. Check that the name, address, and reason for the call match what you heard. A call that sounded fine can still leave a record your tech cannot use.

Would you be comfortable if this was a new customer's first impression? This one is a gut check, and it is usually the one owners answer fastest.

Keep a short log

The notes go into one running document or sheet, with one row per call: the date, the type of call, what went well, what went wrong, and a guess at why. Keep it plain. "Caller asked about weekend rates, agent said it did not know, no message taken" is enough.

After a few weeks, the log does most of the work. You might see that the agent struggles with street names in one part of town, that nobody updated the prices after the last change, or that callers keep asking about a service you stopped offering. Those patterns are hard to spot one call at a time and obvious across thirty.

Turn notes into small fixes

Most of what a weekly review turns up is small. A missing answer gets added to the agent's instructions. A wrong price gets corrected at the source, so the agent and the website say the same thing. A confusing question gets reworded. A detail the techs keep calling back for gets added to the call summary.

We hold one rule about fixes: change one or two things at a time, then listen again the next week. If you rewrite the whole script after one bad call, you will not know which change helped and which one broke something else. Small changes with a weekly check give you a clear before and after.

Some findings are not about the agent at all. If callers keep asking whether you serve a certain town, the website may be unclear. If many calls are people checking on a tech's arrival, the reminder texts may need an arrival window. The review shows you what your customers are confused about. The phone agent just happens to be where they ask.

Who should do the listening

The best reviewer is someone who knows how the business actually runs: the owner, an office manager, or a lead dispatcher. They catch wrong answers a developer would miss, because they know what the right answer is. A developer is useful for making the fixes, but the listening belongs to the business.

Rotate it if you can. Two people taking turns hear different things, and neither one gets tired of it.

Before you start, make sure call recording and review are set up correctly for where you operate. Rules on recording calls and telling callers about it differ by state and country, so confirm the greeting and settings with whoever handles that for your business.

Start this week

Put a time on the calendar, pull ten calls, and listen with a notepad open. Do not try to fix anything in the first session. Just write down what you hear.

By the third week you will have a short list of things worth changing, and a clear sense of whether the agent is getting better or slowly getting worse. That is a lot of signal for an hour a week, and it is the part of running a phone agent that no dashboard does for you.