For years, customer experience teams have been sold the same promise: put a chatbot on the front door, deflect some contacts, and call it transformation.
The problem is that most of those bots are flat.
They can retrieve a help article. They can recognize a keyword. They can point a customer toward a form, a phone number, or another queue. But when a customer has a real problem—an exception, a missing order, an account issue, or a complex request—they often reach the same dead end: “I can’t help with that.”
That is why I have started calling them flatbots.
At Dreamforce 2026, walking through Salesforce’s Agentic Enterprise City and speaking with brands including F1, Live Nation, Crocs, and SPECS, I saw a different ambition emerging. These organizations are not simply trying to make chat more conversational. They are trying to connect AI to the data, workflows, and actions required to actually solve a customer problem.
That distinction matters.
Different Deployment Methods, the Same Destination
The most impressive thing was not that every brand had deployed AI in exactly the same way. They had not.
The range of approaches was striking. Some were using prebuilt Agentforce interfaces and agents. Others were using Salesforce’s newer headless capabilities to create their own front ends on top of Salesforce data and workflows. Some were using AI-assisted—or “vibe-coded”—development to create new experiences for customers, frontline teams, managers, and leaders.
Different deployment methods. The same destination: personalize the experience, resolve more issues digitally, reduce avoidable escalations, and create commercial value from better customer interactions.
That is a much more meaningful ambition than chatbot containment.
From Digital Response to Digital Resolution
Fin, Salesforce’s most recent acquisition, brought a useful proof point to the conversation. It says its customers achieve an average 76% resolution rate through digital interactions.
That is an impressive vendor-provided figure, but the more important point is what it represents: a customer getting the outcome they need without repeating themselves, waiting in another queue, or beginning the journey again with a human agent.
Of course, a number alone does not settle the CX case. Leaders should ask what is being counted as resolved, what happens to repeat contacts, and whether customers are satisfied with the handoff when the AI cannot continue.
But it is a more useful measure than asking whether a bot simply responded.
Salesforce Wants CRM to Become the Layer Beneath the Experience
Salesforce’s wider Dreamforce strategy is built around this shift. Its AIforce proposition is that the traditional CRM interface matters less than the governed layer underneath it: customer data, permissions, business rules, workflows, security controls, and approved actions.