Agentforce prices per action, drawn from a shared pool of Flex Credits. Credits list at $500 per 100,000, which is $0.005 each, and a standard or custom production action costs 20 of them. The full card, including voice and Data 360, is in our Flex Credits rate card guide, and the mechanics of the model are in the general Agentforce pricing guide.
This page is the version of that question for B2B SaaS specifically, because support volume in a seat-based business behaves differently from support volume anywhere else, and because the data an agent needs to answer a B2B SaaS question is usually not in Salesforce.
What sets the bill, and the rate card is not on the list
Four things decide what you pay. They compound in order, so a conservative estimate on the first can still produce a bill several times larger than forecast once the other three land.
What sets the bill
Four drivers, in the order they compound
The rate card is not on this list
- 01Sets the ceiling
Ticket mix
Which contacts can an agent actually close?
Password resets and billing lookups close on their own. Integration failures and anything needing a judgement call do not. Your mix sets the ceiling on everything below.
- 02Multiplies actions
Grounding hops
How many systems does it read before it can answer?
An answer that lives in Salesforce is one read. An answer that needs product usage, entitlement, and billing state is four, and each hop is billable work.
- 03Multiplies actions
Action fan-out
How many paid actions does one resolved conversation take?
The same resolved request costs three actions or eight depending on how the agent is designed. This is the number you control most directly after launch.
- 04Pays twice
Fallback rate
What share still reaches a person?
A conversation the agent attempts and hands off bills for the attempt and still costs a human to finish. High fallback is the one driver that makes the bill worse than doing nothing.
Ticket mix is the only one that is a fact about your business rather than a decision. It is also the one most teams skip: they estimate deflection from a vendor benchmark instead of sorting a month of their own tickets into what an agent could close end to end and what needs a person. That sort takes about an hour with a ticket export and it is the difference between a forecast and a guess.
What it costs at your support volume
The monthly number reads as small at every volume. The annual number is the one that goes to procurement, so both belong in the same view before anyone signs.
Same design, three volumes
What the agent bills a month, and a year
40% closed · 5 actions each
The important property here is the one that is easy to miss: cost per resolved conversation does not fall as you scale. There is no volume break in the meter. A support desk that triples its contacts triples its agent bill unless the design gets tighter over the same period, which does not happen on its own.
Why B2B SaaS pays more per answer
In most industries the record an agent needs is already in the CRM, or the integration to fetch it is planned before launch because everyone knows it is needed. Behavioral health teams plan the EHR connection. Financial services teams plan the core banking connection.
B2B SaaS is the case where the gap is invisible until the agent is live. The questions customers actually ask are about seat usage, API limits, feature entitlement and error state, and none of that lives in Salesforce. It lives in the product database or the warehouse.
Where the answer lives
Same question, two costs
$0.10 per action at list
Answer lives in Salesforce
Invoice status, open case history, renewal date
3 billable actions
$0.30per answer
Answer lives in the product
Seat usage, API limits, feature entitlement, error logs
7 billable actions
$0.70per answer
This is why a deflection estimate borrowed from another industry misleads here. The contact types are similar, the answer paths are not, and the difference lands on every conversation for as long as the agent runs. It is also the part worth designing deliberately: a well-shaped retrieval layer that fetches product state once and reuses it costs a fraction of an agent that re-reads the same systems on each turn.
Agentforce consultation
Get your support volume priced before you commit to a build.
Is Agentforce expensive for a B2B SaaS company?
The honest answer is that the bill is knowable and the return is not, and anyone quoting you both with equal confidence is quoting one of them from a template.
The only number we cannot calculate for you
What the bill has to displace
We can price this
$2,000
Monthly bill at list
We can price this
$0.50
Per resolved conversation
Only you can price this
?
Your cost to handle one now
We can price the meter to the cent, because it is published arithmetic. What we cannot price is what a resolved contact costs you today, and that is the number that decides whether this is cheap. Companies that already run a lean, well-tooled support desk often find the agent has to justify itself on coverage, on nights and weekends, or on time to first response, rather than on cost per contact. That is a legitimate case. It is just a different one, and it should be made before the build rather than discovered during the renewal.
When it does not pay
Four situations where we would tell you to wait, and have:
- Your ticket mix is mostly judgement calls. If the contacts an agent could close end to end are a small share of the queue, the ceiling is low no matter how good the build is.
- The answers live in systems with no reliable read path. An agent that cannot fetch product state gives confident wrong answers, which costs more than the meter ever will.
- Fallback would run high. A conversation the agent attempts and hands off bills for the attempt and still costs a person to finish. Above a certain handoff rate the agent makes the economics worse, not better.
- Nobody owns the evaluation. Without someone measuring resolution quality weekly, action fan-out drifts upward and the bill follows it quietly.
In two of those four, a governed assistant that keeps a person in control does the same job for less. We cover that trade in Agentforce versus off-platform agents.
Price your own volume
Send us your monthly support contact count and where the answers live, and we will come back with a priced range and the assumptions behind it. If the arithmetic says wait, we will say so. You can also run the numbers yourself in the Flex Credit calculator.
Questions B2B SaaS teams ask about Agentforce pricing
- How much does Agentforce cost for a B2B SaaS company?
- At 10,000 support contacts a month, an agent closing 40 percent of them at five billable actions each costs about $2,000 a month at list price. The arithmetic is 4,000 resolved conversations times five actions times $0.10 an action. Your number moves with three things you control and one you do not.
- Is Agentforce expensive for B2B SaaS?
- It depends entirely on what a resolved contact costs you today. At five actions a conversation the agent bills about $0.50 to resolve one. If your current cost to handle that same contact is higher, the meter is cheap. If it is lower, the agent has to win on speed or coverage instead, which is a real reason to buy but a different business case. We can price the bill exactly; only you can price the thing it displaces.
- How much does Agentforce cost per month?
- There is no monthly seat price to quote, because Agentforce meters per action rather than per user. The monthly bill is your resolved conversation volume times the actions each one takes times $0.10. That is why two companies with identical headcount can be a factor of three apart on the same product.
- Why does a B2B SaaS agent cost more per answer than other industries?
- Because the answer usually lives in the product, not in Salesforce. Seat usage, API limits, feature entitlement and error logs sit in the product database or the warehouse. Every system the agent reads before it can answer is billable work, so an answer that takes one read in Salesforce can take four when it needs product state.
- Does Agentforce replace support headcount?
- Not on the evidence we have seen. It changes which contacts reach a person. The contacts an agent closes cleanly are the ones that were cheapest to handle already, so the remaining queue gets harder on average even as it gets shorter. Plan for a team handling fewer, more complex contacts rather than a smaller team doing the same work.
- What is the fastest way to get a number for our own volume?
- Count last month's support contacts, then sort them into contacts an agent could close end to end and contacts that need a person. Multiply the first group by five actions and $0.10. That is your ceiling before any design work, and it takes about an hour with a ticket export.