Why Agentforce Isn't an AI Agent

Autonomous AI Agent: A software system that perceives its environment, sets its own sub-goals, selects tools independently, adapts its approach mid-task without human instruction, and carries context across sessions. The defining characteristic is goal-directed behavior — the system determines what to do, not just how to execute a task someone else specified.

Salesforce spent over $1 billion building Agentforce and gave it the main stage at Dreamforce. The pitch was direct: AI that would work autonomously on your behalf, parsing customer requests and handling them without human intervention. Then enterprise customers deployed it and discovered an architectural reality the demos had not made clear.

Agentforce performs best when given no more than 8 instructions per topic (Salesforce Ben via Paddo.dev). Each workflow requires a pre-written Agent Script, each topic a pre-configured escalation path. When a customer asks something outside those paths, the agent hands off to a human — and the company pays for a referral.

What "Autonomous" Actually Requires

A genuine autonomous AI agent starts from a defined goal. It identifies sub-tasks, selects from available tools, executes, evaluates the output, and adjusts course without a human mapping the steps in advance.

Agentforce uses an LLM for language generation while pre-defined scripts govern the decision logic. From the outside, this looks like one coherent AI conversation. The operational difference surfaces the moment a customer's request falls outside the configured paths.

That distinction has a practical cost. When a customer submits an edge case, an autonomous agent reasons through it using available tools and context. Agentforce escalates. As Salesforce Ben described the pattern that enterprise customers reported: "if every query gets escalated, now you're paying twice: once for Agentforce and again for a human — you've paid $2 just to be told someone else needs to help" (MyAskai).

What the Pricing History Reveals

Agentforce has cycled through three pricing models in eighteen months: $2 per conversation at launch in late 2024, Flex Credits at $0.10 per action in May 2025, then per-user add-ons later in 2025 (MyAskai, SaaStr). Three models in eighteen months reflects a product team still working out what the system delivers and how that maps to value received.

When the conversation ends in escalation, what did the $2 buy? The unit economics question matters because the total first-year cost for a typical mid-size Agentforce deployment runs $75,000 to $200,000 — implementation ($15,000–$100,000 one-time) plus Data Cloud licensing ($12,000–$50,000/year) (AgentforcePros). That outlay is defensible if the system is producing what the pitch described.

The Walk-Back

By 2026, Salesforce's public positioning had moved from the "autonomous" framing of its 2024 launch to an explicit emphasis on control. Salesforce Ben documented the shift: "Rather than positioning agents as fully autonomous decision-makers, Salesforce has placed greater emphasis on control, limiting where agents can improvise, and ensuring critical actions follow defined, predictable paths" (Salesforce Ben).

Salesforce made the right call architecturally for an enterprise product at scale, and the reframing confirms what practitioners had already observed: the "autonomous" pitch from 2024 did not survive contact with production. The Salesforce developer community picked this up directly. From a 2026 r/salesforce thread: "Wasn't the whole pitch that Agentforce would handle things on its own without us micromanaging it? Now we need to write Agent Scripts to control what it does? So we're back to manually mapping out workflows ourselves?" (Reddit r/salesforce)

A Scenario That Illustrates the Gap

A firm configures Agentforce to handle inbound service requests. They write Agent Scripts covering their five most common request types, configure escalation paths, and connect the system to their CRM. For those five types, the system performs as configured. When a client submits a request that sits between two categories — common in professional services where client needs rarely map cleanly to internal taxonomies — Agentforce escalates. The firm handles the same edge cases they handled before, with an added per-conversation cost for the routing.

A goal-directed system receiving the same inbound request reasons about which category fits best using available case data, drafts an initial response, attaches a confidence score, and routes to a human only when confidence falls below a configured threshold — rather than on every unscripted input. Per Enqcode's 2026 AI agent implementation analysis, companies that deploy goal-directed rather than script-directed systems see meaningful reductions in escalation rates on edge-case inputs (Enqcode).

At the surface level, both systems appear similar. The real dividing line is where decision authority lives: in the human who wrote the script in advance, or in the system that reasons from the client's actual input.

The Counterargument Worth Addressing

Agentforce will become more capable. Salesforce is investing in multi-agent architecture through MuleSoft integrations and Agent Network, and their CTO acknowledged "multi-agent intelligence is blocked by failures to establish open interoperability" as a core 2026 problem to solve (Salesforce). A Salesforce-native system will eventually offer integrations with CRM data and enterprise workflows that purpose-built agents cannot match.

Businesses buying Agentforce today should understand what they are purchasing: a configurable workflow automation layer with strong Salesforce ecosystem integration. That is a real purchase category with genuine value. The businesses that will get their $75K–$200K worth are the ones who understood the distinction before they signed.

What a Different Architecture Looks Like

An autonomous AI agent system starts from a defined goal — "qualify and respond to every inbound inquiry within two hours" — and builds the execution path at runtime. It pulls from connected tools (CRM, calendar, email, internal documents), makes judgment calls about which path best serves the goal, and hands off to a human only when it cannot proceed with sufficient confidence.

DeployLabs builds systems of this type for Canadian SMBs. The starting point is an AI Readiness Assessment — a two-week audit that maps where autonomous agents will multiply your team's output versus where simpler automation is the correct and cheaper answer. Not every workflow needs a reasoning agent. The assessment determines which is which before any build begins.

Related Reading

• What Is an AI Operating System? — the architecture frame behind goal-directed agent systems.
• The 42% Abandonment Problem — why AI projects die before they deliver.
• What Claude Cowork Tells Us About AI Adoption — what product design reveals about real-world adoption.