Salesforce Agentforce

What it is

Agentforce is Salesforce’s agent layer inside the CRM you already run — not a separate product you point at Salesforce. Since the Agentforce 360 release in October 2025 it has been the umbrella over Agentforce Builder (design an agent in natural language), Agent Script, Agentforce Voice, and agent observability, all grounded in Data 360, the renamed Data Cloud. Salesforce has since folded most of the portfolio under the name: Sales Cloud is sold as Agentforce Sales, and Revenue Cloud is now Agentforce Revenue Management. The scale is real and recent — Salesforce reported $1.2B in Agentforce ARR in Q1 FY27 on 2026-05-27, up 205% year over year, with 3.8 billion “Agentic Work Units” delivered to date across Agentforce and Slack. It is also buying its way forward: a definitive agreement to acquire Fin, formerly Intercom, for approximately $3.6B was announced 2026-06-15 and is expected to close in the fourth quarter of Salesforce’s fiscal 2027.

Why it shows up in RevOps stacks

• The agent runs on the record graph rather than beside it. Sharing rules, field-level security, and object permissions already govern what the agent can see and write. Nothing is copied into a separate index first, which is the argument every Salesforce-resident RevOps team makes when the security review starts.
• Hosted MCP servers went GA in April 2026 for Enterprise Edition orgs and above. Salesforce ships prebuilt servers for the Agentforce 360 Platform, Tableau Next, and Data 360 SQL, plus custom servers over your own flows and Apex actions. Auth is OAuth with PKCE on a dedicated MCP scope that does not grant access to the existing REST APIs, and the agent acts strictly within the requesting user’s own permissions. This is the honest reason to wire Claude or Cursor into Salesforce here instead of building a middle tier — and the read-only platform/sobject-reads server in a sandbox is where to start.
• The named GTM agent is narrower than the brand. Agentforce Lead Nurturing — renamed from SDR Agent — sends customized first-touch email, follows up when a prospect goes quiet, answers questions from company-supplied knowledge, detects interest, books meetings, and handles opt-outs. Email, not omnichannel. It requires Enterprise, Performance, or Unlimited edition with Sales and Einstein for Sales, plus Sales Engagement, Einstein Activity Capture, Einstein Generative AI, and the Outlook/Gmail productivity integration — and it is incompatible with Activity 360 Reporting.

Pricing reality

Salesforce publishes the agent meter, which is rarer than it sounds. Checked on the pricing page 2026-08-01:

• Salesforce Foundations — $0 to start, any use case
• Flex Credits — $500 per 100,000 credits ($0.005 each); a standard agent action burns 20 credits, so $0.10 per action
• Conversations — $2 per conversation for customer-facing agents. You cannot mix Conversations and Flex Credits in the same org
• Agentforce User License — $5/user/month, requires Flex Credits, limited CRM objects, metered usage — the line for putting an agent in front of every employee
• Agentforce add-ons — $125/user/month for Sales, Service, and Field Service, $150 for Industries, with unmetered employee usage
• Agentforce 1 Sales — from $550/user/month, add-on included, 2.5M Flex Credits per org per year

The meter is not the budget. Sales Cloud Enterprise is $175/user/month and Unlimited is $350, and both the named agents and the hosted MCP servers require Enterprise or above — so a team on Pro Suite at $100/user/month pays an edition upgrade before it pays for a single agent action. Price the edition, the agent SKU, and Data 360 consumption as one number.

Best for

RevOps leaders at companies already standardized on Salesforce Enterprise edition or higher, whose binding constraint is that agents must act inside the CRM’s own permission model rather than over an exported copy. It is strongest on inbound lead follow-up and on internal employee agents that read and update records.

Skip it when Salesforce is not your system of record, when your gap is cold outbound to a purchased list — Lead Nurturing grounds on engagement signal and a scraped contact has none — or when you want to test agents for under five figures a year.

Versus the alternatives

HubSpot Breeze is the SMB and mid-market pole, and since 2026-04-14 it prices on outcomes: $0.50 per resolved conversation and $1 per lead recommended for outreach. Against Agentforce’s $2 per conversation that is a 4:1 ratio on the same unit — pick Breeze when you are on HubSpot or when cost per resolved conversation is the deciding number. Rox and Day.ai are the fast-growing entrants and split on a single question: Rox layers an agent fleet on top of Salesforce and expects you to keep paying for both, while Day.ai argues you should replace the system of record instead. Pick Rox when you need agent behavior Salesforce will not ship without a rebuild, and Agentforce when you would rather not administer a second vendor.

If none of them fit, the fallback is Claude against the hosted MCP server, covered in the Salesforce MCP workflow. You get agent behavior over governed Salesforce data without buying the agent SKU; the trade is that you build, host, and monitor the orchestration yourself.

Watch-outs

• The pricing model is a one-way door per org. Flex Credits and Conversations cannot coexist, and moving between them means re-contracting. Guard: count actions for 30 days before signing. High-volume customer deflection favors Conversations at $2; internal employee agents doing many small reads and updates favor credits at $0.10 per action. Decide on the count, not the demo.
• Data 360 decides the budget, not the agent SKU. Grounding agents in unstructured content pulls Data 360 consumption that is contracted and metered separately from Flex Credits. Guard: require the Data 360 credit allocation and the overage rate in the same quote as the agent line, and refuse to sign the agent SKU on its own.
• The prerequisite list is where pilots slip. Lead Nurturing needs Sales Engagement, Einstein Activity Capture, Einstein Generative AI, and the email productivity integration all licensed and switched on, and it conflicts with Activity 360 Reporting. Guard: verify each prerequisite in your own org before you set a pilot date, and check the Activity 360 conflict against whatever reporting your team actually runs.
• Acquisitions are arriving faster than integration. Fin overlaps Agentforce Service, and Qualified overlaps inbound conversion. Guard: for any standalone contract that overlaps an announced deal, get written convergence terms — product, pricing, and migration path — before agreeing to a multi-year term.