Salesforce Flex Credits: price, consumption and what they buy

By Giorgio Bonan. Updated October 21, 2026, published October 21, 2026.

Salesforce Flex Credits are the pay-per-action currency of Agentforce: $500 buys 100,000 credits at list price, a standard agent action draws 20 credits ($0.10) and a voice action 30 ($0.15). Sales Cloud Core, Advanced and Max include 500,000, 1 million and 2.75 million credits per org per year.

How Flex Credits work

You buy a pool. Each action an agent takes draws credits from it, wherever it runs: customer-facing agents, employee agents, Agentforce Voice, Agentforce Vibes. The pool is shared across teams, channels and use cases, and each action is metered individually. Consumption shows up in the Digital Wallet.

The alternative models are a $2 price per conversation for customer-facing agents, or a flat $125 per user per month for unmetered employee use. The full price list and a cost estimator are on the Agentforce pricing page.

Conversion table

What your edition includes, per rep

Credits included in Sales Cloud editions are per org per year, not per user. Translated into standard actions per rep per working day (21 days a month):

Formula: yearly credits / 12 / 20 credits per action / reps / 21 days. A 25-rep team on Core that lets every rep run four agent actions a day uses its whole yearly allowance; beyond that, it buys credits.

What consumes credits, and when

The second column comes from Salesforce Help's "Understand AIforce Impact" article of 17 September 2026, summarized by Cloud Odyssey. It matters for any team connecting Claude, ChatGPT or custom agents through Salesforce MCP: today those calls draw on the API allocation, and later they will also draw credits. The layer concerned is the one first called Headless 360.

Flex Credits, conversations or per-user: which is cheaper

At list price, a standard action costs $0.10 in Flex Credits. Three break-even points follow from the published prices:

Most sales use (a morning brief, a few lookups, a CRM update after each meeting) sits well below 60 actions per seller per day. Customer-facing agents that take many small steps per conversation can exceed 20 actions per conversation.

Three example budgets

Formula: sellers x actions per day x 21 working days x 20 credits; cost = credits x $0.005. Included credits are the yearly allowance divided by 12.

Questions for your account executive

1. Do credits included in our edition roll over, and do they expire?
2. Are purchased credits pooled with included credits, and which are drawn first?
3. How many credits does each of the agent actions we plan to use draw?
4. Will calls from registered agents through MCP be billed from the same pool, and at what rate?
5. What alerts can the Digital Wallet send before the pool runs out?
6. What happens when the pool is empty: throttling, overage billing or a stop?

How to keep consumption predictable

1. Name an owner for the Digital Wallet. Someone reads it weekly, by product and use case.
2. Start with read-only agents. Summaries and lookups are cheaper to reason about than chains of updates.
3. Pilot on one team for a month. Divide the credits drawn by active users and working days: that is your real cost per rep per day, the number to plug into the estimator.
4. Compare with the flat add-on. Above about 60 actions per rep per working day, the $125 per-user add-on is cheaper at list price.
5. Register agents early. When metering of agent calls starts, unregistered agents will need to be registered within the window Salesforce announces.

A weekly Digital Wallet routine

Ten minutes a week is enough. Without it, the first signal is the invoice.

Reading one month of consumption

An example month for a 25-seller team, as it could appear when grouped by use case:

What to conclude: the CRM-update agent consumes most; it is worth checking that its updates are accepted, or it is spending credits on changes people revert. The total, 156,000 credits a month, is almost twice an Advanced edition's included allowance of about 83,333 per month.

Common surprises

• Included credits are per org, not per user. A 50-rep team on Core shares 500,000 credits a year, about two standard actions per rep per working day.
• Multi-step agents draw per action. One request that triggers five actions draws five times.
• Voice costs more. A voice action draws 30 credits instead of 20.
• Agent calls from outside Salesforce are coming. Once metering of registered agents starts, calls through MCP and APIs will also draw credits.

Prices change: check the date

Every figure on this page was read on Salesforce's pricing pages on 21 October 2026. Salesforce notes that pricing and packaging are subject to change, and the rates for agent calls are still to be announced. Check the date at the top of this page before using a number in a budget.

Who should own Flex Credits

In most orgs the Salesforce admin sees the Digital Wallet and finance sees the invoice, and nobody sees both. Name one owner, usually in RevOps, who reads consumption weekly, approves new agents, and reports cost per active user each month. That single role prevents most surprises.

Planning next year's credit budget

1. Take three months of Digital Wallet data, by use case.
2. Divide by active users and working days to get credits per user per day for each use case.
3. Multiply by the users planned next year, use case by use case.
4. Subtract the credits included in your edition.
5. Compare the result with the per-user add-on for your heaviest users, and buy credits for the rest.

Flex Credits and Data 360 credits are different

Salesforce's Sales Cloud pricing mentions both Flex Credits and Data 360 credits as limited inclusions in some editions. They are separate currencies: Flex Credits pay for agent actions, Data 360 credits pay for data processing in Data 360. Running out of one does not draw on the other. When an agent reads data unified in Data 360, ask your account executive which of the two the operation consumes.

Glossary

What Flex Credits do not cover

Flex Credits pay Salesforce. They do not cover the AI vendor on the other side of an MCP connection: Claude usage is billed by Anthropic, ChatGPT usage by OpenAI. A seller using Salesforce from Claude therefore draws on two meters, as explained in our Claudeforce guide.