Do missed and abandoned calls belong in call QA?
Yes, but as a staffing and routing measure rather than a rep measure. Nobody scores well on a call they never received. Track ring time before answer, abandon rate by hour and day of week, after-hours volume and what happens to voicemails, and keep those separate from rubric scoring. In many shops the largest revenue leak is calls nobody answered.
Two different performance questions
Queue performance asks whether a human answered in time. Handling performance asks what happened once someone did. Mixing them into one quality number makes both unreadable and lets a staffing problem masquerade as a coaching problem.
The tell is a booking rate that sags at predictable hours. If the dip lines up with lunch, shift change, or the Monday morning spike, you are looking at coverage, and no amount of rubric work will fix it.
Separating them also changes who is accountable. Handling belongs to the rep and her manager. Ring time, coverage and routing belong to whoever builds the schedule, and that person often never sees the call reporting at all.
What to measure on the queue side
- Ring time to answer, distributed rather than averaged. The average hides the tail, and the tail is where callers give up.
- Abandon rate by hour and weekday, which points straight at scheduling decisions.
- After-hours and weekend volume, and what actually happens to it.
- Voicemail outcomes — how many were returned, how fast, and how many of those booked.
- Calls routed to mobile phones, which often escape recording and reporting entirely.
The after-hours question is usually the biggest one
Emergency demand does not respect business hours, and a homeowner with no heat calls the next company on the list within a minute or two. Voicemail volume overnight is a direct read on how much demand is leaking, and the return-call speed on those messages is a coachable behavior with an obvious dollar consequence.
Whether the answer is an answering service, extended hours, or an automated first response is an operations decision, but you cannot make it without the numbers. This is exactly the kind of thing a daily brief should surface without anyone running a report.
Speed of response is the coachable part here. A returned voicemail within minutes behaves very differently from one returned the following afternoon, and that gap is entirely a process decision.
Fix the leak before polishing the handling
Improving a rubric score on answered calls is worthwhile. Answering calls that currently go unanswered is usually worth more and takes less time to implement.
Sequencing matters here. Get the routing, hours and coverage right, then work on handling quality, then work on the finer rubric items. Reporting that puts both in one view — call analysis joined to queue data — keeps the team from optimizing the smaller number first.
Topics: missed calls · abandon rate · staffing · call QA
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.