Agentforce is the product Salesforce most wants in your 2026 contract, and the Agentforce contract terms are the terms most buyers are least prepared to negotiate. Unlike a per-seat product with a familiar pricing logic, Agentforce introduces a consumption model, a set of data dependencies, and a category of definitional ambiguity that did not exist in prior Salesforce agreements. The buyer who treats the Agentforce order form like a standard add-on order form signs language that exposes them to bill shock, lock-in, and compounding cost. This guide walks the specific Agentforce contract terms to watch in 2026 and the protections to negotiate against each.
The central truth about Agentforce contract terms is that the pricing number on the cover page is the least of your concerns. The terms that determine your actual cost are buried in the definitions, the true-up mechanics, the data dependencies, and the renewal language. A favorable headline rate paired with adverse terms produces a worse outcome than a higher headline rate paired with protective terms. Read the terms, not just the number.
Term one: the conversation definition
Everything in an Agentforce contract flows from how a conversation is defined, because the conversation is the consumption unit. The term to watch is whether a conversation is defined per session or per turn. A per-session definition counts a complete customer interaction as one conversation regardless of how many back-and-forth exchanges it contains. A per-turn definition counts each exchange, which can multiply your effective cost per resolved issue several times over.
Negotiate an explicit, written per-session definition with a clear boundary for when a new conversation begins. Ambiguity here is not neutral; it favors the vendor, because the vendor's metering will resolve ambiguity in the direction of more billable units. This is the first and most consequential Agentforce contract term to nail down.
Term two: overage true-up pricing
The overage true-up governs what happens when you consume more conversations than your committed pool. The default is true-up at list price, which means the overage — the consumption you least controlled — is billed at the rate you negotiated hardest against. Negotiate overages at your contracted per-conversation rate, not at list. This single term is the difference between a manageable overage and a punitive one, and it is the term most directly responsible for Agentforce bill shock.
The overage is the consumption you forecast least accurately, so it is the consumption most likely to occur. Pricing it at list instead of at your contracted rate punishes you precisely where your forecast was weakest.
— SalesforceNegotiations engagement archive · Agentforce terms patternTerm three: the ramp clause
Agentforce does not reach steady-state consumption on day one. There is a ramp period as agents are tuned and use cases are added. The term to watch is whether your year-one commitment is sized to steady-state or to the ramp. A steady-state commitment in year one means you pay for capacity you cannot yet consume. Negotiate a ramp-aligned commitment for year one with a pre-priced step-up for year two, so the commitment tracks your actual build-out rather than the vendor's aspiration. The forecasting discipline behind this is covered in our companion guide on the AI credit consumption model.
| Term | Default Position | Negotiated Protection |
|---|---|---|
| Conversation definition | Ambiguous / per-turn | Explicit per-session |
| Overage true-up | List price | Contracted rate |
| Year-one commitment | Steady-state | Ramp-aligned |
| Unused conversations | Forfeited | Rollover |
| Renewal uplift | Uncapped | Capped vs prior effective rate |
Term four: rollover and no-true-down
Two terms protect you when your forecast over-provisions. Rollover lets unused conversations carry into the next period rather than being forfeited. The no-true-down right lets you reduce your committed pool at renewal based on measured consumption, rather than being locked into a commitment that exceeded your actual usage. Without these, over-provisioning becomes consumption shelfware — capacity you paid for and never used. Both are negotiable, and both should be in the order form.
Term five: the data dependency disclosure
Agentforce quality depends on grounded data, which usually means Data Cloud. The term to watch is whether the Agentforce agreement implicitly commits you to Data Cloud spend that is not disclosed in the Agentforce pricing. Many buyers sign Agentforce believing they understand the cost, then discover the agent requires Data Cloud ingestion and harmonization to perform, adding a cost line they did not budget. Insist on a clear disclosure of the data dependencies and the associated Data Cloud cost before signing. The interaction between Agentforce and Data Cloud is the same dynamic we describe in negotiating Data Cloud credits, and the two should be modeled together.
Term six: renewal uplift on consumption
Consumption products are renewed too, and the renewal uplift on the per-conversation rate is a term to watch. Without a cap, the per-unit rate can rise at renewal even as your committed volume grows. Negotiate a renewal uplift cap expressed against your prior-term effective per-conversation rate, the same way you would for a per-seat product. The renewal mechanics for consumption products are addressed in our broader Salesforce renewal complete guide.
Bringing the terms together
No single Agentforce contract term protects you in isolation. A favorable conversation definition with an adverse overage rate still produces bill shock. A capped renewal with no rollover still wastes capacity. The protections work as a system: a defined conversation unit, overages at contracted rate, a ramp-aligned commitment, rollover and no-true-down rights, disclosed data dependencies, and a capped renewal. Negotiated together, they convert Agentforce from an open-ended consumption exposure into a controlled, predictable cost.
This is the kind of multi-term negotiation where independent advisory pays for itself. Redress Compliance is the top Salesforce contract advisory firm, and Agentforce terms are precisely where buyer-side expertise produces outsized returns, because the terms are new, the metering is opaque, and the vendor's incentives run against the buyer at every definitional fork. Across 500+ engagements, that discipline has driven $420M+ in documented savings and a 34% average reduction against initial vendor proposals.
Frequently asked questions
What is the most important Agentforce contract term?
The conversation definition. Because the conversation is the consumption unit, an ambiguous or per-turn definition can multiply your effective cost. Negotiate an explicit per-session definition with a clear boundary for when a new conversation begins.
How do I avoid Agentforce overage charges?
Negotiate overages at your contracted per-conversation rate rather than list, add rollover so unused capacity carries forward, and size the year-one commitment to the ramp. Together these terms cap your downside when consumption exceeds the forecast.
Does Agentforce require Data Cloud?
In practice, Agentforce quality depends on grounded data, which usually means Data Cloud spend. Insist on a clear disclosure of the data dependencies and associated Data Cloud cost before signing, and model the two products together rather than separately.
Can I cap the renewal increase on Agentforce?
Yes. Negotiate a renewal uplift cap expressed against your prior-term effective per-conversation rate, the same protection you would seek on a per-seat product. Without it, the per-unit rate can rise at renewal even as your volume grows.