Salesforce's Agentic AI Push: Easy Deployment, Hard Decisions

Salesforce used Dreamforce 2026 to announce a sweeping set of AI capabilities—AIforce, expanded Agentforce, Contact Center as a Service, and Koa, a CRM reasoning model built with NVIDIA. But according to Liz Miller, VP and Principal Analyst at Constellation Research, the real story isn't the technology itself. It's Salesforce's attempt to make agentic enterprise AI faster to deploy.

"Honestly, the story is an easy button," Miller told CX Today at the event. "It's about being able to stand up agents, stand up skills in days rather than years."

That promise of speed, however, doesn't eliminate the harder strategic questions CX leaders must answer: which processes are ready for autonomous agents, where human judgment remains essential, and who takes responsibility when AI makes a mistake.

Why it matters

As enterprise AI moves from answering questions to taking actions—resolving service cases, updating orders, making recommendations—the stakes shift from accuracy to accountability. CX leaders can't treat agentic deployment as a pure technology decision. They're choosing which customer interactions to automate, what boundaries to enforce, and how to recover when systems fail. Faster implementation doesn't guarantee better outcomes if the underlying processes, data, and governance aren't ready.

Start With the Work, Not the Interface

Salesforce positioned AIforce as a way to deliver CRM context and approved actions across multiple surfaces: Claude, Slack, Lightning, or custom-built experiences. The company's headless architecture lets organizations use Salesforce data and business logic without being locked into its traditional interface.

Miller's advice: don't start with the interface question. Start with the work.

"You have to think about work first," she said. Different roles—marketers, sellers, contact-center agents—operate in different tools. They shouldn't be forced into a universal interface just because it's strategically important to the vendor. Instead, they should receive trusted customer context and approved actions in the environments where they already work.

For contact-center agents, that means avoiding "swivel chair" workflows that require jumping between tabs or learning new systems. For field teams or specialized roles, it might mean a custom front end built on Salesforce's governed data layer.

The risk is that organizations focus on the novelty of AI-generated interfaces while neglecting the operational fundamentals beneath them: accurate data, clear business rules, reliable permissions, and effective escalation paths.

Koa Brings CRM-Specific Reasoning

One of the week's most significant announcements was Koa, Salesforce's new reasoning model developed with NVIDIA and trained on synthetic data rather than customer records.

Miller emphasized that Koa isn't just another large language model. "Koa understands the function of CRM. It understands the functionality, it understands the nuance and the difficulty which has been operating these CRM strategies within these technologies," she said.

The distinction matters for complex service cases. General-purpose models can produce fluent language, but enterprise CX requires understanding the customer's history, entitlements, applicable policies, and approved next actions. Koa is designed to handle multi-step CRM work, including next-best-action recommendations in sales and service scenarios.

Still, CX leaders should demand evidence: how does Koa perform on real cases, against which benchmarks, and does it improve resolution quality, policy adherence, and handoff effectiveness—not just model accuracy?

From Bots to Agents: A Critical Distinction

Miller stressed that the current wave of AI represents a shift from chatbots to relationship agents. "I don't want it to be a bot. I want it to be a conversation, and I want it to be part of the relationship," she said.

The legacy chatbot promised faster answers. Agentic CX promises context, action, and outcomes. But "conversation" can't become another soft metric. The real test is whether the organization solved the right problem—not whether the interaction felt natural.

The Agentic Enterprise Is a Choice

Looking ahead, Miller said organizations face a fundamental decision: do AI things, or become an agentic enterprise.

Running limited experiments or deploying narrow-use-case agents is one path. Becoming an agentic enterprise requires deeper readiness: usable data layers, orchestration, security, governance, and coordination across IT, digital, operations, and CX teams.

CX leaders should ask which customer journeys need better outcomes, not just faster responses. Which processes have mature enough data and policies for autonomous action? Where must humans remain available? What should agents be allowed to do independently? And critically: can the organization explain, audit, reverse, and recover from an agent's mistake?

Trust Means Accountability

Salesforce emphasized trust throughout Dreamforce, highlighting its Trust Layer, zero-data-retention protections, and governance tools. Miller argued the industry needs precision about what trust actually means.

"Trust has to start meaning something," she said. Many supposed trust concerns are really fear—about jobs, uncertainty, unexpected system behavior. The concrete trust issue is enterprise risk: what data is being used, what controls exist, and who is accountable when automated actions affect customers.

Customers won't distinguish between Salesforce, third-party model providers, integration partners, and the deploying organization. If an agent makes a harmful decision, they'll hold the brand responsible. Agentic CX isn't just a technology deployment—it's a customer-accountability program.

These details were first reported by CX Today in coverage of Dreamforce 2026.