If you read our scene-setter on the Board vs. The Floor tension — or watched the full video interview with Salesforce’s SVP of Agentforce Contact Center — you already understand the scale of the problem. Board pressure, operational reality, and a 95% pilot failure rate sitting between them.
This piece takes the conversation further. Because knowing the gap exists is only useful if you know how to close it.
Why most AI deployments fail (and it’s not what you think)
The instinct when a contact center AI deployment underperforms is to blame the technology. But three failure modes are far more common — and far more fixable.
“The challenges come from three failure modes. AI deployed in isolation. Organisational gaps in knowledge ownership. And the metrics being used to define success.”
— Gautam Vasudev, SVP Agentforce Contact Center, Salesforce
The first is isolation: AI deployed without access to the customer data that makes it useful. No purchase history. No case context. No policy knowledge. The second is organisational — fragmented ownership of knowledge with no accountability for keeping it current. Gartner found 61% of service leaders have a backlog of knowledge articles to update and more than a third have no formal process for revising content. In that environment, an AI agent amplifies existing problems rather than solving them.
The third failure mode is measurement. Optimising for deflection rates and declaring that as ROI is the wrong goal. Counting containment while customers quietly escalate through another channel isn’t progress — it’s a metric designed to tell you what you want to hear.
The data problem nobody raises in the sales meeting
There is one insight CX leaders should carry into every vendor conversation this year: the triple penalty.
“When you ground your AI in stale or badly structured data, you pay a triple penalty. Unsatisfactory responses. Frustrated escalations to human agents. And the risk of hallucination. You have to be very careful about this.”
— Gautam Vasudev, SVP Agentforce Contact Center, Salesforce
The practical diagnostic Vasudev recommends is straightforward: map your top 20 high-volume customer intents to your current knowledge articles.
“That gives you a report card — whether you’ve got an A grade, a B grade, or a C grade in your knowledge coverage.”
Most organisations discover they are not where they assumed. That discovery is uncomfortable. It is also the most valuable thing you can do before committing to a deployment timeline.
Why some contact center AI deployments reach production while others never do
Speed of deployment is not determined by the technology decision. It is determined by what happens before it.
“The single biggest differentiator between teams that reach production and teams that don’t is predefined success criteria — with alignment internally before a single line of code is written.”
— Gautam Vasudev, SVP Agentforce Contact Center, Salesforce
That alignment spans IT, service operations, finance, HR, and increasingly legal. “This is not a hero’s journey,” Vasudev says. “This is really a collaborative effort.” The use cases that move fastest are the ones where the organisation already has a natural advantage: clean data, structured knowledge, high-volume queries with predictable patterns.
Reframing the board conversation
The language used with a CFO matters more than most CX leaders appreciate. “Starting with a pilot” invites scepticism. “De-risking a strategic investment” opens a very different conversation.
“For a CFO, this becomes a conversation of not ‘hey, we are starting a pilot.’ It becomes ‘we are de-risking a broad, strategic, large investment.’ And every CFO loves the word de-risking.”
— Gautam Vasudev, SVP Agentforce Contact Center, Salesforce
Commit to what you will deliver in 90 days, define it in measurable terms, and position it as the foundation for the next phase of the roadmap. That is the structure that makes board confidence durable rather than borrowed.
The 12-month roadmap to deploying AI in the contact center
Months 1–3: Foundation
Audit top intents. Clean knowledge. Confirm integrations. Stand up agent assist for human reps. Unglamorous work that determines everything that follows.
Months 3–6: First autonomous deployments
High-volume, low-risk queries. Order status. Password resets. Basic account management. Measure honestly and catch failure signals early.
Months 6–12: Compounding
ROI from phases one and two funds expansion into more complex workflows. A good example of how real world customers are using Agentforce Contact Center is Compass Working Capital. By streamlining the enrollment process for their clients, unifying their data, and giving their teams AI-driven insights, they reached 6,000 agent hours saved annually at this stage. “That is all the result of the foundational work done in months one through six,” Vasudev notes. “It is not the starting point.”
The workforce design decision nobody makes deliberately
When AI handles simple queries, it concentrates every complex, distressed, emotionally demanding interaction into the remaining human queue. Seventy-five percent of contact center leaders now believe their AI investments are increasing agent stress. The solution is not less automation, but better design.
“Agent assist is a game changer. It gives reps the confidence to always answer with consistency and the highest quality. Customers tell us it was the single most important deployment they made on their AI journey.”
— Gautam Vasudev, SVP Agentforce Contact Center, Salesforce
Breathing room for agents does not happen by default. It is a design decision — and the organisations building it deliberately are seeing cost performance and employee satisfaction move in the right direction simultaneously.
Why the platform underneath all of this matters
The playbook above is only achievable at pace if the underlying platform has the data depth to support it from day one. Agentforce Contact Center is built on the same platform that already holds customer history, case records, service knowledge and interaction context, meaning AI and human agents work from the same source of truth from the first interaction. No integration tax and no context lost at handoff. The triple penalty is structurally harder to trigger when the data foundation is the CRM itself.
The organisations that will look back on 2026 as the year they got this right are making foundational investments now that will not show up in a six-month board update – but that will determine every ROI conversation that follows. The playbook is available. The gap is closable. The question is whether your organisation approaches it with evidence or with optimism.
