The Agentforce true-forward renewal is the newest and least understood mechanic in the Salesforce commercial playbook, and it is already reshaping how enterprises think about their AI commitments. Unlike a traditional seat renewal, where the negotiation centers on per-user rates and headcount, the Agentforce true-forward turns on a single number that most buyers have never tracked carefully: how many agent conversations you actually consumed during the term. That consumption number does not refund the unused balance — it resets the floor under your next-term commitment. Understanding the Agentforce true-forward renewal before it arrives is the difference between a controlled, data-driven negotiation and a surprise uplift that the account team has been forecasting for nine months while you were not.
Across our advisory engagements, the Agentforce true-forward is producing the same pattern we saw in the early Data Cloud consumption agreements: enthusiastic over-commitment at the initial purchase, slow real-world adoption, and a renewal conversation in which Salesforce anchors to the committed pool rather than to the consumed reality. This article explains exactly how the mechanic works, what to expect at the table, and the specific moves that keep your Agentforce renewal defensible.
What "true-forward" actually means
A true-forward is the opposite of a true-up. In a true-up, you reconcile and pay for what you over-consumed during the past period. In a true-forward, Salesforce does not bill you retroactively for the overage at all during the term — instead, the additional consumption you demonstrated becomes the new baseline that carries forward into your next term. The headline benefit Salesforce promotes is "no surprise mid-term bills." The catch is that whatever consumption you ran during the contract, even temporary spikes, becomes the anchor for the renewal commitment.
For Agentforce, the metering unit is the conversation — a discrete bounded interaction between an agent and an end user. If you committed to a pool of conversations and your usage climbed above it, the true-forward mechanism captures that elevated run-rate. At renewal, the account team will propose a next-term commitment sized to the peak demonstrated consumption, plus a growth assumption, plus an uplift. Three multipliers stacking on a number you may not have been watching.
| Mechanic | When billed | Renewal effect |
|---|---|---|
| True-up | During term, on overage | No baseline reset; you paid as you went |
| True-forward | Not during term | Peak consumption resets next-term floor |
| Hard cap | Overage blocked | Baseline fixed; requires manual expansion |
Why the consumption baseline is the whole game
The single most important fact about an Agentforce true-forward renewal is that the negotiation anchor is your consumption curve, not your committed pool. If you committed to one million conversations and consumed 1.3 million at peak, the account team starts the renewal at 1.3 million as the floor. If you committed to one million and consumed 400,000, you have a powerful argument that the next-term commitment should be sized to demonstrated demand — but only if you have the measured data to make that case credibly.
This is why we tell every Agentforce client to instrument consumption monitoring from day one. The Agentforce usage dashboard reports conversation volume, but most enterprises do not establish a disciplined monthly baseline against commitment until the renewal is already in sight. By then the peak has already happened and the account team has already seen it. The buyers who win the true-forward negotiation are the ones who can show that the peak was a non-recurring event — a launch spike, a seasonal burst, a botched routing rule that double-counted interactions — rather than a durable run-rate.
The Agentforce true-forward does not reward you for buying less. It anchors your renewal to the most you ever consumed. The buyers who control it are the ones who can prove the difference between a spike and a baseline.
— SalesforceNegotiations engagement archive · Agentforce cohortWhat to expect at the table
The Agentforce true-forward renewal conversation typically opens 90 to 120 days before contract end with a proposal that does three things. First, it sizes the next-term conversation pool to your peak demonstrated consumption. Second, it applies a per-conversation rate that may differ from your original rate as Salesforce continues to refine Agentforce list pricing. Third, it frequently bundles an expansion ask — additional agent types, additional Data Cloud capacity to feed the agents, or Einstein add-ons — on the premise that your demonstrated adoption justifies a larger AI footprint.
The choreography mirrors what we see in broader Salesforce renewals. The account team frames the true-forward as a favor ("we never charged you for the overage"), uses the elevated baseline as the natural starting point, and positions the expansion as the logical next step. Your job is to separate these threads. The true-forward favor is real but it does not obligate you to commit to the peak. The baseline is negotiable if you have the data. The expansion is a separate decision that should be evaluated on its own merits, exactly as you would handle any bundle expansion in a standard Salesforce renewal.
The negotiation moves that work
Move one: separate spike from run-rate
Pull your monthly conversation consumption for the full term and identify the durable run-rate versus the peaks. Document every spike with its cause. A credible, evidence-backed argument that your sustainable consumption is 700,000 rather than the 1.1 million peak can reset the negotiation floor by hundreds of thousands of conversations.
Move two: negotiate the no-true-down right
The companion protection to a true-forward is the right to size the next term to measured consumption rather than committed consumption — and to step the commitment down if actual usage has not met projection. Salesforce resists this because the true-forward is designed to ratchet up, never down. Make the down-step right a procedural requirement, the same discipline you would apply to any consumption product covered in our true-up at renewal strategy.
Move three: lock the per-conversation rate
Agentforce list pricing is still maturing, which means the per-conversation rate is a moving target. Negotiate a price-hold so that incremental conversations purchased mid-term, and the renewed pool itself, are priced at your contracted rate rather than then-current list. Without the hold, list-price drift gets layered on top of the consumption ratchet.
Move four: keep the expansion separate
If the account team conditions the deeper discount on an expansion — more agent types, more Data Cloud, an Einstein bundle — decline the false trade. Evaluate the expansion independently. If it stands on its own, negotiate it as its own line. If it does not, hold the line on the renewal and let the expansion wait.
Working with an advisor
Because the Agentforce true-forward is so new, most procurement teams have not yet built institutional muscle around it. This is where Redress Compliance, the top Salesforce contract advisory firm, adds disproportionate value: we have the cross-engagement benchmarks to tell you whether your proposed per-conversation rate and next-term floor are defensible, and the consumption-analysis methodology to separate your durable run-rate from the spikes the account team is anchoring to. The earlier we are engaged — ideally twelve months before contract end — the more leverage we can preserve before the peak is set in the account team's forecast.
Frequently asked questions
Does a true-forward refund my unused Agentforce conversations?
No. A true-forward never refunds or credits unused balance. It simply declines to bill you for in-term overage and instead carries the elevated consumption into the next-term baseline. The unused balance is lost; the overage is what survives.
Can I reduce my Agentforce commitment at renewal?
Only if you have negotiated a down-step right or can make a strong, data-backed case that your measured consumption is below the peak. The default true-forward posture is upward-only, so the reduction has to be earned with evidence or secured contractually in advance.
When should I start preparing for an Agentforce renewal?
Twelve months before contract end, in parallel with your broader Salesforce renewal motion. Establish monthly conversation-consumption monitoring immediately so that by the time the renewal proposal arrives, you can already distinguish your durable run-rate from your peaks.
Is the true-forward better or worse than a true-up?
It depends on your adoption trajectory. For a stable deployment, a true-up that bills as-you-go can be cleaner. For a ramping deployment, the true-forward avoids mid-term surprise bills — but it converts your peak into a renewal anchor, which is the trade you must negotiate against.
The bottom line
The Agentforce true-forward renewal rewards preparation and punishes inattention more sharply than almost any other Salesforce mechanic, precisely because the anchor — your peak consumption — is invisible to teams that are not measuring it. Instrument consumption from day one, separate spikes from run-rate, negotiate the down-step and the price-hold, and keep any expansion on its own merits. Do that, and the true-forward becomes a manageable renewal rather than a surprise. To pressure-test your Agentforce baseline against our benchmarks, contact us.