Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Salesforce is no longer merely considering consumption pricing for AI agents. The company first proposed charging about $2 per conversation in August 2024, launched that model with Agentforce later that year, and added Flex Credits in May 2025. As reflected in Salesforce pricing materials reviewed in August 2026, buyers may encounter conversation pricing, action-based credits, user licensing, and contract-specific packages.
The important question is not simply whether Agentforce costs $2. It is how Salesforce defines a billable conversation or action, how many automated steps one request triggers, and what licenses and platform services remain necessary.
What Salesforce said in 2024
The pricing story began on Salesforce’s fiscal second-quarter 2025 earnings call on August 28, 2024. Morgan Stanley analyst Keith Weiss asked how Salesforce might price its software if AI agents performed work that would otherwise require licensed human users.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Salesforce CEO Marc Benioff said the company was considering consumption-based pricing and mentioned approximately $2 per conversation. He also discussed the possibility of selling consumption credits, similar to the way Salesforce sells Data Cloud credits.
#1 Best Overall
At that point, this was a strategic pricing signal—not a finalized rate card. The underlying business problem was potential seat cannibalization: if agents automate more service, sales, or operational work, customers may not need as many human Salesforce seats. That was an investor concern and an economic possibility, not proof that Salesforce customers had broadly reduced their licenses.
Consumption pricing gives Salesforce another way to monetize automated work even when the number of human users stays flat. It also lets the company capture value from digital labor, workflows, and customer interactions.
See the original CIO report on Salesforce’s 2024 pricing discussion.
Recommended Free Tools
What Salesforce actually launched
Salesforce later turned the proposal into a commercial Agentforce model. In its October 2024 launch material, Salesforce said Agentforce pricing would start at $2 per conversation, with standard volume discounts. Agentforce for Sales and Service was scheduled to become generally available on October 25, 2024.
A conversation is a relatively simple unit for finance teams: forecast the number of customer interactions, multiply by the applicable price, and account for discounts. But the unit can be blunt. A short request and a complex troubleshooting exchange may each count as one conversation even though the agent performs very different amounts of work.
That limitation helps explain why Salesforce subsequently added a more granular consumption model.
Flex Credits introduced a second meter
On May 15, 2025, Salesforce introduced Flex Credits while retaining the conversation-based option. Flex Credits measure agent activity through actions, such as updating records, resolving cases, automating workflows, or executing custom prompts and flows.
Salesforce’s published base signal is:
- $500 per 100,000 Flex Credits
- 20 Flex Credits for a standard action
- An implied base example of $0.10 per standard action
- 30 Flex Credits for an Agentforce Voice action, according to the public pricing material
The $0.10 figure is not a universal price for every action or deployment. Applicable usage types, multipliers, environments, editions, discounts, and contract terms can change the calculation. Salesforce’s rate-card documentation controls for a particular purchase.
More importantly, one customer request does not necessarily equal one action. Salesforce’s own public example describes a request requiring two actions and costing $0.20 under the example assumptions. A workflow that retrieves information, validates eligibility, updates a record, and sends a response could consume several actions.
Salesforce describes conversation pricing as particularly suitable for external-facing customer agents, while Flex Credits provide broader and more granular measurement. The right choice depends on the workflow rather than on which headline price appears lower.
How the visible pricing choices compare
| Model | Published signal | What it measures | Likely fit |
|---|---|---|---|
| Flex Credits | $500 per 100,000 credits | Agent actions, subject to usage rules | Internal or external workflows requiring granular measurement |
| Conversations | $2 per conversation | Completed or billable interactions under Salesforce’s definition | Customer-facing use cases with forecastable interaction volumes |
| Agentforce User License | $5 per user per month | User access layered on metered usage | Employee-facing access where Flex Credits are also required |
| Salesforce Foundations | $0 for listed capabilities | Defined entry-level capabilities, not unlimited production usage | Evaluation or limited starting deployments |
| Other packages | Varies | Edition- and contract-dependent access | Organizations buying a broader Salesforce agreement |
These are public pricing signals, not a universal quote. Salesforce states that its pricing information is subject to change. Actual cost can depend on geography, edition, product availability, existing contracts, volume, required data services, integrations, and negotiated terms. Check the Agentforce pricing page and the applicable Flex Credit documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Worked examples: why the unit matters
Conversation example
At the published conversation price:
10,000 conversations × $2 = $20,000 per monthThis is an illustration, not a quote. It excludes volume discounts, taxes, required Salesforce products, implementation, monitoring, regional pricing, and contract terms.
Flex Credit example
Using Salesforce’s published base assumptions:
100,000 credits = $50020 credits per standard action = $0.10 per action
A request requiring three standard actions would consume 60 credits, or $0.30 under those assumptions:
3 actions × 20 credits = 60 credits60 credits × $0.005 = $0.30
This does not mean every request uses three actions. A simple request might use fewer; a request involving multiple retrievals, validations, updates, or system calls might use more. Voice and other usage categories may have different consumption rules.
That is why comparing $2 per conversation with $0.10 per action without estimating action counts can produce a misleading result. If a typical interaction requires 20 standard actions, its base Flex Credit equivalent would be $2. If it requires two actions, the equivalent would be $0.20.
Free tools Windows power users keep installed
One-click scans. No signup required.
Conversation pricing versus Flex Credits
When conversations may be easier
Conversation pricing can be attractive when a service organization measures demand in completed customer interactions and can forecast volume reliably. It is easier to explain to finance teams and may reduce the need to model every internal agent step.
The trade-off is that the price may not reflect complexity. A conversation that triggers several backend operations may consume the same conversation unit as a short informational exchange. Unexpected traffic or unusually long interactions can also increase the bill.
When Flex Credits may be more useful
Flex Credits can provide better visibility when the business wants to pay for discrete work performed rather than an entire interaction. They may be useful for internal employee agents, workflow automation, and mixed internal-external deployments.
The cost is forecasting complexity. Finance and operations teams need to understand the number and type of actions per request. A poorly designed agent can inflate consumption through unnecessary retrievals, repeated validations, retries, or redundant updates.
Flex Credits are not automatically cheaper. They may be economical for workflows requiring only a few eligible actions, but the result depends on the actual workflow and the applicable rate card.
The total-cost model buyers should use
The headline meter is only one component of an Agentforce business case.
Conversation model
Monthly cost = billable conversations × conversation price - discounts + required licenses and services + implementation and governanceFlex Credit model
Monthly cost = sum of actions by usage type × applicable credit multiplier × effective credit price + platform and user licenses + implementation and governanceA complete model should include:
- Expected monthly traffic and seasonal peaks
- Average and high-end actions per request
- Human handoff and escalation rates
- Failed, retried, or duplicated actions
- Voice, text, and other channel differences
- Existing Salesforce editions and human-user licenses
- Agentforce user licenses, where required
- Data Cloud or Data 360, integration, API, storage, and identity requirements
- Implementation, testing, security review, monitoring, and governance
- Negotiated discounts, minimum commitments, payment timing, and credit expiration rules
The question for a CFO is therefore not “What is the Agentforce list price?” It is “What is the fully loaded cost per resolved interaction, completed workflow, or business outcome?”
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Important billing questions and edge cases
Before signing an agreement, a buyer should obtain written answers to the following:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches- What exactly starts and ends a conversation? Ask how follow-up messages, reopened cases, sessions, and transfers are treated.
- Which actions consume Flex Credits? Request the applicable usage table, including prompts, flows, retrievals, record updates, and tool calls.
- Are failed or retried actions billed? Clarify how technical failures, timeouts, duplicate submissions, and automated retries are counted.
- How are human handoffs charged? An agent may consume resources before escalating to a service representative.
- Do sandbox and production use the same rules? Environments and usage types may be treated differently.
- How is voice priced? Salesforce’s public material identifies separate voice-action consumption.
- Do credits expire or roll over? Contract documents and the applicable rate card control.
- What is included in any free or foundational offering? A $0 entry point does not mean unlimited production use.
- What controls exist? Ask about alerts, limits, attribution by agent or department, and the ability to pause or restrict a runaway workflow.
- What changes at renewal? Published rates, multipliers, entitlements, and packaging can change.
Salesforce says Digital Wallet provides visibility into consumption, with more granular information for Flex Credits than for conversations. Monitoring should be treated as part of the pricing decision, not as an afterthought.
Common failure modes
- Budget shock: pilot traffic understates production demand or a seasonal event creates a usage spike.
- Action inflation: an agent performs excessive retrieval, validation, or update steps for a simple request.
- Seat-plus-usage stacking: the organization continues paying for human licenses while also paying for automated execution.
- Unclear attribution: departments cannot identify which agent generated consumption.
- Bad unit economics: the metered cost approaches the labor cost of the process being automated.
- Over-automation: the agent handles easy cases but creates expensive escalations for complex ones.
- Contract ambiguity: the public list price does not show minimums, discounts, entitlements, or renewal protections.
How Salesforce compares with alternatives
Salesforce is not the only enterprise vendor using consumption-oriented AI packaging. Microsoft Copilot Studio is a natural comparison for organizations centered on Microsoft 365, Dynamics, Azure, and Power Platform. ServiceNow AI agents may fit organizations whose IT service, employee, and operational workflows already run on ServiceNow.
Intercom Fin and Zendesk AI are narrower customer-support alternatives for organizations that do not need Salesforce’s broader CRM and data-platform footprint. Current prices and exact packaging for these products are not stated here because they require separate verification.
The best alternative depends on the company’s existing data, permissions, workflow, identity, and governance stack. A lower headline price can be offset by migration, integration, or duplicated platform costs.
A practical procurement checklist
Ask Salesforce or its implementation partner for a scenario-based quote containing:
- Monthly low, expected, and peak conversation volumes
- Estimated actions per request by workflow
- Separate treatment of text, voice, internal, and external use
- Expected human handoff rates
- Required human and Agentforce user licenses
- Data, integration, storage, and platform prerequisites
- Included, prepaid, committed, and pay-as-you-go credits
- Discount tiers and minimum commitments
- Credit expiration, rollover, and renewal provisions
- Sandbox and production billing rules
- Usage dashboards, alerts, limits, and departmental attribution
- Exit, migration, and data-retention terms
Run the quote through at least three scenarios: a low-volume pilot, an expected production case, and a high-growth or peak-demand case. Include the cost of keeping the human workforce and Salesforce seats needed for exceptions and escalations.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
