Agentforce does not license like Sales Cloud or Service Cloud. It meters conversations, bundles into editions, and entitles actions. Understand the unit before you sign, because the unit decides the bill.
Agentforce is licensed by the conversation, wrapped in edition bundles, and gated by action entitlements. This guide walks the unit, the editions, the entitlements, and the contract terms that decide what you actually pay.
Agentforce is Salesforce's autonomous agent layer. The rest of the platform licenses per seat. Agentforce licenses per conversation, which moves the commercial question from headcount to usage.
That shift is the whole story. You know how many people you employ. You do not know, on day one, how many conversations an agent will handle or how many will resolve cleanly.
Agentforce bills on a consumption meter. The headline unit is the conversation, and Salesforce publishes the rate on its Agentforce pricing page.
A conversation is a bounded interaction, not a single message. One conversation can carry many turns and several agent actions. Message volume inside the session does not raise the count, which is friendlier than a per message meter.
Salesforce offers a prepaid Flex Credits pool that draws down as agents act. The choice between a fixed rate and credits is a forecasting decision, not a discount decision.
Agentforce is sold both as a consumption add on and inside an edition bundle. The bundle includes platform entitlements and a defined allowance of agent capability.
The top edition packages the Einstein platform, Data Cloud entitlements, and an Agentforce allowance. The allowance is a starting pool, not a production ceiling, so volume above it meters.
You can also buy Agentforce as a standalone consumption line on top of existing clouds. This route is simpler to scope but weaker on leverage, because it sits outside the renewal where rate trades happen.
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 is the billed unit, but actions are what consume cost inside it. A topic that chains retrieval, reasoning, and a write back costs more to serve than a single lookup.
Standard actions ship with the platform. Custom actions, built on flows or Apex, extend what an agent can do and can pull in more Data Cloud and model time. Map your action library before you forecast volume.
The standard account team pitch is that the per conversation rate is the number to negotiate. We disagree. In most of the licensing reviews we ran, the rate was the easy part and the conversation definition was the lever that moved the bill.
A vague unit definition let routine sessions split into several billable conversations. The buyer side move is to define the billable conversation in writing, cap the Data Cloud overlay, and only then negotiate the rate. Pin the unit before the price.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
License the unit, not the headline. The buyers who control Agentforce cost define the billable conversation first and negotiate the rate second.
Four clauses decide whether the license behaves the way your model assumed. Get them in the paper before you sign.
Write down what counts as one conversation. A precise definition stops routine sessions from splitting into several billable units, which is the single most common source of overrun.
Cap the per conversation rate uplift across the term and tie the rate to a volume tier. Confirm true forward terms on credits so unused pools carry sensible treatment at renewal.
Four moves recur in the engagements where the license stayed predictable.
Agentforce is licensed on a consumption meter, priced per conversation rather than per seat. A conversation is a bounded interaction that can span many turns and actions. Buyers commit either to a fixed per conversation rate or to a prepaid Flex Credits pool that draws down as agents act.
A conversation is one bounded session between an end user and an agent, not a single message. Multiple turns and multiple actions inside that session still count as one conversation. The session boundary is the unit Salesforce bills, so message volume inside it does not raise the count.
For grounded agents, yes in practice. Agentforce reasons over data surfaced through Data Cloud, and that consumption is metered on its own line. Treat the Data Cloud entitlement as part of the Agentforce license, not as an optional extra you can defer.
Flex Credits are a prepaid consumption pool that depletes as agents take actions. They suit uncertain or seasonal volume because you commit to a pool rather than a fixed rate. They lose to a negotiated per conversation rate when volume is high and steady.
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.
Yes. At committed volume the per conversation rate and the Data Cloud credit rate behind it 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 clauses that decide cost are the uplift cap on the per conversation rate, the true forward terms on credits, the ramp schedule, and the definition of a billable conversation. A vague conversation definition is the clause that quietly inflates the bill.
Fold it into the renewal. Agentforce has the most leverage as one line in a larger commitment, because the account team values the consumption upside. A standalone Agentforce order gives away that leverage and usually lands a worse rate.
Define the billable unit and the included allowance in writing before you commit volume. Most buyers sign the headline rate and miss the Data Cloud overlay and the conversation definition. Lock both, then negotiate the rate against a defensible 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.
Agentforce is not licensed on what you own. It is licensed on what your agents do. Get the unit right in the paper, and the run rate stops surprising the budget owner.
