Salesforce Agentforce Pricing 2026: Rates and Cost Math
See official Agentforce rates, calculate Flex Credit and conversation costs, and choose the right pricing model for one Salesforce workflow.
ConvoPro Team
Salesforce Advisors
Insight
Salesforce Agentforce pricing at a glance
Salesforce Agentforce pricing in 2026 is not one number. As of July 21, 2026, Salesforce publicly lists Flex Credits at $500 per 100,000 credits, Conversations at $2 per conversation, an Agentforce User License at $5 per user per month plus Flex Credits, employee add-ons from $125 per user per month, and Agentforce 1 Editions from $550 per user per month.
The correct option depends on who uses the agent, how many actions it performs, whether the workflow is customer-facing or employee-facing, and what sits outside the published rate. The safest way to budget is to model one real workflow before selecting an org-wide pricing structure.
This is an independent guide published by ConvoPro, not an official Salesforce pricing page. Salesforce states that its public pricing is informational and subject to change, so confirm final terms with your account team.
Pricing model | Published US price | How it is metered | Practical fit | Main issue to verify |
|---|---|---|---|---|
Salesforce Foundations | $0 | Free access tier | Exploration and initial building | Confirm the consumption entitlements available in your org |
Flex Credits | $500 per 100,000 credits | Each agent action consumes credits | Mixed use cases, variable workloads, employee and customer workflows | Number of actions performed per request |
Conversations | $2 per conversation | Each qualifying customer-facing conversation | External agents with stable interaction volume | Conversation definition and org-level model choice |
Agentforce User License | $5 per user/month | Seat fee plus metered Flex Credit use | Broad employee access with limited CRM object access | Flex Credit consumption is still additional |
Agentforce add-ons | $125 per user/month | Per-user flat fee | Employee agents and packaged AI capabilities | Base products, eligible users and included capabilities |
Agentforce Industries add-ons | $150 per user/month | Per-user flat fee | Industry-specific employee use cases | Edition and industry requirements |
Agentforce 1 Editions | From $550 per user/month | Bundled edition | Larger employee-facing programs | Salesforce lists 2.5 million Flex Credits per org per year, not per user |
Salesforce currently describes Flex Credits and Conversations as separate consumption models. They cannot be used together in the same Salesforce org. That makes the choice more consequential than comparing two rates in a spreadsheet.
How Flex Credit pricing works
Flex Credits charge for the discrete actions an agent performs. Salesforce examples include updating a record, summarizing a case, answering a question, executing a prompt, or running a Flow.
At Salesforce’s published US list rate:
One Flex Credit costs $0.005.
A standard Agentforce action uses 20 credits, or approximately $0.10.
An Agentforce Voice action uses 30 credits, or approximately $0.15.
The basic monthly formula is:
Monthly cost = standard actions × $0.10 + voice actions × $0.15
A more useful workflow formula is:
Monthly cost = runs per month × actions per run × cost per action
This only calculates Agentforce consumption. It does not include implementation, Data 360 usage, other consumption services, integrations, telephony, testing, support or ongoing administration.
Worked example: service case assistance
Assume:
100 service users
3 cases handled per user per day
20 working days per month
3 standard actions for each case
The monthly action count is:
100 users × 3 cases × 20 days × 3 actions = 18,000 actions
At $0.10 per standard action:
18,000 actions × $0.10 = $1,800 per month
This matches Salesforce’s published case-management example. The agent identifies a customer, retrieves related cases and adds a case comment. Salesforce explicitly labels the example as illustrative and excludes Data 360 credits and other services.
Worked example: customer order status
Assume a self-service agent handles:
20 requests per day
30 days per month
2 standard actions per request
The monthly calculation is:
20 requests × 30 days × 2 actions = 1,200 actions
1,200 actions × $0.10 = $120 per month
That figure may look inexpensive, but it remains accurate only while each request reliably stays at two actions. Add identity verification, another system lookup, an order change, an escalation or a customer message, and the action count rises.
The rate is not usually the hardest part to estimate. The difficult input is how many metered actions a completed workflow will actually require.
Flex Credits versus $2 conversation pricing
Conversation pricing provides a simpler external-agent metric: $2 for each qualifying conversation. Flex Credits instead meter every action used during that interaction.
At public list rates, the rough consumption-only break-even point is 20 standard actions:
Standard actions in one conversation | Flex Credit cost | Conversation price |
|---|---|---|
5 | $0.50 | $2.00 |
10 | $1.00 | $2.00 |
20 | $2.00 | $2.00 |
30 | $3.00 | $2.00 |
This does not prove that Flex Credits are cheaper whenever an interaction uses fewer than 20 actions. The comparison excludes contract pricing, other consumption, failures, retries, data operations and differences in how Salesforce defines and meters a conversation.
It does provide a useful design test. If your customer interaction is short and consistent, calculate both models. If it regularly branches into record retrieval, knowledge searches, Flow execution, external systems and record updates, count those steps before assuming a $0.10 headline action represents the finished job.
Salesforce positions Conversations for customer-facing agents and Flex Credits for a broader range of use cases. Because the models cannot coexist in one org, the decision should reflect your full planned workflow mix rather than the first agent you launch.
Flex Credit purchasing options
Salesforce currently describes three purchasing structures:
Buying structure | Payment approach | Primary planning risk |
|---|---|---|
Pre-Purchase | Buy a set amount for the contract term and pay upfront | Buying more credits than the organization uses |
PayGo | No upfront commitment; usage is billed monthly in arrears | Variable monthly cost |
Pre-Commit | Commit to a baseline and pay monthly in arrears | A term-end true-up if usage falls below the commitment |
Salesforce says Flex Credits can be purchased through PayGo and Pre-Commit structures. Conversation pricing, Agentforce add-ons and Agentforce 1 Editions are not available through those two models.
The public pricing page also states that unused Flex Credits do not roll into later subscription terms. If consumption exceeds the contracted entitlement, Salesforce says there is no separate overage penalty; the contracted rate is billed monthly in arrears. Confirm how those terms apply to your agreement before purchasing.
What the employee license options actually mean
Per-user pricing can look simpler than consumption pricing, but the options are materially different.
Agentforce User License
The $5 per-user monthly license is intended to extend employee access. Salesforce states that it requires Flex Credits, provides access to limited Salesforce CRM objects and retains metered employee usage.
Do not budget it as an all-inclusive $5 agent license. Your estimate needs both components:
Employee seat cost + expected Flex Credit consumption
Agentforce add-ons
Salesforce lists Agentforce add-ons for Sales, Service and Field Service at $125 per user per month. It describes these as including unmetered Agentforce usage for licensed employees and additional AI capabilities.
Industry-specific add-ons are listed at $150 per user per month.
These may be a better commercial fit when a defined employee population will use agents frequently enough that consumption forecasting becomes burdensome. You still need to verify the applicable Salesforce editions, included features and implementation requirements.
Agentforce 1 Editions
Agentforce 1 Editions start at $550 per user per month for Sales, Service, Field Service and Industries. Salesforce lists the Agentforce add-on and 2.5 million Flex Credits per org per year as included.
The phrase per org per year matters. A 500-user deployment does not receive 500 separate blocks of 2.5 million credits.
Costs the rate card does not calculate
Agent consumption should be a distinct line in the budget, not the entire budget.
Cost category | Questions to answer |
|---|---|
Underlying licenses | Which Salesforce editions, clouds or user licenses must already be in place? |
Data and grounding | Will the workflow consume Data 360 credits or another retrieval service? |
Implementation | Who will define topics, actions, prompts, Flows, integrations and guardrails? |
Data preparation | Is the required knowledge complete, current, permissioned and usable? |
Testing | How will the team test accuracy, action selection, permissions and failure paths? |
Integrations | Are MuleSoft, external APIs, custom services or middleware required? |
Voice infrastructure | What telephony or contact-center services are needed? |
Monitoring | Who owns Digital Wallet alerts, action logs, quality reviews and cost anomalies? |
Ongoing administration | Who updates prompts, actions, permissions and workflows when processes change? |
Adoption | How will employees be trained, supported and held accountable for using the workflow? |
Salesforce’s own examples warn that the published calculations exclude Data 360 credits and other consumption services. Treat the consumption estimate as one input to total cost, not a complete quote.
A practical Agentforce pricing decision framework
Start with the operating model, then choose the meter.
Define one completed job. “Support automation” is too broad. “Identify the customer, retrieve open cases, prepare a summary and draft the next response” is measurable.
Separate AI judgment from deterministic work. Interpretation, summarization and classification may benefit from AI. Known validation rules, record routing and required approvals may remain in Flow.
Count the actions in a normal run. Include retrieval, prompts, Flow calls, record changes, external calls and messages.
Measure monthly volume. Use real case, message, call or employee-task counts rather than an adoption target.
Model exceptions. Estimate how often the workflow retries, branches, escalates or needs another lookup.
Compare the applicable models. For an external agent, compare Flex Credits with Conversations. For employee use, compare the $5 license plus consumption with the flat employee add-ons.
Add non-meter costs separately. Include data, implementation, testing, integrations, training and ongoing ownership.
Validate through a bounded pilot. Measure actual actions, completion rate, exception rate, human review and total cost before committing the entire org.
The ConvoPro Agentforce cost calculator provides a workflow-level method for documenting these assumptions.
Where ConvoPro fits in the decision
Agentforce can be the right choice for an organization building a broader Salesforce agent program across channels, departments and use cases.
A different approach may fit a lean Salesforce team whose immediate problem is one repeated workflow that involves messy records, emails, files or human judgment.
ConvoPro currently publishes a starting price of $25 per user per month, plus AI usage passed through at cost. Its product model centers on shared prompt buttons, admin-defined boundaries, visible usage and human confirmation before configured data-changing actions run. Implementation and partner-led rollout are scoped separately.
That does not make ConvoPro a universal replacement for Agentforce. It creates another buying path:
Use Agentforce when the organization is ready for a broader enterprise agent strategy.
Use Salesforce Flow alone when the process is deterministic and does not require AI interpretation.
Consider ConvoPro when the goal is to prove one governed Salesforce workflow before expanding into a larger agent or data program.
The ConvoPro versus Agentforce comparison applies those criteria to workflow scope, governance and team capacity.
Agentforce pricing FAQs
How much does Salesforce Agentforce cost in 2026?
Salesforce lists several models. Flex Credits cost $500 per 100,000 credits. Conversations cost $2 each. The Agentforce User License costs $5 per user per month and requires Flex Credits. Employee add-ons start at $125 per user per month, industry add-ons at $150, and Agentforce 1 Editions at $550.
How many Flex Credits does an Agentforce action use?
Salesforce states that a standard Agentforce action uses 20 Flex Credits. At the published US rate, that is approximately $0.10. A Voice action uses 30 credits, approximately $0.15.
Can one Salesforce org use Flex Credits and Conversations?
No. Salesforce states that the two consumption models are not supported in the same org. Model the organization’s planned mix of workflows before choosing one.
Do unused Flex Credits roll over?
Salesforce says unused Flex Credits do not roll into subsequent subscription terms.
Is the $5 Agentforce User License an all-inclusive price?
No. Salesforce states that the license requires Flex Credits. Budget the user license and metered usage separately.
Sources and verification
Pricing and packaging were last verified on July 21, 2026 against the official Salesforce Agentforce pricing page and Agentforce rate cards. ConvoPro statements were checked against the current ConvoPro pricing page, product comparison and workflow-pilot page.
Salesforce pricing, packaging, entitlements and contract terms can change. Use your Salesforce quote and executed agreement as the final source of truth.
Choose the model from one real workflow
Do not begin with a company-wide license estimate. Bring one repeated workflow, its monthly volume, the actions it performs and the controls it requires.
Then calculate the consumption cost, add the operating costs and compare the implementation paths on equal terms.
Plan a governed workflow pilot with ConvoPro to map the actions, review points and cost assumptions before scaling.
