Insights 24 September 2026·SaaSed Team

How Salesforce Flex Credits Work - and Where They Cost You

Agentforce Flex Credits are Salesforce's consumption currency for Agentforce actions, and they can make AI spend easier to start but harder to forecast. The commercial risk is not the headline rate, but whether the credit model is tied to real action volumes, governance and renewal flexibility.

Salesforce introduced Flex Credits in May 2025 as part of a broader move towards more flexible Agentforce pricing, alongside the existing conversation-based model. In plain terms, a customer buys a pool of credits, then Salesforce deducts credits when Agentforce performs defined actions.

For buyers, Agentforce Flex Credits matter because they can appear late in a renewal conversation, often attached to a wider AI proposal. By that point, the commercial frame may already be set, which makes it harder to test whether the proposed credit volume matches actual use.

The mechanism is not difficult. The difficulty is knowing what your organisation will consume, which teams will drive that usage and what happens when the first usage pattern is wrong.

How Flex Credits Work

Salesforce's public framing is that Flex Credits give customers a way to pay for Agentforce usage by action rather than by conversation. Salesforce announced the model in its May 2025 Agentforce flexible pricing announcement, positioning it as a way to match spend more closely to AI activity.

The base commercial mechanic is currently simple: $500 buys 100,000 Flex Credits. A standard Agentforce action consumes 20 credits, which equates to $0.10 per action. A voice action consumes 30 credits, which equates to $0.15 per action.

Actions are the work Agentforce performs inside Salesforce. Examples include updating records, automating workflows, resolving cases or completing a task triggered by a user or process. The definition matters because small differences in how actions are counted can change the bill materially when usage scales across service, sales or operations teams.

This differs from the older $2-per-conversation model, which Salesforce still keeps live in parallel. Under that approach, the commercial unit is the conversation rather than the underlying actions taken during it. The key constraint is that Flex Credits and Conversations cannot be used in the same Salesforce org at the same time, so this is not simply a toggle finance can adjust after the fact.

Agentforce Flex Credits in practice

Before using these figures in a business case, confirm them against Salesforce's current official Agentforce pricing page. Rate cards change, packaging changes and contract terms can alter how published pricing translates into your actual renewal proposal.

The buying route also matters. The same unit price can behave very differently depending on whether you pre-purchase credits, pre-commit to a level of spend or pay as you go.

Buying Model	How It Works	What to Watch For
Pre-Purchase	You buy a fixed pool of credits up front for expected Agentforce usage.	Forecasting error sits with you, especially if usage is lower than expected or concentrated in a few workflows.
Pre-Commit	You commit to a consumption level over a defined period, often as part of a wider Salesforce agreement.	Minimum commitments can become hard to unwind once bundled into a renewal.
PayGo	You consume credits as usage happens, with billing tied more directly to activity.	Budget control depends on monitoring, alerts and agreed commercial guardrails.

Flex Credits pricing can look tidy in a spreadsheet. It becomes less tidy when a process that looked like one business outcome consumes multiple actions, or when an automation becomes popular faster than expected.

Where Flex Credits Create Budget Risk

The danger with Agentforce Flex Credits is not that consumption pricing is inherently bad. The risk is buying the model before you have enough evidence about your own usage pattern.

Forecasting is the first problem. Agentforce may start with a controlled pilot, then spread into adjacent workflows once teams see what it can do. A service team resolving cases, a sales team updating opportunities and an operations team automating follow-ups may all draw from the same commercial pool, but with very different consumption profiles.

Unused credits are the second issue. Under standard terms, unused Flex Credits do not typically roll over. If you overestimate consumption, you may have paid for capacity that expires unused. If you underestimate consumption, you may be negotiating add-on capacity from a weaker position, especially if the workflow has already become business-critical.

Bundling creates the third risk. When Flex Credits are folded into a larger renewal, the true cost-per-outcome can become hard to see. A discount on one SKU may mask a commitment on another. A credit pool may look modest next to the full contract value, but still change the cost base if the use case expands.

For a broader view of how these mechanics interact with tokens, Data Cloud and contract structure, SaaSed's breakdown of how Flex Credits and tokens can affect your Agentforce bill covers the surrounding cost stack.

Risk Area	Why It Matters	The Question to Ask Salesforce
Consumption forecasting	Early estimates are often based on assumed workflows rather than observed usage.	Which specific actions are included in your forecast, and what evidence supports the volume?
No standard rollover	Unused credits can become wasted budget at the end of the term.	Can unused credits roll over, convert or be exchanged if adoption is slower than expected?
Renewal bundling	Credits can be hidden inside a wider commercial package.	What is the standalone price, discount and commitment for Flex Credits separate from the wider renewal?
Org-level model choice	Flex Credits and Conversations cannot run in the same org simultaneously.	What would it take commercially and operationally to change model later?

The buyer's job is not to reject the model. It is to stop the model from becoming vague at the exact point where precision matters.

What to Negotiate Before You Buy Flex Credits

Before buying Agentforce Flex Credits, ask Salesforce to show concrete action-volume examples for your proposed use cases. Not a generic demo. Not a broad estimate. You want examples that show the likely number of standard actions, voice actions and related platform consumption for each workflow you are being asked to fund.

Start with the use cases that have budget ownership. If service wants case resolution, ask what a resolved case consumes in credits across low, medium and high complexity scenarios. If sales wants account research or CRM updates, ask how many actions sit behind that outcome. This lets finance and IT compare spend against business value, not just activity.

Next, negotiate flexibility. Rollover rights are worth asking for, even if Salesforce's standard position is restrictive. If rollover is not available, ask whether unused credits can be exchanged for other Salesforce capacity, moved to another approved use case or handled through a mid-term adjustment. The answer may be no, but the discussion reveals how much room exists before signature.

Avoid locked-in minimum commitments until usage patterns are proven. A short pilot or controlled initial pool can give you better evidence than a polished forecast. SaaSed has written separately about controlling Agentforce pricing before you sign, and the same principle applies here: commercial control is much easier before the product is embedded.

Build a review checkpoint into the agreement. That checkpoint should happen before renewal pressure returns, not in the final month. It should cover consumed credits, unused credits, action mix, adoption by team, outcome achieved and whether the chosen pricing model still fits.

Common Mistakes Companies Make with Flex Credits

The first mistake is buying a large credit pack before piloting real usage. A theoretical workflow rarely behaves like a live one. Users ask different questions, automations trigger more often than expected and exceptions create extra actions.

The second mistake is treating Flex Credits like a fixed subscription. Agentforce Flex Credits are consumption units, so governance matters. If no one monitors usage by workflow, team and outcome, finance may only understand the pattern after the spend has already happened.

The third mistake is failing to separate commercial value from technical excitement. A workflow can be impressive and still be expensive relative to the outcome it produces. The cost-per-action is only useful when it can be connected to cost-per-case, cost-per-opportunity update or cost-per-completed process.

The fourth mistake is letting ownership blur. If procurement negotiates the pool, IT enables it and business teams consume it, someone still needs to own the monthly review. Without that owner, credit burn becomes a shared problem with no clear decision-maker.

Frequently Asked Questions

What are Salesforce Agentforce Flex Credits? Salesforce Agentforce Flex Credits are prepaid or committed consumption units used to pay for Agentforce actions. Actions can include tasks such as updating records, automating workflows or resolving cases inside Salesforce.

How much do Flex Credits cost? Salesforce's published pricing currently states $500 for 100,000 Flex Credits, with standard actions consuming 20 credits and voice actions consuming 30 credits. That equates to $0.10 for a standard action and $0.15 for a voice action, but buyers should confirm current pricing directly with Salesforce before signing.

Do unused Flex Credits roll over? Under standard terms, unused Flex Credits generally do not roll over. If your adoption timeline is uncertain, rollover, exchange rights or a smaller initial commitment should be discussed before the order form is signed.

Can we switch between Flex Credits and Conversations pricing? Salesforce keeps both models live, but Flex Credits and Conversations cannot be used in the same Salesforce org simultaneously. If you may need to change model later, ask Salesforce to document the operational process, commercial impact and timing before you commit.

Should we pilot Agentforce before committing to a large Flex Credit purchase? Yes, in most enterprise environments a pilot is the cleaner way to understand consumption. It gives finance, IT and procurement evidence about action volumes, adoption patterns and governance needs before a larger commitment is added to the renewal.

Agentforce can be commercially sensible, but only if the buying model is understood before it becomes part of the renewal architecture. At SaaSed, we see a familiar pattern: 8 out of 10 companies already overpay for SaaS without realising it, and consumption-based AI can make that harder to spot. If Agentforce is entering your renewal conversation, book a complimentary Salesforce audit conversation before the numbers settle into the contract.

Quiet second opinion before you commit: Contact Us