When Tenure Lowers the QA Bar

The people skipping trained steps on calls were not the newest hires. They had been on the phones the longest.

I noticed it grading calls one week and figured it was one agent having an off day. Then I saw it again on someone else's call. Then a third. All longer tenured, all skipping the same small things: mentioning the survey, thanking the caller, confirming the issue was resolved before closing.

What the Pattern Looked Like

Grading 50-plus calls a month on Calabrio, patterns like that show up eventually. This was not sloppiness from someone new to the job. It looked more like the steps had just stopped mattering to people who had been doing this long enough to feel like they did not need them anymore.

Each individual call was still competent. The callers got their issues addressed. If you listened to any single recording in isolation, you would not flag it. The pattern only became visible across multiple agents over multiple days, and only because the same specific steps were being dropped.

The steps being skipped were not technical. They were the process and soft-skill checkpoints that QA scoring is specifically designed to measure: verification, empathy markers, proper closure. The kind of things that feel optional once you have done a thousand calls and the muscle memory takes over.

Why Tenure Creates Blind Spots

Nobody was double-checking these agents closely because they had already earned the trust to be left alone. They hit their numbers. Their technical resolution was solid. Managers had no reason to look harder.

That trust is earned and usually deserved. But it also means a shortcut can go unnoticed for a while. New hires get listened to constantly. Their calls are reviewed, coached, and corrected in real time. Experienced agents get spot-checked, and the spots that get checked tend to confirm what everyone already believes: they know what they are doing.

Addressing It as a Team Problem

I flagged it through QA coaching as a team-level issue instead of coaching each person one at a time. There were a few reasons for that approach:

• Singling out individuals for a shared pattern creates defensiveness. If three people are doing the same thing independently, the issue is cultural, not personal. Treating it as one person's mistake misses the systemic cause.
• The standard does not get to loosen just because someone has put in the years. The steps exist for a reason. If they stopped being enforced for tenured agents, the implicit message to newer agents is that those steps are temporary requirements you can drop once you have been around long enough.
• Team-level reinforcement reaches agents who are starting to drift but have not been caught yet. The three I identified were the ones whose calls happened to land in my review queue that week. There may have been others.

What Changed Afterward

The reinforcement was straightforward: here is the standard, here is where we are drifting, here is why these steps still matter regardless of experience level. No punitive action, no formal write-ups. Just a recalibration of expectations.

The harder part was making the point stick without insulting people who genuinely are good at their jobs. Telling a ten-year veteran to remember to thank the caller can land wrong if it sounds like you are questioning their competence. Framing it as "the bar applies to everyone, including the people who have been clearing it the longest" helped.

QA scoring is not just a tool for catching bad calls. It is the mechanism that prevents good agents from quietly redefining what "good enough" means on their own terms.