CONTAMINATION DOES NOT SPREAD EVENLY ACROSS A REPORT. IT POOLS WHERE THE NUMBERS LOOK BEST, WHICH MEANS CLICK-THROUGH RATE FALLS HARDEST ON THE PAGES YOU WOULD POINT TO AS PROOF THINGS ARE WORKING.
• Quality scores on human-reviewed calls survive for the same reason, which is exactly why we route flagged calls to a person instead of letting the model close them out.
The exposed ones are the metrics that count an event no human needs to be present for:
• Deflection rate
• Chatbot containment
Where The Junk Sits
I expected the machine and bot traffic to sit deep in the results where nobody looks. It does the opposite and FIGURE 2 is the picture of it.
Half of all machine and bot impressions, 49.9 %, landed in the top three positions. Only 12.9 % of human impressions did. The humans pile up at the bottom instead: 42.5 % of them at position 21 or worse.
Contamination does not spread evenly across a report. It pools where the numbers look best, which means click-through rate falls hardest on the pages you would point to as proof things are working.
My first instinct was to rewrite the titles on those pages. They were never broken. Nothing was reading them. So they weren’ t responsible for the junk. The impressions came from software that almost never clicks, no matter what the titles said.
The Same Failure, One Funnel Over
I recognized that pattern because I live with its twin, much closer to the floor.
We score every call with an AI model and route the flagged ones to a human reviewer. A quality score rolled up across a book of calls, meaning one average standing in for hundreds of individual scores, is a blend.
If the automated layer behaves differently on one campaign than another, the average stays green while the campaign moves, and the natural response is to coach agents whose calls were never the problem.
Same failure, different channel: a number built by averaging across a population that turned out to be two.
26 CONTACT CENTER PIPELINE
WHERE REASONING IS NEEDED
This is the point where measurement stops and reasoning begins, and I want to be clear about which side of it I am on.
In web search, I can prove the split because I have the string. In your contact center, you usually cannot because the channel hands you the event and keeps the fingerprint.
Email opens are the one case I have observed directly. An open is recorded when a tracking pixel loads, and plenty of what loads pixels is not a recipient. Corporate security gateways open links to sandbox them and add a second layer on top.
The rest is inference, labeled as such. Deflection, containment, self-service success, and speed-to-lead all count a physical event that software can now manufacture. I have not measured those on a contact center stack. What I have measured is the mechanism they share.
WHAT METRICS SURVIVE
Now the reassuring part, which turns out to be most of your reporting pack.
Anything that ends in a human confirmation step still means what it says, because a person had to be present- an agent or a customer- for the metrics to move.
• Average handle time( AHT) holds up because a human handled the calls.
• Service levels and average speed of answer on answered calls continue to be valid because somebody stayed on the line long enough to be answered.
• CSAT, NPS, and customer effort score survive because customers chose to respond.
• Self-service success
• Speed-to-lead
• Cost per contact because the denominator is contacts.
• FCR, when the first contact was a script.
Occupancy sits awkwardly between the two. Your agents were genuinely busy, and the number is honest about that. But busy is not the same as productive if some of the work arrived from sessions no customer needed.
The voice floor is largely trustworthy. Digital and self-service reporting is where to look first. If a metric can move without a person doing anything, treat it as an estimate rather than a count.
FIVE QUESTIONS FOR YOUR ANALYTICS TEAM
None of this requires you to touch a data export. Where a channel produces something you can read, a query string or a chat transcript, ask for 50 examples and read them yourself. You will know within a minute.
Then ask your analytics team these five questions:
1. What physical event increments this number? An open is a pixel load. A deflection is a ticket that never appeared.