When vendors pitch contact center AI, the business case focuses on implementation cost and projected containment rate savings. The math is straightforward: AI handles 60 to 70 percent of common inquiries, agent workload drops, response times improve, operational cost falls. The numbers in the proposal are usually accurate.
What the pitch does not emphasize is the ongoing operational cost of keeping the AI performing at the level that justified the investment in the first place. Virtual agents are not install-and-forget technology. They are operational systems that degrade without continuous care — and the cost of that care is the line item most business cases never include.
This is the prompt engineering tax. It is not hidden because vendors are dishonest. It is hidden because the vendor's incentive is to close the deal on the strength of the projected containment rate, not to model what it costs to sustain that rate eighteen months in.
Prompt engineering at launch focuses on training the AI to handle known inquiry types based on historical data. That is necessarily a snapshot — it reflects customer language, product catalog, business processes, and demand patterns as they existed at one point in time. According to research from MIT on AI system maintenance, AI models can degrade 10 to 15 percent in performance within months without active optimization. Four forces drive that decay, and none of them are unusual or avoidable — they are simply continuous.
None of these four drivers are signs that something went wrong with the implementation. They are what normal business operation looks like. The problem is not that the business kept changing — it's that the AI's training and prompts were treated as a one-time deliverable instead of an operational asset that needs the same ongoing attention as the business itself
Continuous prompt optimization is a different discipline from initial prompt engineering, and it requires different things: regular review of conversation logs to identify where the AI is failing or giving outdated answers, updates to knowledge bases and prompts as products and policies change, recalibration ahead of known seasonal demand shifts, and ongoing monitoring of containment rate as a leading indicator rather than a one-time launch metric.
This is not a part-time addition to someone's existing role. Sustaining performance at scale requires dedicated time from someone who understands both the AI platform's mechanics and the business context well enough to know what 'correct' looks like as the business evolves. Most organizations have not assigned that role, because the original business case did not account for needing it.
The gap between the vendor's business case and the real cost of ownership comes down to four components.
If you are building or reviewing a business case for contact center AI, three additions make the difference between a projection that holds up and one that quietly fails by month twelve:


