Almost certainly not. And the businesses pushing hardest for it tend to damage the exact thing they were trying to protect.
Here is the honest version. A well built agent will take a large share of your inbound contact, and in the deployments we run that share sits somewhere around half. What it takes is the repetitive end: order status, password resets, the same billing question over and over, first line troubleshooting, anything arriving at 11pm.
What it does not take is the conversation where somebody is angry, or bereaved, or negotiating, or describing a fault nobody has seen before.
The reallocation, not the reduction
The teams getting real value from this are not the ones counting roles removed. They are the ones who noticed their best people were spending the morning on password resets.
Move that volume and the same headcount is suddenly available for retention calls, complex faults and complaints, which is work that was previously getting whatever attention was left over at 4pm on a Friday.
That is a better use of a person, and it shows up in numbers that matter more than support cost.
Why the cutting approach backfires
Retention depends on the conversations AI is worst at. If you thin the team to the point where nobody has capacity for a genuine complaint, you have automated the cheap contact and degraded the expensive one.
There is a trust cost too, and it is moving in the wrong direction. The share of people who say AI-led service costs a business their trust went from 47% to 57% in eight months. That is not a reason to avoid automation. It is a reason to be deliberate about which contact you automate and how obviously the human route stays open.
What actually changes for the team
Three things, in our experience.
The work gets harder. Everything easy is gone, so what reaches a person needs judgment. That is a real change and worth acknowledging rather than selling as pure upside.
The volume gets less brutal. Nobody is clearing a queue of two hundred identical install questions.
And the job starts needing a different skill, because the person picking up a handover is stepping into a conversation already in progress with context attached, not starting from scratch.
The honest caveat
If your customer operation is overstaffed for reasons unrelated to AI, this will make that visible. That is not the AI making a decision, but it would be dishonest to pretend the information does not surface.
What I would push back on is treating that as the goal. We do not sell headcount reduction and we do not measure a deployment by roles eliminated, because the businesses that use AI to gut a support team usually find out within two quarters that they cut the wrong thing.
