The ROI from AI in customer service comes from operational redesign around the AI, not from the AI itself. Companies that wire the AI into the existing workflow without redesigning anything see most of the projected savings stay on the slide. Companies that change the work the human team does, the contracts with vendors, and the routing of contacts capture the value.
A retailer deploys an AI agent for tier-1 support. The AI handles 60% of contacts. Twelve months later, the cost of support per contact is the same. The team did not shrink, because nobody planned for what the residual hard contacts would need. The vendor contracts did not change, because nobody renegotiated. The savings exist in a slide deck, not in the P&L.
What people in the field are saying
kdschemin's "The ROI isn't missing, the redesign is" names this pattern directly: the AI returns on investment only when the operation around it is redesigned. Without that, the technical performance is real and the financial return is not.
What does the technical-only ROI look like?
The AI handles a real share of contacts. Containment numbers rise. Average handle time on the AI channel is shorter than the human channel. The vendor case study is true. None of it has reached the cost line yet, because the human team is still sized for the old volume and the contracts still price for the old workload.
Where does the redesign have to happen?
Four places. First, the headcount and skills mix of the human team: the residual contacts are harder, so the team is smaller and more specialist. Second, the metrics: AHT and CSAT for the human channel will look worse because of the work mix, and you need to set new baselines. Third, the BPO or service contracts, which are priced for old volume. Fourth, the QA and coaching loop, which now has to cover the AI's behaviour as well as the team's.
Why do most teams skip this?
Because the AI deployment is easier to scope than the operational change. Buying a vendor product is a procurement decision. Redesigning the work is a leadership decision that touches HR, contracts, and metrics. The first happens fast. The second drags. The ROI gets stuck in between.
What does it take to capture the value?
Plan the operational redesign as part of the AI deployment, not as a phase 2. Set the team size, the metrics, the contracts, and the QA loop before the AI goes live, with the projected volume mix in mind. Treat the AI rollout and the redesign as one project, owned by one person. The companies that did this saw the ROI. The companies that did not are running the AI and still paying for the old shape.
Related: the field note on AI ROI measurement, AI ROI and operational redesign, and how the contact-centre agent job is being redesigned.