Salesforce Agentforce Pricing 2026: Plans, Flex Credits & Real Cost Explained

Publish date:

• 11th September, 2026

Salesforce Agentforce pricing no longer follows a single licensing model. Depending on how you use your AI agents, you may be billed by actions, conversations, users, or successful outcomes. That flexibility is useful, but it can also make Agentforce costs hard to estimate.

In this guide, we break down the Salesforce Agentforce pricing models for 2026, explain how Flex Credits work, compare the available options, and show practical cost scenarios to help you estimate a realistic Agentforce budget.

Salesforce Agentforce Pricing: Quick Answer

Salesforce Agentforce pricing currently includes several consumption-based and licensing options:

Pricing Option	Starting Price	How You Pay	Best Suited For
Salesforce Foundations	Included with eligible Salesforce editions	Included entitlement	Exploring Agentforce capabilities before wider adoption
Flex Credits	$500 per 100,000 credits	Based on agent actions	Organizations that want usage-based pricing and granular cost control
Conversations	$2 per conversation	Based on customer conversations	Customer-facing AI agents with conversation-based usage
Agentforce User License	From $5/user/month	Per user + applicable consumption	Providing employees access to Agentforce
Agentforce Add-ons	From $125/user/month	Per user	Teams using Agentforce extensively within specific Salesforce products
Industry Add-ons	From $150/user/month	Per user	Industry-specific Agentforce deployments
Agentforce 1 Editions	From $550/user/month	Bundled per-user pricing	Organizations looking for a broader Salesforce + Agentforce package
Agentforce Help Agent	$2 per resolution	Successful resolution	Support use cases where businesses want costs tied to resolved issues

What This Means for Your Budget

The advertised price is only the starting point. Your actual Agentforce cost depends on factors such as:

• how many actions an agent performs,

• the volume of conversations or resolutions,

• the licensing model you select,

• Data 360 consumption required by your use case,

• integrations and custom workflows,

• implementation and testing requirements, and

• ongoing monitoring and optimization.

For example, a standard Agentforce action consuming 20 Flex Credits works out to about $0.10 per action at the published rate of $500 per 100,000 credits. An interaction requiring five billable actions would therefore consume about 100 Flex Credits, or roughly $0.50 in Agentforce action consumption.

The key takeaway: Don't estimate your Agentforce budget from the headline price alone. First map the actions your agents will perform and their expected usage volume, then account for licensing, data consumption, implementation, and ongoing optimization to estimate the total cost.

Why Salesforce Agentforce Pricing Is Different

Traditional Salesforce licensing is relatively easy to budget: choose an edition, multiply the monthly price by the number of users, and estimate your annual cost.

Agentforce pricing works differently because the cost can depend on what your AI agents actually do.

Depending on the pricing model you choose, Salesforce may charge based on agent actions, conversations, users, or successfully resolved customer issues. This means two companies with similar Salesforce environments can have very different Agentforce bills.

For example, an internal HR agent answering simple policy questions may perform only a few actions per request. A customer service agent, however, might need to identify the customer, retrieve account information, search knowledge, update a case, trigger a Flow, and generate a response—all within a single interaction.

That is why estimating Agentforce cost based only on the number of employees or customers can be misleading.

The 4 Factors That Have the Biggest Impact on Agentforce Cost

Cost Driver	Why It Matters
Usage Volume	More conversations, actions, or resolutions generally mean higher consumption.
Agent Complexity	Multi-step workflows can consume more resources than simple question-and-answer agents.
Pricing Model	Flex Credits, Conversations, per-user licensing, and resolution-based pricing can produce very different costs for the same use case.
Salesforce Architecture	Data 360 usage, integrations, Flows, APIs, and other Salesforce products can add to the overall cost of running Agentforce.

A Simple Way to Think About Agentforce Pricing

Instead of asking:

“How much does Agentforce cost per user?”

A better question is:

“What will our agents do, how often will they do it, and which pricing model makes those activities most cost-efficient?”

Answering those questions before deployment gives you a much more realistic Agentforce budget and helps avoid choosing a pricing model that looks inexpensive initially but becomes costly as usage scales.

Salesforce Agentforce Pricing Models Compared

No single Salesforce Agentforce pricing model is cheapest for every organization. The right option depends on whether your agents primarily serve customers, assist employees, execute multi-step workflows, or autonomously resolve support requests.

Here is a practical comparison of the main Agentforce pricing approaches in 2026:

Pricing Model	How Cost Is Calculated	Best For	Main Consideration
Flex Credits	Credits consumed when agents perform billable actions	Businesses running different types of agents and workflows	Costs depend heavily on the number of actions agents perform
Conversation Pricing	Charged per qualifying conversation	Customer-facing conversational use cases	Simple to estimate when conversation volume is predictable
Per-User Licensing	Monthly fee based on enabled users	Employee-facing Agentforce use cases	Can be easier to budget when usage is spread across a known workforce
Agentforce 1 Editions	Bundled per-user licensing with included Agentforce capabilities and credits	Organizations planning broader Salesforce AI adoption	Higher starting commitment but combines multiple capabilities
Pay Per Resolution	Charged when the Help Agent successfully resolves a qualifying customer issue	High-volume customer support and self-service	Businesses need to understand what Salesforce considers a billable resolution
Salesforce Foundations	Included entitlement for eligible Salesforce customers	Exploring Agentforce before a larger rollout	Included usage is limited, so production-scale consumption may require additional capacity

Which Agentforce Pricing Model Is Best for Your Use Case?

A useful starting point is to match the pricing structure to the type of work you want the agent to perform.

• Choose Flex Credits when: Your agents perform different actions across Sales, Service, employee support, or custom workflows and you want costs tied more closely to actual agent activity.

• Consider Conversation Pricing when: Your primary use case involves customer-facing conversational agents and conversation volume is easier to forecast than the number of individual actions performed.

• Consider Per-User Licensing when: Agentforce will primarily assist a defined group of employees, such as sales representatives, service teams, or field service users.

• Consider Pay-Per-Resolution when: Your goal is autonomous customer support and you prefer to connect Agentforce spending with successfully resolved customer issues.

• Start with Salesforce Foundations when: You already have an eligible Salesforce edition and want to explore Agentforce capabilities before committing to a larger deployment.

Before Choosing a Pricing Model

Don't compare the options using unit price alone.

For example, $0.10 per standard action may appear cheaper than $2 per conversation, but a conversation can involve multiple actions. Similarly, a per-user license may look expensive compared with consumption pricing until Agentforce usage becomes frequent across hundreds of employees.

Before selecting a model, estimate:

Monthly interactions × average billable activity per interaction × expected usage growth

Then add any relevant licensing, Data 360 consumption, integration, implementation, and ongoing optimization costs.

This gives you a more useful comparison than simply choosing the Agentforce option with the lowest advertised starting price.

How Salesforce Agentforce Pricing Has Changed

Salesforce has changed Agentforce pricing significantly since its launch, moving from a primarily conversation-based model toward more flexible ways to pay for AI agent usage.

Understanding these changes is useful because older articles may still reference pricing options that don't reflect the full range of Agentforce pricing available in 2026.

Period	Pricing Development	Why It Matters
2024	Agentforce launched with conversation-based pricing starting at $2 per conversation	Businesses initially had a relatively simple consumption model for customer-facing agents
2025	Salesforce introduced Flex Credits at $500 per 100,000 credits	Customers gained a more granular way to pay based on the actions agents perform
2025–2026	Salesforce expanded per-user and bundled Agentforce licensing options	Organizations gained alternatives for employee-facing and broader enterprise AI adoption
2026	Salesforce introduced outcome-based pricing for Agentforce Help Agent	Eligible support use cases can connect AI spending to successfully resolved customer issues

What Changed for Agentforce Buyers?

The biggest change is that businesses no longer have to evaluate Agentforce through a single pricing lens.

In 2026, the budgeting question is less about “What is the Agentforce license price?” and more about “Which pricing structure best matches the work our AI agents will perform?”

For buyers, this makes usage forecasting more important. A customer service agent, an internal employee assistant, and a sales agent may have completely different consumption patterns—and therefore different cost economics.

Tip: When comparing Agentforce pricing online, always check the publication or update date. Older pricing guides may focus heavily on the original $2-per-conversation model and may not reflect newer Flex Credit, licensing, bundled, or outcome-based options.

Salesforce Agentforce Flex Credits Explained: How Much Does an Action Cost?

Agentforce Flex Credits are Salesforce's usage-based pricing system that charges businesses according to the billable actions their AI agents perform. Instead of paying a fixed amount per interaction, your cost scales with the actual work the agent completes.

Salesforce lists Flex Credits at $500 per 100,000 credits.

For a standard Agentforce action:

1 standard action = 20 Flex Credits

That means:

100,000 Flex Credits ÷ 20 credits = 5,000 standard actions

So the approximate cost is:

$500 ÷ 5,000 actions = $0.10 per standard action

Agentforce Flex Credit Cost Calculator

You can estimate your Flex Credit consumption using this simple formula:

Monthly Agent Interactions × Average Billable Actions per Interaction × 20 Flex Credits = Estimated Monthly Flex Credits

Then:

Estimated Flex Credits ÷ 100,000 × $500 = Estimated Agentforce Consumption Cost

Example: Calculating Agentforce Flex Credit Cost

Suppose a customer service agent handles 5,000 interactions per month and performs an average of 4 billable actions per interaction.

Step 1: Calculate monthly actions

5,000 interactions × 4 actions = 20,000 actions

Step 2: Convert actions into Flex Credits

20,000 actions × 20 Flex Credits = 400,000 Flex Credits

Step 3: Calculate estimated consumption cost

400,000 ÷ 100,000 × $500 = $2,000 per month

In this simplified scenario, Agentforce consumption would be approximately $2,000 per month, excluding other applicable Salesforce licensing, data consumption, implementation, integration, or operational costs.

How Agentforce Costs Change With Usage

Using the published rate of approximately $0.10 per standard action, here's how different usage levels can affect monthly consumption:

Monthly Interactions	Avg. Actions per Interaction	Monthly Actions	Flex Credits	Estimated Cost
1,000	2	2,000	40,000	$200
5,000	4	20,000	400,000	$2,000
10,000	5	50,000	1,000,000	$5,000
25,000	6	150,000	3,000,000	$15,000
50,000	8	400,000	8,000,000	$40,000

These examples are illustrative estimates based on the published Flex Credit rate. Actual consumption depends on which activities Salesforce classifies and meters as billable actions and the terms of your Salesforce agreement.

What Can Increase Flex Credit Consumption?

The number of customer questions alone does not determine your Agentforce cost. What matters is the amount of billable work the agent performs.

Depending on the use case and configuration, an interaction may involve activities such as:

• retrieving Salesforce data,

• executing a Flow or supported automation,

• calling an external system,

• updating business records, or

• completing other metered agent actions.

For example, two customer support agents could each handle 10,000 interactions per month, but the agent executing more billable actions per interaction may consume significantly more Flex Credits.

Why Agent Design Matters for Agentforce Pricing

This is where Agentforce cost optimization becomes important.

Consider two agents handling the same 10,000 monthly customer requests:

Agent Design	Avg. Billable Actions	Monthly Actions	Approx. Consumption
Agent A – streamlined workflow	3	30,000	$3,000/month
Agent B – complex workflow	8	80,000	$8,000/month

Both agents handle the same number of interactions, but Agent B could cost about $5,000 more per month in this simplified example.

Key takeaway: With Flex Credit pricing, optimizing the number of billable actions required to complete a business outcome can be just as important as controlling overall interaction volume.

What Adds to Your Agentforce Cost Beyond Flex Credits?

Salesforce Agentforce costs aren't limited to Flex Credits or the price of a conversation. For most production deployments, businesses also need to consider the Salesforce products, data consumption, integrations, implementation work, and ongoing management required to make AI agents reliable and useful.

Understanding these costs before deployment can help you build a more realistic Agentforce budget.

1. Data 360 Consumption

Agentforce can use Salesforce Data 360 to access and unify business data for more contextual and personalized responses.

Depending on your architecture and use case, Data 360 consumption may add to the overall cost of running Agentforce. The amount will vary based on the data services, processing, and capabilities your deployment uses.

That is why you should evaluate Data 360 as part of your Agentforce cost model, rather than treating it as a fixed Agentforce license cost.

2. Agentforce Implementation and Configuration

Buying Agentforce capacity does not automatically give you a production-ready AI agent.

Businesses may need to invest in:

• use-case discovery and process mapping,

• agent configuration,

• topics, instructions, and actions,

• Salesforce Flow or Apex development,

• security and permission configuration,

• testing and validation, and

• user training and rollout.

Implementation costs can therefore vary significantly between a simple internal assistant and an autonomous agent connected to multiple business processes.

3. Integration Costs

Agentforce becomes more powerful when it can work across Salesforce and external business systems.

For example, an agent may need access to an ERP, payment platform, order management system, scheduling application, or another third-party platform.

These integrations may require APIs, middleware, custom development, authentication, monitoring, and ongoing maintenance—all of which should be included when estimating Agentforce's total cost.

4. Knowledge and Data Readiness

An AI agent is only as useful as the information and processes available to it.

Before deployment, organizations may need to clean customer data, restructure knowledge articles, remove duplicates, define access permissions, and update outdated documentation.

These activities may not appear on an Agentforce pricing page, but they can become an important part of the implementation budget.

5. Testing, Governance, and Ongoing Optimization

Agentforce should not be treated as a one-time implementation.

After launch, teams need to monitor agent behavior, review outcomes, identify unnecessary actions, improve instructions, update knowledge sources, and control access to sensitive business processes.

As usage grows, ongoing optimization can also help reduce unnecessary consumption and improve the cost per successful business outcome.

Agentforce Cost: Headline Price vs. Total Cost

Cost Component	Included in Headline Agentforce Price?	Should You Budget for It?
Flex Credits / Consumption	Yes	Yes
Agentforce licenses	Depends on model	Yes
Data 360 consumption	Not always	Depends on use case
Implementation & configuration	No	Yes
Custom integrations	No	If required
Data & knowledge preparation	No	Often
Testing & governance	No	Yes
Ongoing optimization	No	Recommended

The Better Way to Calculate Agentforce TCO

Instead of budgeting only for the advertised Agentforce rate, estimate:

Agentforce TCO = Licensing + AI Consumption + Data Consumption + Implementation + Integration + Ongoing Optimization

This gives decision-makers a more realistic picture of what it may cost to move from an Agentforce pilot to production.

Key takeaway: The cheapest Agentforce pricing model on paper is not necessarily the lowest-cost option in production. Your architecture, data readiness, integrations, agent design, and ongoing usage can significantly affect total cost.

Agentforce Flex Credits vs. Conversation Pricing: Which Costs Less?

One of the biggest Agentforce pricing decisions is whether action-based or conversation-based consumption better matches your use case.

At the published headline rates:

• Flex Credits: approximately $0.10 per standard billable action

• Conversation pricing: $2 per qualifying conversation

Using these rates alone, the simplified mathematical crossover occurs at 20 standard actions:

20 actions × $0.10 = $2.00

This means an interaction using only a few standard billable actions may cost less under Flex Credits than the $2 headline conversation rate. As the number of actions increases, that cost advantage becomes smaller.

Simplified Cost Comparison

Standard Actions per Interaction	Flex Credit Cost*	$2 Conversation Rate	Unit-Cost Comparison
2	$0.20	$2.00	Flex Credits lower
5	$0.50	$2.00	Flex Credits lower
10	$1.00	$2.00	Flex Credits lower
15	$1.50	$2.00	Flex Credits lower
20	$2.00	$2.00	Same headline cost
25	$2.50	$2.00	Conversation rate lower
40	$4.00	$2.00	Conversation rate lower

Illustrative comparison based on $0.10 per standard billable action. Actual billing depends on Salesforce's metering rules, eligible usage, purchased products, and contract terms.

Example: 10,000 Customer Interactions per Month

The difference becomes easier to understand at scale.

Suppose your AI agent handles 10,000 interactions every month.

Average Standard Actions	Estimated Flex Credit Consumption	Illustrative $2 Conversation Cost
3 actions	$3,000/month	$20,000/month
8 actions	$8,000/month	$20,000/month
15 actions	$15,000/month	$20,000/month
20 actions	$20,000/month	$20,000/month
30 actions	$30,000/month	$20,000/month

This example shows why understanding the workflow behind an Agentforce interaction matters. Two agents processing the same volume can produce very different consumption costs if one performs substantially more billable actions.

When Flex Credits May Make More Sense

Flex Credits may be worth evaluating when:

• workflows require relatively few billable actions,

• you want granular visibility into agent consumption,

• different agents perform different types of work, or

• usage is better measured by actions than conversations.

When Conversation Pricing May Be Worth Evaluating

Conversation-based pricing may be worth considering when:

• customer conversations are the primary usage pattern,

• interaction volume is easier to forecast than individual actions,

• workflows regularly involve many actions within a conversation, or

• predictable conversation-level budgeting is important.

Don't Choose Based on the 20-Action Number Alone

The 20-action crossover is a mathematical illustration, not a universal Agentforce pricing rule.

Before selecting a pricing model, model a representative sample of your actual workflows and compare expected consumption using your Salesforce pricing and contract terms.

For example:

Expected monthly volume × average billable activity × applicable rate

This gives you a more reliable cost estimate than assuming every Agentforce interaction behaves the same way.

Codleo Tip: Before moving from an Agentforce pilot to production, model a low-, expected-, and high-usage scenario. This helps you understand how quickly costs could change as adoption and workflow complexity increase.

Salesforce Agentforce Voice Pricing: What Should You Budget For?

Agentforce Voice adds another layer to Salesforce Agentforce pricing because the total cost of an AI voice agent may involve more than AI consumption alone.

For businesses planning AI-powered customer service or contact center use cases, it is better to estimate the total cost of the voice experience rather than looking at a single Agentforce rate.

What Can Make Up the Cost of Agentforce Voice?

A production Agentforce Voice deployment can involve several cost components:

Cost Component	What It Covers	What Affects the Cost?
Agentforce Consumption	AI agent activity during voice interactions	Usage volume and billable activity
Voice Usage	Voice-related consumption associated with customer interactions	Call duration and applicable metering model
Telephony	Connecting and managing customer calls	Telephony provider and Service Cloud Voice setup
Data & Context	Customer information used to personalize and complete requests	Data architecture and applicable Data 360 consumption
Integrations	Connections with external business systems	Number and complexity of systems involved
Implementation	Voice agent design, configuration, testing, and deployment	Use-case complexity and business requirements
Monitoring & Optimization	Improving agent performance after launch	Call volume, workflows, governance, and ongoing changes

Why Voice Can Cost More Than a Text-Based Agent

A text-based Agentforce interaction may only need to retrieve information and generate a response.

A voice agent may need to do much more during the same customer request.

For example, a customer calling to change a reservation might require the agent to:

Identify the caller → understand the request → retrieve the reservation → check availability → update the booking → confirm the change

The business therefore needs to consider not only AI consumption but also the telephony and supporting infrastructure required to complete the call.

Example: Modeling Agentforce Voice Cost

Suppose your contact center expects:

• 5,000 AI-assisted calls per month

• an average call duration of 4 minutes

• multiple business actions during each call

That represents approximately:

5,000 calls × 4 minutes = 20,000 voice minutes per month

However, voice minutes alone are not enough to calculate the final budget.

A realistic estimate should consider:

Voice TCO = Agentforce Consumption + Voice Usage + Telephony + Data Consumption + Integrations + Implementation + Ongoing Optimization

This is why businesses should model their actual call flows before estimating Agentforce Voice costs.

Questions to Ask Before Deploying Agentforce Voice

Before selecting a voice architecture, determine:

1. How many calls will the AI agent handle each month?

2. What is the average call duration?

3. How many business actions does a typical call require?

4. Which telephony platform will connect to Salesforce?

5. Which Salesforce and external systems must the agent access?

6. When should the AI agent transfer the customer to a human?

These questions give you a much stronger foundation for estimating the real cost of an Agentforce Voice deployment.

Codleo Tip: Model at least three voice scenarios—simple inquiry, standard transaction, and complex escalation. Comparing their call duration and workflow requirements can reveal which use cases are financially suitable for automation before you scale Agentforce Voice across the contact center.

Agentforce Help Agent Pricing: How Pay Per Resolution Works

Salesforce has introduced an outcome-based pricing option for Agentforce Help Agent, where businesses pay based on successfully resolved customer issues rather than simply paying for every interaction.

The published starting rate is $2 per qualifying resolution.

This changes how businesses think about AI support costs. Instead of focusing only on how many conversations customers start or how many actions an agent performs, the pricing model connects consumption more closely to the outcome the agent delivers.

What Does “Pay Per Resolution” Mean?

A resolution generally represents an eligible customer issue that Agentforce Help Agent successfully handles according to Salesforce's applicable metering criteria.

This distinction is important.

A customer starting a conversation does not necessarily mean the interaction should automatically be treated as a successful resolution. Businesses evaluating this model should understand Salesforce's current definition and metering rules for a billable resolution as part of their pricing and contract review.

Agentforce Pay-Per-Resolution Cost Example

The basic calculation is straightforward:

Number of Billable Resolutions × $2 = Estimated Agentforce Help Agent Cost

For example:

Monthly Billable Resolutions	Estimated Cost
1,000	$2,000/month
5,000	$10,000/month
10,000	$20,000/month
25,000	$50,000/month
50,000	$100,000/month

These are simplified estimates based on the published $2-per-resolution rate. Confirm actual billing eligibility and contract terms with Salesforce.

Example: Estimating Cost From Support Volume

Suppose your support operation receives 20,000 eligible requests per month, and Agentforce successfully resolves 40% of them under the applicable resolution criteria.

That would mean:

20,000 requests × 40% = 8,000 resolutions

Then:

8,000 × $2 = $16,000 estimated monthly resolution-based consumption

The remaining requests may require another outcome, including escalation to a human support representative.

This makes resolution rate an important metric when evaluating the economics of this pricing model.

When Can Pay-Per-Resolution Pricing Make Sense?

This model may be worth evaluating when your organization has:

• high volumes of repetitive customer support requests,

• clearly defined support outcomes,

• a strong and reliable knowledge base,

• processes that can be completed autonomously, and

• measurable support costs you can compare with AI-assisted resolution costs.

Common examples could include order-status questions, account assistance, basic policy queries, appointment-related requests, and other repeatable service scenarios—subject to what your Agentforce configuration can safely and reliably handle.

Don't Compare $2 Per Resolution With $2 Per Conversation Directly

Although both models may show a $2 headline price, they measure different things.

Model	What Drives the Charge?	Primary Cost Metric
Conversation Pricing	Qualifying customer conversation	Cost per conversation
Flex Credits	Billable agent activity	Cost per action
Help Agent	Qualifying successful outcome	Cost per resolution

For this reason, you can't determine the cheapest model by comparing headline numbers alone.

You need to compare metrics such as:

Cost per interaction → Cost per successful resolution → Human escalation rate → Total support cost

A Better ROI Metric: Cost Per Successful Resolution

For customer service use cases, one of the most useful metrics is:

Cost per Successful Resolution = Total AI Support Cost ÷ Number of Successfully Resolved Cases

Then compare that figure with your existing cost per human-handled support case.

For example, if a business currently spends $15 to handle an eligible support case through a human agent and an appropriate AI use case can be resolved at a materially lower total cost while maintaining service quality, the economics of automation become easier to evaluate.

Codleo Tip: Don't evaluate Help Agent only by its $2 headline rate. First identify which support requests are genuinely suitable for autonomous resolution, then model resolution rate, escalation rate, supporting technology costs, and service quality together.

How Much Does Salesforce Agentforce Cost Per Month?

No single monthly Agentforce price applies to every business. Your cost depends on the pricing model, usage volume, number of billable actions, licenses, data consumption, integrations, and implementation requirements.

However, you can build a useful starting estimate by modeling your expected Agentforce consumption.

Here are three illustrative Flex Credit scenarios based on the published rate of approximately $0.10 per standard billable action.

Scenario 1: Small Agentforce Pilot

A company launches an internal or customer-facing agent for a narrow use case.

Assumptions:

• 2,000 interactions per month

• 3 average standard billable actions per interaction

Calculation:

2,000 × 3 = 6,000 monthly actions

6,000 × $0.10 = $600/month

Estimated annual consumption: $7,200

This type of scenario can help a business validate agent behavior, adoption, and consumption patterns before expanding to additional workflows.

Scenario 2: Growing Customer Service Deployment

A mid-sized service team uses Agentforce to handle repeatable customer requests.

Assumptions:

• 10,000 interactions per month

• 5 average standard billable actions per interaction

Calculation:

10,000 × 5 = 50,000 monthly actions

50,000 × $0.10 = $5,000/month

Estimated annual consumption: $60,000

At this stage, workflow design becomes increasingly important. Reducing unnecessary billable activity can materially change annual consumption.

Scenario 3: High-Volume Agentforce Deployment

A larger organization deploys Agentforce across a high-volume customer workflow.

Assumptions:

• 50,000 interactions per month

• 8 average standard billable actions per interaction

Calculation:

50,000 × 8 = 400,000 monthly actions

400,000 × $0.10 = $40,000/month

Estimated annual consumption: $480,000

At this scale, even a small change in average billable actions can significantly affect costs.

For example, reducing the workflow from 8 to 6 actions per interaction would change the simplified consumption estimate to:

50,000 × 6 × $0.10 = $30,000/month

That's a difference of approximately $10,000 per month in this illustrative scenario.

Agentforce Cost Comparison by Usage

Deployment Scenario	Monthly Interactions	Avg. Actions	Estimated Monthly Consumption	Estimated Annual Consumption
Small Pilot	2,000	3	$600	$7,200
Growing Deployment	10,000	5	$5,000	$60,000
High-Volume Deployment	50,000	8	$40,000	$480,000

These scenarios illustrate Flex Credit consumption using an assumed $0.10 per standard billable action. They are not Salesforce quotes or typical customer costs. Actual pricing and metered activity depend on your Salesforce products, configuration, usage, and contract.

From Agentforce Consumption to Total Cost of Ownership

The figures above estimate Agentforce consumption only. Do not treat them as the complete cost of an Agentforce deployment.

For a more realistic budget, calculate:

Estimated Agentforce TCO = Consumption + Licensing + Data Usage + Implementation + Integrations + Ongoing Management

For example, two companies spending the same $5,000 per month on Agentforce consumption could still have very different total costs if one requires complex integrations, significant data preparation, or custom development.

Build Three Budgets Before You Buy

Instead of forecasting Agentforce using a single usage number, create three scenarios:

Scenario	Purpose
Low Usage	Expected consumption during early adoption
Expected Usage	Your most realistic production forecast
High Usage	What happens if adoption or agent activity grows faster than expected

This makes it easier to understand your potential cost range before committing to production.

Codleo Tip: Track cost per successful business outcome, not just cost per action. For a service agent, that could be cost per resolved case. For a sales agent, it could be cost per qualified opportunity or completed sales task. Lower consumption does not necessarily mean better ROI if the agent delivers fewer useful outcomes.

Which Agentforce Pricing Model Should You Choose?

The best Salesforce Agentforce pricing model depends on how your agents will be used, how frequently they will perform work, and whether you want costs tied to actions, conversations, users, or successful outcomes.

Instead of choosing the lowest advertised price, start with your Agentforce use case and expected consumption pattern.

Agentforce Pricing Decision Matrix

Your Use Case	Pricing Model to Evaluate	Why
Testing Agentforce capabilities	Salesforce Foundations	Provides an entry point for eligible Salesforce customers before a broader rollout
Agents performing measurable business actions	Flex Credits	Consumption can be tied more closely to billable agent activity
Customer-facing conversational agents	Conversation Pricing	Useful when qualifying conversation volume is easier to forecast
Employee-facing AI assistance	Per-User Licensing	Can suit organizations providing Agentforce capabilities to a defined group of employees
Broader Salesforce + AI rollout	Agentforce 1 Editions	Bundled approach for organizations planning wider adoption
Autonomous customer support	Pay Per Resolution	Connects applicable Help Agent consumption to qualifying resolved issues

Choose Based on the Work Your Agent Will Perform

Here is a simple framework.

If your agent performs a small number of measurable actions:
Start by evaluating Flex Credits. Estimate how many billable actions a typical interaction requires and multiply that by your expected monthly volume.

If your agent primarily handles customer conversations:
Evaluate conversation-based pricing and compare the expected cost with an action-based model using representative workflows.

If Agentforce will assist a defined employee population:
Compare available per-user licensing with consumption-based alternatives. Consider how often employees will actually use the agent, not just seat count.

If you're deploying autonomous customer support:
Evaluate pay-per-resolution pricing and model your expected resolution rate, escalation rate, and total cost per successful resolution.

If you're planning broader enterprise adoption:
Compare the economics and included capabilities of Agentforce 1 Editions with purchasing Agentforce capabilities separately.

5 Questions to Answer Before Selecting a Plan

Before requesting a final Agentforce quote, answer these questions:

1. What business process will the agent automate or assist?

2. How many interactions do you expect each month?

3. How many billable actions does a representative interaction require?

4. Will the agent primarily serve customers, employees, or both?

5. What other Salesforce products, data services, and integrations are required?

Once you know these numbers, you can build a much more realistic pricing comparison.

Example: Don't Choose Agentforce Pricing by Company Size

Consider two organizations with 500 employees.

Company A deploys an internal agent to answer occasional HR questions.

Company B deploys an autonomous service agent that handles thousands of customer requests and executes multiple business processes every day.

Both organizations have the same employee count, but their Agentforce consumption patterns—and potentially their optimal pricing models—can differ completely.

This is why usage and workflow design are generally more useful budgeting inputs than company size alone.

Recommended Agentforce Pricing Selection Process

Use this sequence before committing to a pricing model:

Define Use Case → Map Agent Workflow → Estimate Volume → Identify Billable Activity → Compare Pricing Models → Calculate TCO → Pilot → Measure Actual Consumption → Scale

A pilot can be particularly valuable because it replaces assumptions with real consumption data. You can then compare your estimated cost with actual Agentforce usage before expanding the deployment.

Codleo Tip: Don't start an Agentforce pricing discussion with “Which license should we buy?” Start with “Which business outcome are we trying to achieve?” Once the workflow and expected volume are clear, selecting and budgeting for the appropriate pricing model becomes much easier.

How to Reduce Salesforce Agentforce Costs: 7 Practical Ways

Agentforce cost optimization is not simply about choosing the cheapest pricing model. How your agents are designed, what tasks they perform, and how closely you monitor consumption can significantly affect your long-term spending.

Here are seven practical ways to control Salesforce Agentforce costs without limiting the value your AI agents deliver.

1. Start With One High-Value Use Case

Avoid deploying Agentforce across multiple departments at once.

Start with a workflow that has:

• measurable transaction volume,

• repetitive tasks,

• clear business outcomes, and

• enough existing cost or manual effort to justify automation.

A focused pilot makes it easier to measure consumption, identify problems, and calculate ROI before expanding Agentforce.

2. Map Agent Actions Before Deployment

Before building an agent, document every step required to complete the workflow.

For example:

Customer Request → Identify Customer → Retrieve Order → Check Status → Generate Response

Then determine which activities may generate billable Agentforce consumption.

Removing unnecessary workflow steps can reduce consumption while also making the agent faster and easier to maintain.

3. Track Cost Per Business Outcome

Monitoring Flex Credits alone does not tell you whether Agentforce is delivering value.

Connect consumption with an actual business outcome.

Agentforce Use Case	Useful Cost Metric
Customer Service	Cost per resolved case
Sales	Cost per qualified opportunity
Employee Support	Cost per completed request
Appointment Management	Cost per completed booking
Lead Qualification	Cost per qualified lead

This helps you determine whether higher Agentforce consumption is actually producing higher business value.

4. Monitor Consumption Regularly

Don't wait until the end of the billing period to understand Agentforce usage.

Monitor consumption as adoption increases and investigate unexpected changes.

For example, if an agent's monthly interaction volume increases by 10% but its consumption increases by 40%, review whether workflows have become more complex or unnecessary activities are being executed.

5. Optimize High-Volume Workflows First

A small efficiency improvement can become financially significant at scale.

Consider an agent handling 50,000 interactions per month.

If workflow optimization reduces average standard billable actions from:

8 actions → 6 actions

the simplified consumption estimate changes from:

50,000 × 8 × $0.10 = $40,000/month

to:

50,000 × 6 × $0.10 = $30,000/month

That's an illustrative difference of $10,000 per month.

For this reason, prioritize optimization of the workflows generating the highest volume or consumption.

6. Review Your Pricing Model as Usage Changes

The pricing model that works during a pilot may not remain the best fit after Agentforce adoption increases.

Periodically review:

• interaction volume,

• average billable activity,

• number of enabled users,

• autonomous resolution volume,

• escalation rates, and

• expected future growth.

Then compare those numbers with the Agentforce pricing options available under your Salesforce agreement.

7. Scale Based on Measured ROI

Don't expand Agentforce simply because a pilot technically works.

Before adding another agent or business process, measure:

Business Value Generated − Total Agentforce Cost = Estimated Net Value

Also consider improvements that are harder to express directly in dollars, such as faster response times, increased availability, reduced repetitive work, and improved employee productivity.

Scale the use cases where Agentforce demonstrates measurable operational or financial value.

Agentforce Cost Optimization Checklist

Before scaling an Agentforce deployment, ask:

• Do we know our average consumption per interaction?

• Which workflows consume the most?

• Are all agent actions necessary to achieve the outcome?

• What is our cost per successful business outcome?

• Which use cases generate the strongest ROI?

• How quickly could consumption increase as adoption grows?

• Does our current pricing model still match our usage pattern?

If you cannot answer these questions, optimize and measure the existing deployment before expanding it.

Codleo Tip: The goal should not be to minimize Agentforce usage at all costs. The better objective is to reduce wasted consumption while increasing the value generated per interaction.

Is Salesforce Agentforce Worth the Cost?

Salesforce Agentforce can be worth the investment when it automates high-volume work, reduces repetitive manual effort, improves response times, or helps employees complete revenue-generating tasks more efficiently.

But measure a successful Agentforce deployment by business outcomes—not simply by the number of conversations, actions, or Flex Credits consumed.

How to Calculate Agentforce ROI

A simple starting formula is:

Agentforce ROI (%) = [(Estimated Business Value − Total Agentforce Cost) ÷ Total Agentforce Cost] × 100

Your total Agentforce cost should include more than AI consumption:

Total Cost = Agentforce Consumption + Licensing + Data Usage + Implementation + Integrations + Ongoing Management

Business value will depend on the use case.

For customer service, for example, value may come from reducing the number of cases that require human handling.

Agentforce ROI Example: Customer Service

Suppose a business handles 10,000 support requests per month.

Assume:

• 4,000 requests can be successfully handled by Agentforce

• average human-handled case cost = $12

• estimated Agentforce-related cost for those requests = $20,000/month

Without automation:

4,000 × $12 = $48,000

Estimated monthly cost avoided:

$48,000 − $20,000 = $28,000

Using the simplified ROI formula:

($48,000 − $20,000) ÷ $20,000 × 100 = 140%

In this illustrative scenario, Agentforce would generate an estimated 140% ROI on the modeled monthly cost.

This is an illustrative example, not a typical Agentforce ROI benchmark. Actual savings depend on your existing operating costs, resolution quality, implementation costs, escalation rates, and Agentforce consumption.

Measure ROI Differently for Each Agentforce Use Case

Not every Agentforce deployment should be measured using customer service savings.

Agentforce Use Case	Useful ROI Metric
Customer Service	Cost per successfully resolved case
Sales	Cost per qualified opportunity / revenue influenced
Lead Qualification	Cost per qualified lead
Employee Support	Cost and time saved per completed request
Appointment Management	Cost per successfully completed booking
Field Service	Time saved per service request

This helps prevent a common mistake: evaluating every AI agent using the same ROI metric.

When Agentforce May Be Worth the Investment

Agentforce is easier to justify financially when:

• the workflow has sufficient transaction volume,

• employees spend significant time on repetitive tasks,

• the business outcome can be clearly measured,

• the required data and knowledge are reliable,

• the agent can complete meaningful portions of the workflow, and

• the value generated exceeds the total cost of running and maintaining the solution.

When Agentforce May Not Make Financial Sense Yet

Agentforce may be harder to justify when:

• the process happens only occasionally,

• workflows change frequently,

• most interactions still require human intervention,

• data or knowledge sources need significant cleanup,

• integrations are disproportionately complex, or

• the organization has no clear metric for measuring success.

In these situations, improving the underlying process or starting with a smaller Agentforce pilot may make more sense than pursuing a large-scale deployment immediately.

Calculate Your Agentforce Break-Even Point

Another useful question is:

How many successful outcomes does Agentforce need to deliver before the investment pays for itself?

A simplified calculation is:

Break-Even Outcomes = Total Agentforce Cost ÷ Value Generated per Successful Outcome

For example, if your total monthly Agentforce cost is $20,000 and each successfully automated case creates $10 of measurable value:

$20,000 ÷ $10 = 2,000 successful outcomes

Agentforce would need to deliver approximately 2,000 such outcomes per month to reach the simplified break-even point.

Codleo Tip: Build the ROI model before the Agentforce implementation—not after it. Define the current cost of the process, target outcome, expected automation rate, and acceptable cost per outcome. Once Agentforce goes live, you can compare actual results against those baseline numbers.

Final Thoughts: What Will Agentforce Really Cost Your Business?

Salesforce Agentforce does not have one price that fits every organization. Your actual investment depends on the pricing model you choose, how frequently your agents are used, the number of billable activities they perform, and the supporting Salesforce architecture required for your use case.

The most important numbers to understand before budgeting for Agentforce are:

• your expected monthly usage,

• average billable activity per interaction,

• applicable Agentforce licensing or consumption model,

• data and integration requirements,

• implementation and ongoing management costs, and

• the business value generated by each successful outcome.

Instead of asking “What is the cheapest Agentforce plan?”, ask:

“Which Agentforce pricing model gives us the best cost per successful business outcome?”

Start with a focused use case, model low, expected, and high usage scenarios, validate those assumptions through a pilot, and measure actual consumption before scaling.

Need Help Estimating Your Agentforce Costs?

Choosing an Agentforce pricing model is easier when you know what your agents will actually do.

As a Salesforce Summit Consulting Partner, Codleo Consulting helps businesses assess Agentforce use cases, map agent workflows, estimate consumption, and plan implementations around measurable business outcomes.

Whether you're evaluating Flex Credits, conversation-based pricing, per-user licensing, or outcome-based pricing, our Salesforce consultants can help you understand the likely cost drivers before you move from planning to production.

Talk to Codleo's Agentforce experts for a pricing and readiness assessment.