Agentforce prices per conversation, near two dollars on the standard meter. The list rate is the start. The Data Cloud overlay and the add ons decide what lands on the invoice. Here is the 2026 price picture.
Agentforce prices near two dollars per conversation in 2026, with a Data Cloud overlay and add ons behind it. This reference walks the rate, what it includes, the add ons that move it, and the buyer side levers that cut it.
Agentforce is Salesforce's autonomous agent layer, and it prices unlike the rest of the platform. Sales Cloud and Service Cloud charge per seat. Agentforce charges per conversation.
That difference is why budgets get surprised. Seats are easy to count. Conversations are not, and the rate alone never tells you the bill.
The headline is near two dollars per conversation on the standard meter, published on the Agentforce pricing page. The honest answer is a range, because the overlay and rework move it.
A conversation is a bounded session, not a single message. It can carry many turns and several actions. Message volume inside the session does not raise the count, which keeps the meter simpler than a per message model.
Salesforce also offers a prepaid Flex Credits pool. Credits suit uncertain volume, a fixed rate suits steady volume. Choose on forecast confidence, not on the discount on offer.
Agentforce 2026 cost stack, illustrative ranges per resolved conversation
| Cost layer | Driver | Range added | Buyer control |
|---|---|---|---|
| Conversation meter | List rate near two dollars | Base | Negotiate at volume |
| Data Cloud overlay | Grounding and retrieval | 25 to 60 percent | Right size the pool |
| Model premium | Premium model selection | 0 to 20 percent | Default to standard model |
| Escalation rework | Failed resolve plus handoff | 12 to 30 percent | Tune topics and guardrails |
Agentforce reaches the invoice by four routes. They do not carry the same bargaining position, and most buyers choose on how easy the route is to scope rather than on which route the account team has a reason to fund.
The top edition packages the Einstein platform, Data Cloud entitlements and a defined Agentforce allowance. Salesforce sells this as Einstein 1 Edition and Agentforce 1 Edition. Read the included conversation or credit allowance line by line before you sign the edition, because the bundle headline rarely covers production scale on its own.
The allowance is a starting pool, not a production ceiling. Every conversation above it meters at the standard rate. Across the licensing reviews behind this page, edition bundle allowances covered 15 to 40 percent of first year production volume and no more. Size the allowance against real first year volume, price the remainder at the metered rate, and add that number to the bundle price before you compare routes.
You can also buy Agentforce as a standalone consumption line on top of the clouds you already own. It is the simplest route to scope and the weakest one to negotiate, because it sits outside the renewal where rate trades happen. A standalone order asks the account team for a concession it has no reason to pay for.
Agentforce licensing routes, illustrative comparison
| Route | Billing unit | Best when | Leverage |
|---|---|---|---|
| Fixed per conversation | Conversation | High steady volume | High in a renewal |
| Flex Credits pool | Credit drawdown | Uncertain volume | Moderate |
| Edition bundle | Allowance plus meter | Platform consolidation | Moderate |
| Standalone add on | Conversation | Single use case | Low |
The conversation rate covers the interaction. Two costs that buyers expect to be included usually are not.
Grounded agents read from Data Cloud, and that read is metered separately. The overlay is the single largest line outside the headline rate. Budget it as core Agentforce cost.
Premium model selection costs more than the standard model. Default agents to the standard model and reserve premium models for the topics that measurably need them.
Three add ons move the effective price the most. Each sits outside the conversation rate.
The conversation is the billed unit. Actions are what consume cost inside it. Standard actions ship with the platform. Custom actions built on Flows or Apex draw more Data Cloud and more model time, and a topic that chains retrieval, reasoning and a write back costs more to serve than a single lookup. Map the action library before you forecast volume, because the action mix decides where in the table above a given topic lands.
Stack the four layers in that table at their floors and you get 1.37 times the list rate. Stack them at their ceilings and you get 2.10. That is the 1.4 to 2.1 band, and the action mix is what places you inside it.
Every Agentforce business case handed to us opens the same way. Two dollars beats a human interaction, so the payback is obvious. It is not. Across the pricing reviews behind this page the loaded cost per resolved conversation landed 1.4 to 2.1 times the headline rate once the Data Cloud overlay and escalation rework were counted, and on low volume topics it ran past the human cost it was bought to replace.
Commit only where volume is high and the resolve rate is clean, and let pilot data rather than the account team's forecast set the committed number. Then write the billable conversation definition into the paper in your own words, because a vague unit rewrites the arithmetic after you have signed.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Price the resolved conversation, not the meter. The rate is the easy number, the overlay and the rework are the ones that decide the invoice.
Four moves recur where the run rate stayed under control.
Four clauses decide whether the meter behaves the way your model assumed. Get all four into the paper before you sign the consumption commitment.
The first clause is the one that costs money. Leave the unit vague and one routine session can split into several billable conversations. That is the single most common source of overrun we see. Pin the unit before you argue the price, because the price is applied to whatever the unit turns out to be.
Agentforce lists near two dollars per conversation on the standard meter in 2026. A conversation can include several agent actions, so the effective cost depends on the action mix. Flex Credits offer a prepaid consumption alternative for spiky or uncertain volume.
The conversation rate covers the agent interaction itself. It does not, on its own, cover the Data Cloud consumption that grounds answers or any premium model usage. Budget those as separate metered lines that sit on top of the headline rate.
An edition bundle includes platform entitlements and a defined allotment of Agentforce capability, but consumption above the allotment still meters. Read the included conversation or credit allowance carefully, because the bundle headline rarely covers production scale on its own.
Because the list rate is only the base layer. The Data Cloud overlay, premium model selection, and escalation rework all add cost. In our reviews the loaded cost per resolved conversation ran above the headline rate once those layers were counted.
The three that move the price most are the Data Cloud overlay for grounding, premium model usage, and the volume of conversations that escalate after failing to resolve. Each one sits outside the headline conversation rate and is metered on its own.
It depends on volume. Flex Credits win when volume is uncertain or seasonal because you prepay a pool. A negotiated fixed per conversation rate wins when volume is high and steady. The choice is a forecasting decision, not a discount decision.
Yes. At committed volume the per conversation rate and the Data Cloud credit rate are both negotiable. Tie the rate to a volume tier and fold it into the wider Salesforce renewal, where the account team will trade rate to land the consumption commitment.
The metric that matters is cost per resolved conversation, not per conversation. A conversation that escalates still bills, so a low resolve rate quietly raises the effective price. Track resolve rate from week one to see the true cost.
Yes. Agentforce has the most pricing leverage as one line in a larger renewal commitment. A standalone Agentforce order gives away the leverage the account team has to trade rate against the wider consumption upside.
Model the loaded cost per resolved conversation before you sign. Most buyers price the list rate and forget the Data Cloud overlay and escalation rework. Build the loaded cost first, then negotiate the rate against a defensible volume forecast.
The conversation meter, the Data Cloud overlay, the edition bundle math, and the renewal levers that cut the run rate across the Salesforce estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The Agentforce list rate is the cheapest number in the deal. What you actually pay is the rate plus the overlay plus the conversations that fail to resolve. Price the total.
