Salesforce Agentforce: Ten Moves That Set Your Conversation Price
At the $2.00 per conversation list price, the committed volume, not the discount rate, decides the bill. In the Agentforce deals we benchmarked in 2024 to 2025, 30 to 50 percent of committed conversations would have expired unused.
Prepared by Redress Compliance · June 2026 · Representative Salesforce estate scenario (benchmark scenario, not a quote)
Executive Summary
Salesforce prices Agentforce on consumption, not on seats: $2.00 per conversation at list, Flex Credits at $500 per 100,000 credits ($0.10 per standard action), and the Agentforce 1 edition at roughly $550 per user per month. Every one of those numbers moves. The volume you commit moves further.
Across roughly 20 to 35 Agentforce negotiations we benchmarked in 2024 and 2025, committed conversation volume ran 30 to 50 percent above first year actual use. Unused conversations expire. The largest saving in an Agentforce deal is the volume you decline to commit, not the discount you win on it.
This paper delivers the ten buyer side moves: the conversation volume model, the edition decision, Data Cloud sizing, the overage rate, substitution rights, the uplift cap, anniversary opt outs, the ROI framework, Q4 timing against the January 31 fiscal close, and monthly consumption governance.
It closes with the seven clause contract appendix, discount benchmarks from our advisory engagement file, and a self assessment diagnostic. A representative insurer estate runs through the paper as the worked example (benchmark scenario, not a quote).
Build the Conversation Volume Model First
The commitment conversation starts with your model or with theirs. The account team forecast assumes aggressive deflection from day one. Your model starts from actual contact center volumes, scopes only the use cases that will be live in year one, and applies a conservative containment rate.
The worked scenario in this paper is a North American insurer: 5,500 Service Cloud users and 2.4 million inbound service contacts per year. Salesforce proposed a three year commitment of 1.2 million conversations per year. The modeled year one baseline came to 420,000.
| Year one agent use case | Annual contacts | Containment assumption | Modeled conversations |
|---|---|---|---|
| Order and policy status | 520,000 | 40% | 208,000 |
| Account and password service | 430,000 | 30% (rounded) | 128,000 |
| Claims status | 280,000 | 30% | 84,000 |
| Modeled year one baseline | 1,230,000 | 420,000 |
The remaining 1.17 million contacts (billing disputes, coverage questions, everything not yet piloted) stay out of the commitment until an agent handles them in production. First year actual use in this scenario ran to 380,000 conversations, under the modeled baseline.
Proposed commitment vs modeled baseline vs actual use. Benchmark scenario, not a quote.
At a negotiated $1.50 net rate, the proposal prices at $1.80 million per year. The modeled baseline prices at $630,000. Declining the unproven 780,000 conversations saved $1.17 million in year one and cost nothing in capability.
Choose the Commercial Path Deliberately
Agentforce reaches you through four commercial doors, and they price differently. The Einstein 1 editions of 2024 have been folded into the Agentforce 1 edition; the bundle question is the same question with a new name. Decide on arithmetic, not on the account team's preferred packaging.
| Path | List price | What it is | When it wins |
|---|---|---|---|
| Conversations | $2.00 per conversation | Standalone consumption commitment drawn down by agent conversations | Service deflection with long, multi step conversations |
| Flex Credits | $500 per 100,000 credits | $0.10 per standard action, $0.15 per voice action; the only path sold pay as you go or pre commit | Short interactions and pilots; under 20 actions per conversation |
| Agentforce add on | $125 to $150 per user per month | Per user AI add on to existing Sales and Service Cloud editions | Assistive AI for a defined user population |
| Agentforce 1 edition | About $550 per user per month | The successor bundle to Einstein 1: edition plus Agentforce plus a Data Cloud allocation | Heavy per user AI usage across a small, intensive population |
The bundle math in the worked scenario: a 1,200 agent service organization on Agentforce 1 prices at $7.92 million per year (1,200 users at $550 for 12 months). The same organization on Enterprise edition at $165 per user costs $2.376 million, plus the 420,000 modeled conversations at $1.50 for $630,000: $3.01 million in total, 38 percent of the bundle price.
The crossover between conversations and Flex Credits is mechanical. At $0.10 per standard action, a conversation averaging fewer than 20 actions is cheaper on credits; above 20 actions, the flat $2.00 conversation wins.
Run your own action counts from pilot telemetry before choosing the meter.
Size the Data Cloud Commitment to Real Data Scope
Production Agentforce runs on Data Cloud (rebranded Data 360 in October 2025), and Data Cloud has its own meter. Credits list at $500 per 100,000 and burn against rows processed. Identity resolution is the expensive operation: roughly 100,000 credits per million rows, and it reprocesses the full row set on every run, not just the changed rows.
That mechanic is the trap. A 20 million row profile set unified monthly draws about 2 million credits a month, roughly $10,000 per month at list before any discount. Size the commitment to the data the agents actually need, not to the whole estate.
- Scope by use case: ingest only the objects the year one agents query. Exclude marketing profile data the service agents never touch.
- Schedule unification: monthly rather than streaming identity resolution cuts the credit burn for most service estates.
- Refuse bundled allocations you cannot map: a Data Cloud allocation inside Agentforce 1 still expires unused if your data scope does not need it.
Validate every consumption assumption against the published rate card on the Salesforce Data 360 pricing calculator before you accept a credit number in an order form.
Negotiate the Overage Rate, Not Just the Headline Rate
The overage rate is where conversation pricing punishes adoption. In most first generation Agentforce order forms we reviewed, usage above the committed block was simply undefined, which defaults to list price at $2.00, in arrears, with no notice obligation.
Fix three numbers in writing before signature. The overage rate itself (at or near your committed net rate, never list). A notification threshold at 80 percent of the pro rata block. And a true up window that lets you convert overage into committed volume at the committed rate within 30 days.
Win Substitution Rights Across Agents and Meters
By default, your conversation block is locked to the SKU you bought. Salesforce permits converting conversation packs into Flex Credits, or reallocating volume across agent types and orgs, only at renewal, unless the contract says otherwise. On a product line repackaged twice in 18 months, that lock is the real risk.
This is the side letter language we negotiate for Fortune 500 clients, adapted per deal:
The dollar equivalence wording matters. Conversion at equivalent list units rather than equivalent dollars silently strips your discount in the exchange.
Cap the Uplift on Consumption Pricing
Salesforce order forms default to a renewal uplift, typically around 7 percent, and consumption SKUs inherit it. On a growing conversation block, the uplift compounds against rising volume: price and quantity climb together.
Negotiate a renewal cap of 0 to 3 percent on the per conversation and per credit rates. Then protect the discount band itself: in standard Salesforce practice, the discount tier can reset if committed volume drops at renewal, so a customer who rightsizes the block gets repriced upward. Write the discount as durable across volume changes within a stated range.
Neutralize the Three Year Commitment Trap
The standard pitch is a three year conversation commitment to lock the unit rate before adoption scales. On Agentforce, the term is the trap. The product is maturing through monthly release cycles, and the commercial model itself has changed twice since launch: conversations arrived in 2024, Flex Credits in 2025, and the Data 360 repackaging in October 2025.
Here we disagree with the standard reseller advice outright. Locking three years of volume on a product whose meter may not exist in its current form at renewal converts a pricing hedge into stranded inventory. In the deals we benchmarked, early large commitments outran real usage by 30 to 50 percent, and expired volume erased the unit rate advantage.
The buyer side structure: an annual term, or a three year paper with an opt out right at each anniversary on the Agentforce line only, plus rate protection language that holds the negotiated discount if you renew. You keep the price; Salesforce keeps the relationship; nobody warehouses dead conversations.
Prove the model
Commit the modeled baseline only (420,000 conversations in the worked scenario). Fix the overage rate, the definition clause, and the substitution right at signature.
Expand on evidence
Grow the block against actual telemetry at the protected discount. Exercise conversion rights if action counts favor Flex Credits.
Renegotiate from strength
Renew with two years of consumption data, a clean exit option, and benchmarks. This is when a longer term becomes rational.
Build the ROI Framework Before Signature
An Agentforce business case survives board review when it is denominated in cost per resolved conversation, not in licenses bought. Set the baseline before the pilot: a fully loaded human handled contact in most service estates runs $6 to $12. The agent comparison must carry its full stack.
| Metric | Definition | Board test |
|---|---|---|
| Cost per resolved conversation | Conversation rate plus allocated Data Cloud and platform cost, divided by contained resolutions | Below the loaded human cost for the same intent |
| Containment rate | Conversations resolved with no human escalation | Measured per use case against the model in section 1 |
| Escalation quality | Share of escalations arriving with usable context | Handle time on escalated contacts must fall, not rise |
| CSAT delta | Satisfaction on agent handled vs human handled contacts | No statistically significant decline |
Two of the four metrics are about escalations because that is where pilots fail quietly. A 40 percent containment rate with chaotic handoffs costs more than the contact center you had.
Time the Commitment to Q4 and Use the Benchmarks
Salesforce's fiscal year ends January 31, and Agentforce is the growth story the company reports on. An Agentforce commitment signed in the November to January window carries measurably deeper discounts than the same paper signed in spring. Run the evaluation on your calendar; sign on theirs.
Median negotiated discount on Agentforce conversation packs closed in Salesforce Q4 across our engagement file.
Median negotiated discount on comparable conversation pack commitments closed in fiscal Q1 to Q3.
| SKU | Observed discount range | Primary lever |
|---|---|---|
| Agentforce conversation packs | 25 to 45% | Committed volume tier plus Q4 timing |
| Data Cloud credits | 30 to 50% | Multi year credit commitment sized to modeled burn |
| Agentforce 1 edition | 20 to 35% | Edition migration scope and competitive pressure |
| Agentforce add ons | 15 to 30% | Attach rate across an existing user base |
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025. Ranges reflect negotiated outcomes on enterprise commitments, not list adjustments.
Discount ranges match the table above. Benchmark ranges, not a quote.
Anchor every rate conversation against the published list on the Salesforce Agentforce pricing page. If the proposal hides the Agentforce line inside a wider renewal number, demand the line level price before discussing anything else.
Govern Consumption Monthly After Signature
The contract sets the price; governance keeps it. Stand up a monthly consumption review before go live, owned by the software asset manager, with the dashboard covering conversations consumed against pro rata block, actions per conversation, Data Cloud credit burn, and containment by use case.
Two thresholds drive action. At 80 percent of the pro rata block, the overage notification clause from section 4 triggers a commercial review. A sustained run rate below 60 percent triggers the substitution clause from section 5 at the next anniversary, converting surplus into credits you will use.
Appendix: The Seven Clauses That Decide Flex or Lock
These seven clauses decide whether the commitment flexes with usage or locks you to a static conversation pool. Every one is negotiable before signature and nearly immovable after.
| Clause | What it must say | Default if silent |
|---|---|---|
| 1. Conversation definition | Minimum interaction count; abandoned and immediately escalated sessions excluded | Every 24 hour session bills at the full rate |
| 2. Overage rate | Overage at committed net rate with an 80 percent notification threshold | List price in arrears, no notice |
| 3. Carryover | Unused committed volume rolls forward 12 months within the term | Expires at each anniversary |
| 4. Substitution and conversion | Annual conversion of up to 30 percent of volume across SKUs at equivalent dollar value | Locked to the purchased SKU until renewal |
| 5. Uplift cap | Renewal uplift capped at 0 to 3 percent on consumption rates | Standard uplift, around 7 percent |
| 6. Anniversary opt out | Termination right on the Agentforce line at each anniversary with discount preservation on renewal | Full term lock |
| 7. Consumption reporting | Monthly machine readable usage reports at line item level | Self service dashboards only, no contractual cadence |
Self Assessment: Are You Ready to Sign?
Answer before the commercial meeting. Each no is leverage you have not yet used.
- Do you have a conversation volume model built from your own contact data, by use case?
- Have you priced all four commercial paths (conversations, Flex Credits, add on, Agentforce 1) against that model?
- Do you know your average actions per conversation from pilot telemetry?
- Is the Data Cloud credit estimate mapped to named objects and a unification schedule?
- Is the overage rate, the conversation definition, and the carryover right in the draft paper?
- Does the draft contain the substitution clause and an anniversary opt out?
- Is your signature date inside the November to January window?
- Is there a named owner for the monthly consumption review?
Three or more answers of no means the deal is not ready to sign, whatever the discount on the table says.
Our recommendation: do not sign the proposed conversation block. Commit the modeled year one baseline, and make the paper flex.
- Before signature: build the volume model from your own contact data, price all four commercial paths against it, and fix the overage rate, conversation definition, carryover, and substitution clauses in the draft.
- At signature: take the annual opt out and the uplift cap, close inside the Q4 window against the benchmark ranges in section 9, and stand up the monthly consumption review before go live.
Redress Compliance runs this sequence as a fixed scope engagement on live Agentforce deals. We are glad to tie a meaningful part of the fee to delivered value.
