Yes, today ' s technology can analyze tone, detect politeness, and highlight friendly exchanges between agent and caller.
That ' s useful, but it ' s not the whole picture.
I ' ve reviewed calls that looked flawless according to AI sentiment, only to uncover coaching moments after listening to them myself.
On one call, for instance, the agent politely told a member, " If you place me on hold, I ' ll have to disconnect." The tone was calm, but the message missed the mark.
It reminded me that no algorithm( at the time of this writing) can replace human understanding: the empathy and discernment that come from real listening.
I say that not just as a call center leader, but as someone who started on the phones.
WHEN WE DESIGN QA WITH THE FRONTLINE IN MIND, IT CHANGES HOW AGENTS RE- SPOND TO EACH EVALUATION...
MY FIRST QA EXPERIENCE
I ' ll never forget my first bad QA score. It was 2008, and evaluations were still done on Excel spreadsheets.
The analyst handed me a printed copy of the spreadsheet- a number at the top, a list of misses below- and nothing else. My " errors " were vague; I missed the greeting, didn ' t educate the customer, and provided inaccurate information.
But here ' s the thing: I had greeted the caller. I was confident that I had provided the correct information. And I desperately wanted to know what I had supposedly done wrong so I could fix it.
But the form didn ' t tell me that. Instead, it only left me frustrated and full of questions.
Most of my colleagues at the time shrugged off poor QA scores, since at the time they didn ' t affect pay or bonuses, so why care? But I couldn ' t let it go. I needed clarity. So, I approached the QA analyst- carefully, trying not to sound defensive- but eager to learn. That conversation evolved into a 30-minute-long session, during which she walked me through the details of my call. It was my first month on the phones, and that meeting changed everything.
I later realized that the call had come through on the Indiana Care Select line, but I had greeted the caller with, " Thank you for calling Hoosier Healthwise." That ' s where I lost points, both for using the wrong greeting and for failing to provide the caller with the correct information.
Regarding the caller education section, I had overlooked informing the caller that the first 10 transportation rides are available to them without prior authorization.
Interestingly, about a year or two later, the QA form was updated, especially after quality scores began to directly impact employee bonuses and pay increases.
From that day forward, I knew what " good " sounded like. I had a clear picture of what success looked like, and I worked hard to ensure every call was worthy of a 100 % QA score. Not because of the score itself, but because I understood what mattered.
That early experience taught me a lesson I carry with me today. QA without context is just a number: we feel good when we receive a good score and feel frustration when we get a bad one.
But QA with feedback, coaching, and a little humanity becomes a tool for growth: for the agent, the team, and the customer.
THE AGENT ' S VIEW OF QA
If you spend time in call center communities on Reddit or Facebook- or sit down with your agents in a coaching session- a familiar theme emerges: the word " QA " rarely feels like it stands for Quality Assurance. To many, it feels more like " Quality Apprehension ".
Over the years, I ' ve heard the same frustrations surface again and again.
COACH ' S CORNER
• Nitpicking: Agents are penalized for minor checklist oversights that have little to no impact on the CX.
• Lack of context: QA scorecards often note deductions without clear explanations or examples of what went wrong.
• Punitive culture: QA feels like a tool for punishment rather than growth. A score to survive, not a conversation to improve.
On online forums, agents often describe QA as " the department that waits for you to mess up." One Reddit user summed it up perfectly: " They call it coaching, but it feels like a report card I didn ' t ask for."
When quality reviews prioritize error detection over effort recognition, agents begin to disengage. They start doing just enough to avoid getting flagged: checking boxes instead of connecting with customers. Over time, this mindset breeds frustration, detachment, and eventually burnout.
And here ' s the real irony: these are the very people QA was created to support. When the process adds pressure instead of perspective- when it creates fear instead of feedback- we ' ve missed the mark.
A truly effective QA program should leave agents thinking, " I learned something today," not " I hope I don ' t get another bad score."
WHAT QUALITY SHOULD BE
For agents, QA ' s job is to make work transparent and fair, to help improve the agent’ s performance, not to create a " gotcha!" moment. When we design QA with the frontline in mind, it changes how agents respond to each evaluation: from fear and box-checking to curiosity and growth.
APRIL 2026 13