- Salesforce Managed Services
Agentforce costs $500 per 100,000 Flex Credits, which prices a standard agent action at $0.10 and a Voice action at $0.15. That’s the meter. The bill is bigger, because your edition licences, Data 360 processing, implementation and running costs all sit on top of it.
Salesforce sells Agentforce several different ways, and the September 3, 2026 edition change added another variable on top. You can pay per action, per conversation, per user, per resolution, or through credits already bundled into the Salesforce edition you own.
Each meter answers a different question. None of them answers the one your finance team asks, which is what the whole thing will draw from the budget next year.
The headline rate is one input. A usable Agentforce cost estimate also carries your Salesforce edition charges, agent access, consumption above your included credits, Data 360 processing, implementation, integrations, data preparation, testing, training, and whoever owns the system after launch.
Most pricing guides stop at the first line and leave you to guess at the rest. We wrote this one at VALiNTRY360 to show the arithmetic behind every layer. Every figure below comes from Salesforce’s published rates, every calculation shows its inputs, and you can rerun all of it against your own volumes.
How Much Does Agentforce Cost in 2026?
Here is what Salesforce publishes today.
Item | Public list rate |
Salesforce Foundations | $0 starting entitlement for eligible customers |
Flex Credits | $500 per 100,000 credits |
Standard or custom action | 20 credits |
Voice action | 30 credits |
Conversations | $2 per conversation |
Agentforce User License | $5/user/month, requires Flex Credits |
The credit price does the work here. Divide $500 by 100,000 and a single Flex Credit carries a public list rate of $0.005.
A standard action at 20 credits works out to $0.10. A Voice action at 30 credits works out to $0.15. Salesforce states the per-action figure directly on its Agentforce pricing page.
The Conversations meter counts sessions instead of work. A customer session bills at $2 whether the agent answers one question or twenty, so short interactions subsidize long ones and the unit price tells you nothing about the effort behind it.
Two cautions before you build anything on those numbers. They are public list rates, and your contracted rate can differ once volume and contract term enter the negotiation. They also cover the agent’s activity only, so they say nothing about the data work sitting underneath it.
Scale is what turns a small unit price into a large invoice. At $0.10 an action, 10,000 actions a month costs $1,000 and looks trivial. Run the same rate across a busy contact center and the Agentforce cost climbs into six figures a year on actions alone.
Then the Data 360 processing your agent triggers draws from the same credit pool at completely different multipliers. An estimate built on actions alone can miss most of the bill.
If what you actually need is a comparison of the buying models rather than a total, our guide to Salesforce Agentforce pricing models and cost math covers that question in full. This page is about what the whole thing costs.
What Makes Up the Total Agentforce Cost?
Six layers, in the order finance should stack them.
- The Salesforce base edition sets the floor. Core, Advanced, or Max at a per-user monthly rate, and it exists whether or not you ever deploy an agent.
- Agentforce access comes next, as a per-user charge, a consumption meter, or both. Customer-facing and employee-facing agents price on completely different logic.
- Included credits get subtracted before anything else. Your edition and any Data 360 SKU may bundle Agentforce Flex Credits that already cover part of the year.
- Data 360 adds an entry SKU or profile charge plus processing consumption. Data 360 pricing varies far more by the activity you run than by the volume you hold.
- Implementation and connected-system work covers discovery, agent build, integrations, data preparation, and testing. Agentforce implementation cost sits here and moves with scope.
- Continuing operating expense funds monitoring, tuning, and the named owner of consumption. Small per month and permanent, which is why year-one models drop it.
Written as one line:
Annual Agentforce total cost of ownership = Salesforce access + incremental Agentforce usage + Data 360 + implementation + integration and data work + continuing operations
Miss any layer and the Agentforce cost you present to your board is a fraction of the real one.
The Eight Ways Salesforce Sells Agentforce
Salesforce runs eight commercial routes today. Six of them carry the volume, and they are not interchangeable.
Model | Billing unit | Budget input | Cost variable to watch |
Flex Credits | Credit | Actions, prompts, and data activity per month | Data 360 draws from the same pool |
Conversations | Conversation | Customer sessions per month | Long sessions cost the same as short ones |
Agentforce User License | $5/user/month plus credits | Licensed employees | Still metered on top of the seat |
Employee add-ons | $125/user/month | Employee headcount | Priced on seats you may not all activate |
Agentforce editions | Per user per month | Users plus included credits | Included credits expire at term end |
Salesforce Foundations | $0 | Pilot volume | Entitlement is small, so it runs out fast |
Agentforce Help Agent | $2 per billable resolution | Resolved cases per month | Now bundled into Advanced and Max editions |
Industry add-ons | $150/user/month | Industry Cloud seats | Unmetered, so shelfware is the risk |
The last two are narrower. Salesforce charges $2 per billable resolution for its Help Agent, where the underlying agent activity isn’t metered separately during the interaction, and industry-specific add-ons list at $150 per user per month. Since the September 3 announcement, the Help Agent is included in the Advanced and Max editions rather than sold only as a standalone route.
Each of those is a different billing object. Comparing a $2 conversation with a $2 resolution with a $0.10 action tells you nothing until you know how many of each your workload generates.
Foundations is worth sizing before you treat it as a free trial. Salesforce Help confirms that Enterprise Edition customers and above get 100,000 Flex Credits at no charge, which converts to 5,000 standard actions. A pilot handling 500 requests a month at 3 actions each exhausts that entitlement in roughly 3 months, so the free tier proves the design rather than funding the Agentforce cost of a live deployment.
Flex Credits carry the widest scope, because one pool funds actions, prompts, Voice, and data processing together. That scope is also the risk, since a single pool makes it harder to see which activity is driving spend.
The split that matters most is who the agent serves. Customer-facing agents scale with interaction volume, so consumption meters fit them. Employee-facing agents scale with headcount, so seat pricing usually reads better on a spreadsheet.
Two commercial rules constrain the choice. Salesforce confirms that Flex Credits and Conversations won’t be supported in the same org, so you pick one.
And of the three buying models, PayGo and Pre-Commit apply to Flex Credits only, while Pre-Purchase covers the rest. Pre-Commit is still rolling out.
Modelling before signing is what protects the number, which is why our Salesforce consulting services team maps agent design to a commercial model before a quote reaches procurement. Salesforce’s own Agentforce Flex Credit calculator is useful for a first-year sketch, though it excludes several layers you still have to fund.
How the New Core, Advanced and Max Editions Change Your Agentforce Cost
On September 3, 2026, Salesforce replaced its edition lineup. Each new edition bundles credits at the org level.
Core, $195 per user per month. Billed annually, with 500,000 Flex Credits per org per year. This is the entry point for a first agent deployment.
Advanced, $395 per user per month. Billed annually, with 1,000,000 Flex Credits per org per year. Double the entitlement of Core for roughly double the seat price.
Max, $550 per user per month. Billed annually, with 2,750,000 Flex Credits per org per year. Salesforce’s September 3 announcement holds Max at the old price.
Three limits on that change are worth knowing before you apply it to your own budget. It covers Agentforce Sales, Agentforce Service and Agentforce Industries. Data 360 pricing is untouched. And existing Agentforce 1 customers can move to Max without paying more, which means both packagings are live at the same time for different groups of customers.
Divide by the 20-credit standard action multiplier and those allowances convert to 25,000, 50,000, and 137,500 standard actions. Read those as arithmetic. Flex Credits also fund prompts, Voice, and every Data 360 activity your agents trigger, so the real number of actions you get is lower.
Test the allowance against a workload before it reassures anyone. A service operation handling 500,000 cases a year at 3 actions each consumes 30,000,000 credits. Max’s 2,750,000 included credits covers about 9% of that year.
Hold that 9% next to the 8% figure in the Forrester case study further down. They answer the same question against 30,000,000 forecast credits and 33,000,000 actual ones, so read them as one finding rather than two. Included credits cover somewhere under a tenth of a busy service year.
The budgeting sequence follows from there. Forecast annual consumption, identify your included entitlement, subtract it, then price only the remainder.
Most cost guides skip the middle two steps and multiply every forecast action by $0.10. That inflates the Agentforce cost for any customer already sitting on a current edition, and it can inflate it badly.
One live inconsistency runs through this transition. The general Agentforce pricing page still displays the older Agentforce 1 Edition packaging at $550 per user per month with 2,500,000 credits, alongside the new Max at $550 with 2,750,000. Both pages are live. That’s not an error on Salesforce’s part. Both packagings are genuinely in market, because existing customers stay on their current edition until they choose to move.
Check which packaging your contract actually references before you blend the two, because that single number changes the entire estimate. Our Agentforce AI consulting practice at VALiNTRY360 reads the current entitlement before any forecast gets built.
How Flex Credits Turn Actions Into Spend
Production multipliers come straight off Salesforce’s current rate card. Standard and custom actions cost 20 credits each. Standard and custom Voice actions cost 30.
Prompts meter separately. Starter and Basic prompts cost 2 credits, Standard prompts 4, and Advanced prompts 16. Salesforce processes prompts in 2,000-token increments and rounds up, so a prompt totalling 6,500 input and output tokens meters as 4 prompts.
One scope note on those prompt multipliers. The rate card applies them to Agentforce 1 Edition customers, Agentforce for Sales, Service and Industries customers, and other products that no longer use Einstein Requests. If your org still meters on Einstein Requests, the prompt lines don’t apply to you.
Voice deployments carry a third set of meters underneath the actions. Speech-to-text bills 150 credits per hour of transcription, text-to-speech bills 6,000 credits per million characters, and translation bills 4,000 credits per million characters. At list rates that is $0.75 an hour, $30 per million characters, and $20 per million characters.
Sandbox rates run below production. A standard action costs 16 credits in a sandbox and a Voice action costs 24, so development runs at 80% of live rates against the same credit pool. Salesforce applies that sandbox multiplier to pre-production environments generally, which includes scratch orgs as well as sandboxes.
Does an Agentforce Action Have a Token Limit?
No. Every standard action meters as one standard action, whatever the token count. That answer is worth stating plainly, because a lot of published pricing guides say the opposite.
The claim you’ll run into is that a standard action carries a 10,000-token ceiling, and that an action processing 15,000 tokens bills as two actions while one processing 20,001 bills as three. Several widely-shared guides present that as fact and attribute it to Salesforce documentation. One of the pricing guides ranking for this topic today repeats it.
Salesforce’s current billing documentation doesn’t support it. The 2,000-token increment rule is real, and it applies to prompts. Actions meter per action.
The difference is money. If you budget on the token-ceiling version, a document-heavy service agent looks two or three times more expensive than it is, and you may redesign around a constraint that isn’t there. Check the rate card date before you rerun any of this, since Salesforce updates the multipliers periodically, but as of the Flex Credits rate card dated April 21, 2026 there is no per-action token multiplier on the card at all.
Where long context does cost you is Data 360. Pulling a large document into an agent’s context triggers unstructured or intelligent processing, both of which meter per megabyte. That’s covered below, and it’s the real version of the concern the token myth is pointing at.
Running the Numbers
Two formulas cover the estimate.
Monthly action credits = monthly requests × average actions per request × credits per action
List-rate action spend = total credits ÷ 100,000 × $500
Run them on an illustrative volume. Take 5,000 requests a month at 3 standard actions each, which is 15,000 actions or 300,000 credits.
At the public list rate, 300,000 ÷ 100,000 × $500 gives $1,500 a month before any included entitlement is applied. Over a year, 3,600,000 credits at $18,000.
Change one input and watch it move. Raise actions per request from 3 to 5 and the same 5,000 requests consume 6,000,000 credits a year at $30,000. Agent design sets that number long before procurement sees a quote.
One rule decides whether the forecast holds. Unused Flex Credits do not roll into the following subscription term, so buying 12 months of capacity you never use is money gone.
Salesforce publishes every multiplier in its Flex Credits rate card, dated April 21, 2026. For the credit-by-credit mechanics behind these numbers, including how each usage type draws down the pool, see our breakdown of what an Agentforce Flex Credit actually buys.
How Much Does Data 360 Cost for Agentforce?
Data 360 costs either $500 per 100,000 Flex Credits, $240 per 1,000 profiles a year, or nothing at all, depending on which entry route your use case qualifies for. Picking the wrong one is expensive.
Data 360 is the current name for what Salesforce previously called Data Cloud. It has five entry routes.
- Flex Credits: $500 per 100,000 credits, the same rate Agentforce actions draw against.
- Profiles: $240 per 1,000 profiles a year, including 1 Flex Credit per profile.
- Enterprise Profiles: $420 per 1,000 profiles a year, including 2 Flex Credits per profile.
- Data 360 Starter: $60,000 a year, with 10,000,000 Flex Credits and 5TB of storage. This one is quoted in sales conversations and reported widely across the ecosystem, but it isn’t displayed on Salesforce’s public Data 360 pricing page today, so confirm it against your own quote rather than treating it as a published list rate.
- Data 360 Provisioning SKU: $0, with 250,000 Flex Credits and 1TB of storage.
That $0 SKU deserves attention. Salesforce states on its own pricing page that customers can provision Data 360 for free with a limited amount of storage and consumption credits. It exists for customers running Salesforce products that depend on Data 360 functionality without a separate Data 360 use case of their own.
Plenty of Agentforce deployments sit in exactly that position and qualify for the free route. The $60,000 Starter never enters their budget, though several pricing guides still present that SKU as mandatory for every project.
Work the decision in order. Confirm whether the use case needs Data 360 capability, check the entitlement you already hold, choose between Provisioning, Profiles, Starter, or added credits, then forecast processing and storage separately.
Storage sits outside the credit meter and deserves its own line. Provisioning covers 1TB and Starter covers 5TB, with anything above the allowance charged at your contracted rate rather than drawn from Flex Credits. A grounded agent pulling in documents, transcripts, and search indexes grows that footprint faster than a CRM-only deployment does.
Ingestion itself is free under the current model, including batch and zero-copy. Salesforce puts it plainly: bringing data into Data 360 is free, and you pay when you use it. What you pay for is everything downstream: preparing, unifying, querying, segmenting, and activating that data. So Data 360 pricing rewards architectures that move less data and touch it less often.
Starter is worth one piece of arithmetic before you sign it. Its 10,000,000 included credits carry a list value of $50,000, so the $60,000 SKU charges roughly $10,000 for 5TB of storage plus the platform entitlements.
That comparison rarely appears in a Data 360 pricing discussion, and it changes how you negotiate. Our Data 360 solutions team at VALiNTRY360 sizes this layer against the agent design instead of a generic profile count.
Which Data 360 Workloads Consume the Most Credits?
Data 360 charges by activity, and the multipliers are nowhere near each other. Here is the complete published set, not the abbreviated version most guides run.
Usage type | Unit | Base production multiplier | Cost at list |
Data 360 Queries | Per 1M rows processed | 3 credits | $0.015 |
Data 360 Prep | Per 1M rows processed | 40 credits | $0.20 |
Data 360 Code Extension | Per compute unit | 40 credits | $0.20 |
Data 360 Segmentation | Per 1M rows processed | 50 credits | $0.25 |
Data 360 Activation | Per 1M rows processed | 60 credits | $0.30 |
Data 360 Zero-Copy Sharing-Out | Per 1M rows shared | 60 credits | $0.30 |
Data 360 Unstructured Processing | Per 1MB processed | 150 credits | $0.75 |
Data 360 Intelligent Processing | Per 1MB processed | 600 credits | $3.00 |
Data 360 Streaming Pipeline | Per 1M rows processed | 3,500 credits | $17.50 |
Data 360 Unification | Per 1M rows processed | 75,000 credits | $375 |
Data 360 Real-Time Pipeline | Per 1M combined events, API and actions | 250,000 credits | $1,250 |
Convert those at the $0.005 list rate and the spread is stark. A million rows of queries costs about $0.015, a million rows of unification about $375, and a million real-time events about $1,250.
Same product, same credit pool, a range of roughly 83,000 to 1.
The middle of the table barely registers. Prep runs about $0.20 per million rows, segmentation about $0.25, and activation about $0.30, so the routine data plumbing behind an agent is close to free at list rates.
Two meters in that table deserve more attention than they usually get. Intelligent Processing at 600 credits per megabyte is the most expensive per-megabyte rate Salesforce publishes, four times the unstructured rate, and it’s the meter an Agentforce Data Library draws on when it does more than plain extraction. A single gigabyte of intelligent processing costs about $3,072 at list. Document-heavy agent designs live or die on that line.
The second is the gap between Streaming Pipeline at 3,500 credits per million rows and Real-Time Pipeline at 250,000 per million combined events. Those are 71 times apart. Treating “streaming” and “real-time” as one expensive category is a common mistake and an expensive one, because it pushes teams away from a meter that costs $17.50 per million rows toward batch designs they didn’t need.
Three mechanics change the result further. Multipliers drop as monthly consumption rises, with tier boundaries at 300,000, 1,500,000, and 12,500,000 credits, applied per usage type. Unification falls from 75,000 credits per million rows at the base tier to 15,000 at the top.
Those tiers reset on the first day of each calendar month, so a spiky workload keeps paying base-tier rates while a steady one earns its way down. Sandbox activity uses flat rates with no tiering at all.
Check which meter you’re on before applying any of this. Orgs that bought credits before February 24, 2026 consume Data Services credits for Data 360, while orgs purchasing or renewing after that date can hold either Data Services or Flex Credits. Salesforce confirms on its Data 360 pricing page that there is no forced migration, so a Data Services customer stays on that model until they choose to swap.
Run a Flex Credit forecast against a Data Services org and every number will be wrong.
For Agentforce cost planning, unification, real-time pipelines, intelligent processing and unstructured processing each need their own forecast, while query volume rarely moves the number. Salesforce’s Data 360 pricing calculator shows what each SKU covers before you start modeling.
What Raises Agentforce Implementation Cost Before Go-Live?
Agentforce implementation cost is driven by scope, not by the agent. Five work packages carry most of it, and each has its own way of growing.
Discovery and use-case definition. Scope driver: how many business processes the agent touches. Estimation input: a documented process map and a defined success measure per use case.
Architecture and agent design. Scope driver: number of agents, topics, and connected data sources. Estimation input: the systems of record each agent must read from and write to.
Configuration and action development. Scope driver: count of custom actions against standard ones. Estimation input: how many actions need new Apex, Flow, or API work behind them.
Testing, security, and permissions. Scope driver: approval controls and the number of distinct user groups. Estimation input: UAT scenario count plus regression scope across existing automation.
Rollout, training, and production preparation. Scope driver: user population and the depth of change. Estimation input: number of roles whose daily work actually changes.
Sandbox consumption belongs in this budget too. Build and test actions draw credits at 16 each, and a thorough test cycle across several agents runs into six figures of credits before a single customer touches the system.
Sequence changes the total as much as scope does. Data preparation that happens after the agent is built gets done twice, once to make the agent work and once to make it right.
What pushes Agentforce implementation cost up is rarely the agent itself. It’s the number of Salesforce clouds in play, the volume of existing automation that regression testing has to cover, and the governance sign-offs between a working agent and a live one.
Scope discipline is what keeps that number defensible. Gartner predicted on June 25, 2025 that over 40% of agentic AI projects would be cancelled by the end of 2027, and named escalating costs, unclear business value and inadequate risk controls as the three causes. Every one of those is a scoping failure rather than a technology failure, which is the argument for spending longer on the first work package than feels comfortable.
We don’t publish a fixed project price at VALiNTRY360, because a two-agent service pilot and a six-agent multi-cloud rollout share almost nothing. Our Salesforce implementation services team scopes against those five packages and prices from the answers. If you want the state of your org assessed before any of that starts, a Salesforce health check is usually the cheaper first step.
Costs That Sit Outside the Agentforce Usage Meter
Six dependencies land on the invoice without appearing in the action calculation. Each gets scoped separately from the agent build.
- CRM and data preparation: agents inherit your data quality, so duplicate accounts, stale contacts, and inconsistent picklists get cleaned before launch or after a customer complains.
- API and connected-system work: every action reaching an ERP, billing platform, or logistics system needs an integration behind it, and our Salesforce integration services practice often finds this layer larger than the agent build.
- Identity, access, and governance: permission sets, field-level security, audit trails, and the review that decides what an agent may do without a human, which runs longest in regulated industries. Our Salesforce data governance services team treats this as a cost control rather than a compliance tax, because an agent with an unbounded action menu is both riskier and more expensive.
- Knowledge and Data Library preparation: the Agentforce Data Library runs on Data 360 and bills queries, intelligent processing, and unstructured data against your active consumption card. At 600 credits per megabyte, intelligent processing is the line that turns a document-heavy knowledge base into a budget problem.
- Test environments and release work: sandbox refreshes, deployment pipelines, and regression against three Salesforce releases a year, which behaves like a subscription rather than a project.
- Training and production ownership: someone reviews transcripts, tunes prompts, and watches consumption every month, so budget a fraction of an FTE for it from day one.
The last one is the easiest to leave unfunded and the most expensive to skip. Without a named owner, the Agentforce implementation cost moves to whoever notices the overage first, usually an admin with a full workload already.
Case Study: What Agentforce Cost a 500,000-Case Service Operation
Every figure above this point is a published list rate or a calculation built on one. Forrester put a different kind of number on the table in November 2025, which is what a service operation at real scale actually paid across three years.
The study is Forrester’s Total Economic Impact of Agentforce for Customer Service, commissioned by Salesforce and built on a composite organization drawn from interviewed customers. That composite is a global company running 50 customer service representatives against 500,000 support cases in year 1, with case volume growing 5% a year.
Here is the cost side, risk-adjusted.
Cost line | Initial | Year 1 | Year 2 | Year 3 | Present value |
Agentforce consumption | $0 | $165,000 | $173,250 | $181,913 | $429,855 |
Implementation and management | $40,496 | $37,663 | $37,663 | $37,663 | $134,158 |
Total | $40,496 | $202,663 | $210,913 | $219,576 | $564,013 |
In nominal terms that is $520,163 of consumption and $153,485 of implementation, training and ongoing management, for $673,648 across the three years.
Run that year 1 consumption back through the credit price and it lands where this page said it would. $165,000 at $0.005 a credit is 33,000,000 credits. At 20 credits a standard action that is 1,650,000 actions spread across 500,000 cases, or 3.3 actions per case, within touching distance of the 3 actions the edition example assumed.
It also settles the entitlement question. Against 33,000,000 credits consumed, the 2,750,000 that Max includes covers 8% of year 1.
Three ratios fall out of that table, and each answers something list rates cannot.
Consumption is 77% of the three-year nominal total. The credit meter is where the money goes, and the human layer accounts for the remaining quarter.
Ongoing management runs $37,663 a year against $165,000 of year 1 consumption. Keeping agents tuned and monitored costs about 23 cents for every dollar of usage, and that is the line year-one models leave out.
Implementation lands at $40,496, all of it in the initial period. That is 25% of year 1 consumption, it repeats in neither year 2 nor year 3, and it belongs in the one-time column.
The per-case view is the one to take into a budget conversation. Across three years the composite handles 1,576,250 cases, so $673,648 of total cost works out to $0.43 a case. Forrester puts the benefit at $3,391,397 over the same period, or $2.15 a case, from case deflection rising from 25% in year 1 to 35% by year 3 and a 50% cut in handling time on escalated cases.
The headline figures follow from those two columns: $2,235,896 in net present value, a 396% return, and payback inside 6 months. Forrester publishes the full model in its Total Economic Impact study.
Two limits before you borrow any of it. Salesforce commissioned the study, and a composite organization is a model assembled from interviews instead of a single named customer. The figures benchmark a customer service workload at that scale, and they say nothing about a sales or employee-facing deployment.
A third limit is worth holding alongside them. Stanford HAI’s AI Index reports that where organisations do see financial impact from AI, the most common cost-savings band is still under 10% in functions including service operations. A 396% return is achievable and it is not the base case, so model your own deflection rate before you borrow anyone’s ROI.
What the table does settle is the shape of the spend. Roughly three quarters consumption and one quarter people, with the people quarter arriving as a one-time build followed by a permanent running cost.
What Agentforce Costs by Organisation Size
Four illustrative profiles at public list rates, so you can find the one closest to your own volume. Every figure assumes 3 standard actions per request and subtracts the edition entitlement before pricing the remainder. Implementation sits outside all four.
Profile | Monthly requests | Annual credits | Edition entitlement | Incremental annual cost at list |
Small team pilot | 1,000 | 720,000 | Core, 500,000 | $1,100 |
Mid-market service desk | 8,000 | 5,760,000 | Advanced, 1,000,000 | $23,800 |
Enterprise contact centre | 40,000 | 28,800,000 | Max, 2,750,000 | $130,250 |
Large-scale service operation | 125,000 | 90,000,000 | Max, 2,750,000 | $436,250 |
Two things to read off that table. The entitlement matters enormously at the pilot end and barely at all at the enterprise end, where included credits cover 3% of the year. And the cost per request stays flat at $0.30 across all four, because list pricing doesn’t tier on Agentforce actions the way Data 360 does. Your contracted rate is where volume earns you a discount, not the rate card.
Recalculate every row against your own actions-per-request figure. At 5 actions instead of 3, each of these numbers rises by roughly two thirds.
Four Worked Agentforce Cost Scenarios
Every card below uses public list rates and the same six fields. Recalculate each one against your own volumes and your contracted rate, because these show the method rather than a quote.
Customer Service Self-Service
- Volume: 8,000 customer requests a month
- Agentforce activity: 3 standard actions per request, 24,000 actions a month
- Credit calculation: 24,000 × 20 = 480,000 credits a month, 5,760,000 a year
- Included entitlement: Advanced edition, 1,000,000 credits a year
- Incremental usage: 4,760,000 credits, or $23,800 a year at list
- Outside this calculation: knowledge preparation, order-system integration, monitoring
Deflection rate moves this number more than any other input. Our Agentforce for Service work starts by measuring which case types an agent can actually close.
Sales Prospecting Agent
- Volume: 20 sales users working 150 prospects each a month, 3,000 prospects
- Agentforce activity: 2 standard actions per prospect, 6,000 actions a month
- Credit calculation: 72,000 actions × 20 = 1,440,000 credits a year
- Included entitlement: Core edition, 500,000 credits a year
- Incremental usage: 940,000 credits, or $4,700 a year, plus $1,200 in user licenses
- Outside this calculation: CRM data quality work, enrichment source integration
Sales agents run lighter than service agents, because a prospect touch needs fewer actions than a case resolution. Our Agentforce for Sales team models this against your pipeline volume.
Employee Knowledge Assistant
- Volume: 300 employees asking 8 questions a month, 2,400 questions
- Agentforce activity: 1 standard action and 2 Standard prompts per question, 28 credits each
- Credit calculation: 806,400 credits a year, plus 768,000 once for a 5GB corpus
- Included entitlement: Advanced edition, 1,000,000 credits a year
- Incremental usage: 574,400 credits in year one, or $2,872 at list
- Outside this calculation: document cleanup, permission mapping, ongoing corpus updates
The corpus is half of year-one consumption and none of the recurring cost. Watch the 2,000-token prompt rounding here, since long answers meter as several prompts. That corpus figure assumes unstructured processing at 150 credits per megabyte. If your Data Library uses intelligent processing instead, the same 5GB costs 3,072,000 credits rather than 768,000, and the scenario changes completely.
Voice Service Agent
- Volume: 4,000 calls a month at a 6-minute average
- Agentforce activity: 4 Voice actions per call, plus speech-to-text on every minute
- Credit calculation: 480,000 Voice and 60,000 transcription credits a month, 6,480,000 a year
- Included entitlement: Max edition, 2,750,000 credits a year
- Incremental usage: 3,730,000 credits, or $18,650 a year at list
- Outside this calculation: telephony, escalation routing, call quality review
Voice runs 50% above text per action, and transcription adds a meter most estimates ignore. Salesforce bills speech-to-text at 150 credits per hour, small per call and material at volume.
Check one thing before you use this scenario. Salesforce’s rate card notes that for certain customers the Agentforce Voice Minutes usage type applies instead of per-action Voice billing. If that’s your contract, the per-action arithmetic above doesn’t describe your bill at all, and you need a per-minute forecast instead.
Across all four, the Agentforce implementation cost sits outside the credit math entirely. None of these figures include building the thing.
How to Build a 12-Month Agentforce TCO Model
Stack the layers, then separate what recurs from what doesn’t.
Cost layer | Type | Estimation input | Annual amount |
Salesforce base licensing | Recurring | Users × edition rate × 12 | Your figure |
Agentforce access | Recurring | Seats × per-user rate, where applicable | Your figure |
Incremental Agentforce consumption | Recurring | (Forecast credits − included entitlement) ÷ 100,000 × contracted rate | Your figure |
Data 360 SKU or profile charges | Recurring | Provisioning, Profiles, or Starter | Your figure |
Data 360 processing | Recurring | Rows and MB by usage type × multiplier | Your figure |
Added storage | Recurring | TB above allowance | Your figure |
Implementation | One-time | Five work packages, scoped | Your figure |
Integration and data work | One-time | Systems connected, records remediated | Your figure |
Training | One-time | Roles affected × hours | Your figure |
Continuing support | Recurring | Monitoring and tuning effort | Your figure |
Forecast the consumption line month by month. A pilot month, a ramp month, a steady month, and a peak month all consume differently, and the Data 360 tier thresholds reset monthly so an annual average hides where you actually land.
Take the service scenario as an illustration of how the rows interact. Its $23,800 of incremental consumption sits on top of Advanced seats, a Data 360 entitlement that may cost nothing, and a one-time build, so the recurring number and the year-one number are never the same figure.
Add a contingency on the consumption row specifically. Actions per request is the input teams get wrong most often, and being 50% out on it moves the Agentforce cost by the same 50%. A 20% contingency on that row alone covers most estimation error.
Keep the one-time rows out of the recurring total. Implementation, integration, and initial training land in year one, and carrying them into your run rate overstates every year after.
Then run one test before you present the model. Compare forecast consumption against your included entitlement as a percentage. A busy service operation can burn 10 to 20 times its edition allowance in a year, which means the included credits cover a rounding error.
Budgeting the Agentforce implementation cost as a separate one-time line keeps the recurring number clean year over year. VALiNTRY360 builds the model that way so a finance team can defend both numbers in a renewal conversation.
Why Work With a Certified Salesforce Partner on Agentforce Cost
We’re a certified Salesforce consulting partner, which means we sit between you and Salesforce with access to the current rate cards, the edition entitlements your contract actually references, and the product roadmap that decides which meters change next quarter. On a consumption product that matters more than it does on a seat licence.
Three things that access buys you.
The entitlement you already hold gets counted first. Most cost estimates published anywhere multiply forecast volume by list rate and stop. We start from your active Digital Wallet cards, your contract date and your edition packaging, because the difference between an Agentforce 1 org and a Max org is 250,000 credits at the same seat price, and the difference between a Data Services org and a Flex Credits org invalidates an entire forecast.
Agent design gets priced before it gets built. Actions per request is the input that moves the total one for one, and it’s set in the architecture rather than the contract. Reviewing the action menu, the retrieval paths and the topic boundaries before development starts is cheaper than discovering the cost after go-live.
The standards work is done once. Permission design, approval gates, audit trails and regression coverage are the difference between an agent that passes a security review and one that gets pulled after its first incident. We build to those standards from the first sprint because retrofitting them is the most expensive form of rework on a Salesforce project.
We don’t compete on rate. We compete on whether the number we give you survives contact with your first invoice.
How to Control Agentforce Spend After Go-Live
Salesforce gives you Digital Wallet to watch consumption in near real time. It reports. It does not enforce.
Salesforce is explicit that Digital Wallet doesn’t block or throttle any service, doesn’t turn off functionality when consumption reaches 100%, and doesn’t prevent users from accessing features. Nothing stops at your entitlement, so alerts and a named owner are the only real controls you have.
A five-step monthly review keeps forecast and actual together.
Credits consumed against forecast. Are we tracking to plan? If consumption runs above 110% of forecast for two months, reforecast the term before the true-up does it for you.
Consumption by agent. Which agent is driving the burn? Compare each agent’s credits against the business volume it handles, then investigate any agent whose cost per interaction sits well above the others.
Consumption by action. Which actions run hottest? Retire or merge actions the agent calls repeatedly for the same outcome, since duplicated retrieval is the most common source of quiet overspend.
Data 360 usage by type. Is unification, real-time processing or intelligent processing climbing? Move batch-tolerant work off real-time pipelines specifically, where the multiplier gap is largest at 250,000 credits per million combined events. Streaming Pipeline is a different meter at 3,500 per million rows, so don’t abandon it by accident while trying to avoid real-time.
Projected term-end balance. Will we finish short or long? Short means overage at your contracted rate billed monthly in arrears, with no penalty attached. Long means unused Flex Credits that expire.
Read the design alongside the invoice. Most Agentforce cost drift traces back to an action the agent calls more often than anyone planned, and a transcript sample finds it faster than a usage report does.
That cadence needs an owner with time for it, which is where our Agentforce Managed Services team at VALiNTRY360 picks it up and tunes agent design against what the consumption data shows.
Which Agentforce Cost Model Fits Your Use Case?
Five situations, five different answers.
If usage is low or uncertain, start with Salesforce Foundations and PayGo. You avoid committing to a volume you can’t yet forecast, and a pilot generates the consumption data every later estimate depends on.
If customer interaction volume is predictable, compare Conversations against Flex Credits using your real action count per session. Dividing $2 by the $0.10 list rate puts the crossover at 20 standard actions per conversation, though prompts, Voice, and Data 360 activity all shift it.
If you’re deploying broadly to employees, compare the $5 user license plus consumption against the $125 employee add-on. The add-on wins once per-user consumption is high enough, and your pilot tells you where that line falls.
If the design leans on Data 360, price both together, because they share one credit pool. An agent that triggers unification or real-time pipelines can cost more in data processing than in agent actions.
If you’re already a Salesforce customer, begin with your current edition, your active Digital Wallet cards, and your contract date. List pricing is where a negotiation starts, and volume and term move it from there.
The buying model changes your cash position as much as your rate. Pre-Purchase takes the money upfront and draws the balance down, PayGo bills only what you use each month, and Pre-Commit sets a baseline billed in arrears. Exceeding any of them carries no penalty, since Salesforce charges overage at your contracted rate.
Match the model to how confident you are in the forecast. An unproven workload belongs on PayGo, where a wrong estimate costs you nothing but the difference, while a measured one earns better rates on a commitment.
Five questions to answer before procurement:
- Which Salesforce edition do we own, and under which packaging?
- Which credits are already included, and when do they expire?
- What will our agents actually do per request, action by action?
- Which Data 360 activities will the design trigger?
- Who owns usage monitoring after launch?
Answer those five and your Agentforce cost stops being a range. You get a number with visible inputs, which is the only kind a finance team signs off on.
What This Looks Like in Practice: VALiNTRY360 Case Studies
Everything above is method. What a method is worth shows up in delivery.
Our Salesforce case studies cover the work behind these numbers: service operations where deflection rates were measured before an agent was scoped rather than assumed afterwards, data layers sized against an actual agent design instead of a generic profile count, and implementations where the governance model was built in the first sprint rather than retrofitted after a security review.
They’re worth reading for the constraints as much as the outcomes. The projects that landed on budget are the ones where actions per request was measured in a pilot before anyone signed a consumption commitment, and that pattern holds across every engagement we’ve run.
If your own AI programme hasn’t reached the scoping stage yet, our AI readiness assessment covers the data, permission and process questions that decide whether an Agentforce forecast is worth building at all.
Your Pre-Purchase Agentforce Cost Checklist
Nine things to confirm before a quote turns into a signature. Each one moves the number.
- Which edition packaging your contract references. Old Agentforce 1 at 2,500,000 credits and new Max at 2,750,000 both list at $550, and both pages are live today.
- Your included entitlement and its expiry date. Credits do not roll over, so an entitlement you cannot consume inside the term is money already spent.
- Your contract date against February 24, 2026. It decides whether Data 360 bills you in Data Services credits or Flex Credits, and the wrong assumption invalidates the whole forecast.
- Actions per request, measured rather than estimated. This is the input teams get wrong most often, and it moves the total one for one.
- Sandbox consumption across the build and test cycle. Development runs at 16 credits an action and draws from the same pool as production.
- Unification, real-time and intelligent processing activity, priced on their own. All three carry multipliers hundreds or thousands of times higher than a query, so a blended rate hides them.
- Flex Credits or Conversations, decided before signing. They cannot run in the same org, and switching later means reopening the contract.
- The buying model against how confident your forecast is. PayGo suits an unproven workload, and Pre-Purchase suits one you have already measured.
- The named owner of monthly consumption review. Nothing stops at your entitlement, so a person has to watch it.
Work that list before procurement and the quote you receive is one you can check rather than one you have to trust.
FAQs About Agentforce Cost and Data 360 Pricing
How much does Agentforce cost in 2026?
Flex Credits list at $500 per 100,000, which prices a standard action at $0.10. What you actually pay depends on your purchase route, monthly usage, credits already included in your edition, and your negotiated contract terms. Pricing checked September 11, 2026.
How much does one Agentforce action cost?
A standard action consumes 20 Flex Credits. At the public list rate of $500 per 100,000 credits, that calculates to $0.10 per action. Voice actions consume 30 credits, or $0.15. Sandbox actions cost 16 credits. Contracted rates can differ from published list rates.
Does an Agentforce action have a token limit?
No. Every standard action meters as one standard action regardless of how many tokens it processes. Several published guides claim a 10,000-token ceiling above which one action bills as two or three, and Salesforce’s billing documentation doesn’t support that. The 2,000-token increment rule applies to prompts, not actions.
How much does Agentforce Voice cost?
A Voice action consumes 30 Flex Credits, or $0.15 at the public list rate. Speech-to-text adds 150 credits per hour of transcription, text-to-speech adds 6,000 credits per million characters, and translation adds 4,000 credits per million characters. For some customers an Agentforce Voice Minutes usage type applies instead, so confirm which meter your contract uses.
Is there a free version of Agentforce?
Salesforce Foundations gives eligible Enterprise Edition customers and above 100,000 Flex Credits at no charge, which covers 5,000 standard actions. That is enough to prove a design in a pilot, and it runs out quickly once real traffic arrives.
Which Salesforce edition do you need for Agentforce?
Core, Advanced, and Max all bundle credits, at 500,000, 1,000,000, and 2,750,000 per org per year. The edition sets your included entitlement rather than your capability, so choose it on seat count and expected credit volume together.
Do the new Salesforce editions affect existing customers?
Not automatically. The Core, Advanced and Max editions launched on September 3, 2026 across Agentforce Sales, Agentforce Service and Agentforce Industries. Existing Agentforce 1 customers can move to Max at no extra cost, which is why both packagings appear on Salesforce’s site at the same $550 price with different credit allowances. Data 360 pricing is unaffected by the change.
Are Agentforce Flex Credits included with Salesforce editions?
Yes. As of September 3, 2026, Core includes 500,000 credits per org per year, Advanced includes 1,000,000, and Max includes 2,750,000. Subtract your entitlement before pricing any additional consumption, and remember that unused credits expire at term end.
Do unused Agentforce credits roll over?
No. Salesforce states that unused Flex Credits do not roll into subsequent subscription terms, and they are not refundable. That makes over-purchasing as costly a forecasting error as running short, so size your commitment against measured pilot consumption.
What happens when you run out of Flex Credits?
Nothing stops. Digital Wallet reports consumption without blocking or throttling any service, so usage continues past your entitlement and bills as overage at your contracted rate, monthly in arrears. Salesforce applies no penalty rate, which makes alerts your only real control.
Do sandbox and testing consume Agentforce credits?
Yes. A standard action costs 16 credits in a sandbox against 20 in production, and a Voice action costs 24 against 30. Development runs at 80% of live rates and draws from the same credit pool, so budget for it.
Is Flex Credit pricing cheaper than $2 conversation pricing?
It depends on actions per session. Twenty standard actions equal $2, so lighter sessions favor Flex Credits and heavier ones favor Conversations. Prompts, Voice, and Data 360 activity shift the crossover, and you can only run one model per org.
Does Agentforce require Data 360?
It depends on the capability. Grounding an agent in unified data or using the Agentforce Data Library draws on Data 360. Salesforce provisions a $0 SKU for customers whose Data 360 use is limited to supporting other Salesforce products.
How much does Data 360 cost for Agentforce?
Data 360 pricing runs through several routes: Flex Credits at $500 per 100,000, Profiles at $240 per 1,000 profiles a year, Enterprise Profiles at $420, a Starter SKU quoted around $60,000, and a $0 Provisioning route for qualifying use cases.
Which Data 360 activity costs the most?
Real-time pipelines at 250,000 credits per million combined events, or $1,250 at list. Unification follows at 75,000 credits per million rows. By megabyte, intelligent processing is the most expensive meter Salesforce publishes at 600 credits per MB, four times the unstructured processing rate. Queries at 3 credits per million rows are effectively free by comparison.
What does Agentforce cost per case?
Forrester’s composite service organisation paid $0.43 per case across three years, covering $673,648 of total cost against 1,576,250 cases. That figure includes implementation, management and consumption, and it benchmarks a customer service workload at 500,000 cases a year. Your own number moves with actions per case and deflection rate.