Customer Support Tech
Customer support after deflection stopped being the metric
Containment rates became contractual, and then immediately stopped being interesting. What replaced them says more about where support tooling is headed than any product roadmap.
- Author 01
WebTechOS Editorial
- Published 02
2026-07-04
- Read 03
6 min
Every support vendor now quotes a deflection number, and the numbers are converging. When every tool claims between fifty and seventy percent containment on well-documented queries, containment stops being a differentiator and becomes table stakes.
What separates good deployments from bad ones now is what happens in the remaining thirty percent — the conversations the agent could not close. That is where the cost sits, and increasingly where the churn sits too.
Escalation is the new battleground
A customer who spends four minutes with a bot, gets nowhere, and then has to re-explain the entire problem to a human has had a worse experience than if the bot had never existed. The deflection metric rewards the attempt and is silent on the cost of a failed one.
The vendors worth shortlisting are the ones instrumenting this properly: time-to-human on failed containment, context carried into the handoff, and reopen rates on conversations the agent marked resolved. Ask for those three numbers in any evaluation. Most vendors will not have them at hand, which is itself informative.
Ask for reopen rate on AI-resolved conversations. The pause before the answer tells you what you need to know.
Documentation became infrastructure
The uncomfortable finding across every deployment we have looked at is that agent quality tracks knowledge-base quality almost exactly, and knowledge-base quality is a staffing decision nobody wants to make. Teams that cut support headcount on the strength of an AI deployment, and cut the technical writers along with it, saw containment degrade within two quarters as documentation went stale.
The correct read is that documentation moved from a support artefact to production infrastructure. It should be reviewed, versioned, tested and owned accordingly — and budgeted for as infrastructure rather than as content.
WebTechOS accepts no payment for coverage, placement or scores. Where a piece references pricing, it reflects published list rates at the date shown.
Keep reading
All insights →The agent pricing reckoning
Per-seat licensing assumed software helps a person work. Agents do the work. Four billing models are now fighting to replace the seat, and three of them will lose.
AI Agent HubWhy most agent projects fail in month three
The demo works. The pilot works. Then something changes upstream, nobody notices for two weeks, and trust never comes back. A field guide to the failure that kills more agent projects than capability ever has.
SaaS InsiderThe consolidation nobody predicted
Unbundling was supposed to be the permanent condition of SaaS. Instead, buyers spent two years cutting vendor counts, and the tools that bundled well are winning categories they were not supposed to.