Agentforce Pricing: Flex Credits, Conversations and User Plans

Salesforce Agentforce pricing has two headline consumption options: $500 per 100,000 Flex Credits or $2 per conversation, alongside separate per-user licenses for employee use. At the published credit rate, a standard production text action costs $0.10, but a customer request can trigger several actions. For a company already on Salesforce, the buying decision is which work is metered, which employees qualify for unmetered use, and what your existing edition already includes.

Verified against Salesforce's live Agentforce pricing page and Help documentation, October 2026. Sources checked on 26 October 2026; prices below are US dollars.

Salesforce Agentforce Pricing at a Glance

Agentforce has several billing routes, not a single price per agent. The table covers every offer named on Salesforce's Agentforce pricing page, plus the relevant action, prompt and sales-engagement meters in its current Flex Credits rate card. Credit multipliers are published rates; dollar equivalents marked “calculated” use the published credit-pack price.

Sales and Service Max are edition purchases, while the employee add-ons sit on top of qualifying subscriptions. The $550 Sales Max and $550 Service Max prices are monthly equivalents billed annually. The central Agentforce page gives a starting price for the wider Max family, so request a quote for the exact Sales/Service or Industries configuration. Do not assume every variant has the same price.

What Is Agentforce Charging You For?

Salesforce Agentforce is the company's AI-agent offering: software that can retrieve information and perform tasks in business workflows. Its billing separates access to the software from the work the software performs.

For an operator, start by identifying the interaction. A customer checking an order, an employee asking for a case summary, and a scheduled process preparing summaries can have different billing treatment even when they touch the same customer record. Salesforce's usage and billing documentation distinguishes action-based agent work, prompt-based AI features, and licensing that makes certain usage unmetered.

That is why “we already pay for Salesforce” is not enough to price the project. Check the existing edition, the agent or feature you intend to deploy, and the identity under which its work executes. Then compare the incremental bill with the work it will remove.

Flex Credits: What Salesforce Counts as an Action

An action is a function the agent executes, not a message the customer sends. Salesforce distinguishes standard actions supplied with the product from custom actions you create or modify. Retrieving a record and updating that record can be separate actions inside the same request.

The current Flex Credits Help documentation says each standard or custom text action is currently counted as one action regardless of the tokens it processes. Actions count whether they run through explicit reasoning instructions or are selected during model reasoning. Utilities such as handing off to a representative, setting variables, or changing topics are excluded from agent-action billing.

The practical distinction is between a conversation transcript and the execution trace, the record of functions the agent called. A long exchange can use few actions; a short request can cause several lookups and updates. Estimate from those function calls rather than the number of chat bubbles.

Some standard actions require additional user licenses. Asynchronous calls to Salesforce AI inside a custom action can also incur extra charges. Buying a credit pool therefore does not automatically grant every action or cover every operation hidden inside custom code.

Direct prompts have their own meter

Prompt usage applies to direct model requests, including embedded AI features. Salesforce counts input and output in blocks of up to 2,000 tokens, rounding up, with the model determining the prompt category. The current rate card assigns different multipliers to Starter, Basic, Standard and Advanced prompts. A token is a small unit of data processed by the model. Prompt metering definitions.

For budgeting, keep direct prompt calls separate from action invocations. Do not apply a prompt multiplier to every chat message, or assume every AI operation is a standard action.

Conversations: What Starts and Ends a Billable Session

Salesforce still publishes $2 per conversation today. It is not merely a historical launch price. However, a conversation is a defined usage window or event, not a promise that the customer's issue was solved.

For Agentforce Service Agent messaging, the window begins with the user's first message after the previous window ends, or when the agent sends its configured welcome. Salesforce's Conversations usage definitions specify:

• Unauthenticated Messaging for Web: the window ends when the user ends the conversation.
• Authenticated Messaging for Web: it ends 24 hours after starting.
• Messaging for In-App and the listed enhanced messaging channels: the window ends after 24 hours. The list includes WhatsApp, Facebook Messenger, Apple Messages for Business, SMS and LINE.

A blanket “every conversation lasts 24 hours” description would miss the unauthenticated web rule. Ask which channel your service agent will use before converting case volume into billable conversations.

The same Help page retains other conversation-based usage types. Sales Coach consumes a conversation when the user requests feedback after a coaching session. SDR consumes one when it sends the initial email to a lead, with subsequent activity included; cancelling and restarting outreach consumes another. Its model access can also consume Einstein Requests. Those definitions do not mean every current sales-agent product uses the Conversations SKU.

The Conversations rate card also warns that certain features can consume Einstein Requests and Data Services Credits. The flat conversation charge is not a universal all-in infrastructure price.

Help Agent Resolutions is a different $2 meter

Help Agent charges for qualifying resolutions, using 400 production Flex Credits per resolution. Salesforce's rules require at least two message turns, no explicitly negative final feedback, and either completion without human escalation or explicitly positive final feedback. Unresolved sessions are not billed as resolutions; agent actions and Data 360 queries within a successfully resolved interaction are included. Help Agent billing rules.

Duration still matters. The Service usage documentation defines up to 2 hours for chat and messaging resolutions, 10 minutes for a voice resolution, and 3 days for email. Longer interactions can count as additional resolutions. Ask for the exact Help Agent channel rules, rather than borrowing the older Conversations window.

Sales engagement can use Leads Worked

Salesforce also publishes a Leads Worked meter for prospect engagement. Its Agentforce Engagement billing page describes a rolling 30-day window beginning with the first qualifying response to a person. Current Flex Credits documentation also notes that a web interaction can count as two Leads Worked when the agent attempts to create a lead, and that related actions and data services can consume credits.

For a sales operator, “per lead” therefore needs a product-specific definition. Get the agent name and usage type on the quote; do not reuse an SDR conversation estimate for a different engagement agent.

Agentforce for Sales Pricing: Access Versus Unmetered Use

The $5 user license and $125 employee add-on solve different purchasing problems. The first provides limited-object employee access and requires usage credits. The second bundles employee AI capabilities with unmetered usage when Salesforce's conditions are satisfied. Neither figure is a substitute for checking your existing CRM entitlement. Published employee options.

For a sales team whose main need is occasional record lookup, price the eligible access and consumption route first. For employees using specialized sales capabilities throughout their work, evaluate the add-on's included features and unmetering conditions. The cheapest access fee is irrelevant if it cannot license the action the rep needs.

The Coworker license is another distinct offer. Its included searches and indexing allowance should be evaluated against an employee search requirement; do not read its seat price as a blanket allowance for every autonomous sales workflow.

Unmetered depends on who runs the task

Salesforce's metering rules require the Unmetered User-Based AI permission and execution as the current user for global unmetering. The eligible rows specify Standard or Admin users and qualifying employee-agent or AI features. Scheduled work and work running as the Automated Process User are metered. Data services can still consume credits.

For example, an eligible rep launching an AI feature under their own identity can qualify for unmetered usage. Moving similar work into a scheduled background job changes the billing treatment. Check the implementation before projecting seat-license savings across automated work.

Salesforce also states a limit of 30 model calls per minute per user for unmetered usage, while noting it is not currently technically enforced. Treat that as a documented condition, not permission to run unlimited background automation through a person's license.

Agentforce for Service: Which Editions Are Prerequisites?

Prerequisites depend on the agent and licensing route. A service team should establish eligibility before comparing credit prices.

For Flex Credits, Salesforce's current usage article requires Foundations. With add-on access, it says to activate Foundations and names Enterprise, Performance, Unlimited or Developer Editions. With an Agentforce 1 Edition, it says Foundations is already included and active.

The Service Agent considerations page separately lists Lightning Experience and Enterprise, Performance, Unlimited or Developer Editions, with add-on requirements varying by agent type. A supported edition alone is not a complete license checklist.

Sales prerequisites are also specific: the Agentforce Engagement billing page names Enterprise, Performance and Unlimited with Sales and Einstein for Sales.

There is a naming wrinkle worth taking to procurement. The live commercial Sales and Service pages use Core, Advanced and Max, while these Help pages retain older edition names. The Sales pricing page says AI can be added to Core and above. Ask Salesforce to map your actual order-form edition to the agent's documented entitlement; do not infer that renamed tiers automatically include every legacy add-on.

Is Agentforce Free Through Salesforce Foundations?

Foundations is a free add-on for eligible existing Salesforce customers, with limited consumption allowances. It is a way to begin evaluating agents without purchasing a new Agentforce credit package immediately, not a perpetual unlimited agent service.

The Foundations page currently shows two different allowance descriptions. Its feature cards advertise 450,000 Flex Credits combined for Agentforce and Data 360, subject to restrictions. Its FAQ still describes 200,000 Agentforce Flex Credits for testing use cases and proofs of concept. Do not add those figures together or assume the combined headline is an Agentforce-only recurring allowance. Confirm the credited products, expiry and available balance in your order details and Digital Wallet.

Salesforce's separate Foundations eligibility page lists Enterprise, Unlimited, Einstein 1 Sales and Einstein 1 Service, across supported Sales, Service and Industries subscriptions. Its wording differs from the Flex Credits prerequisite article, another reason to confirm the specific route for your org.

An eligible company may never need an additional Agentforce purchase if it limits itself to a small evaluation, stays within its granted allowances and stops there. A recurring production workload needs a consumption budget even if its initial testing fits inside the free allocation.

Salesforce Pricing Calculator: Estimate Agentforce From the Work

At list price, the calculation starts with $0.005 per Flex Credit. That is $500 divided by 100,000. Multiply each usage type by its rate-card multiplier, then apply your contracted credit price. Salesforce also provides an Agentforce ROI Estimator, but its result depends on the workload you enter.

Order-status requests: Salesforce's $120 example

Salesforce's own pricing example uses two actions to authenticate a customer and retrieve an order. At 20 credits per action, each request consumes 40 credits, worth $0.20 at list price. Its assumed 20 requests per day over 30 days produce:

2 actions × 20 credits × 20 daily requests × 30 days = 24,000 credits = $120.

Those inputs and the result come from Salesforce's published example. The interpretation is what matters: this is the action-consumption component of a small order-status workflow, not a quote for an entire service deployment. Additional data and other consumption services are excluded.

The action-versus-conversation crossover

One $2 conversation equals 20 standard production text actions at $0.10 each. This is our arithmetic using Salesforce's listed rates, with no assumed customer volume or negotiated discount.

Below that action count, the action component is numerically cheaper. Above it, the flat conversation component is numerically cheaper. That comparison only helps if both routes support the intended workload and the relevant contract is available; it excludes other charges and says nothing about resolution quality.

Salesforce says Flex Credits and Conversations cannot operate as pricing models in the same org. You cannot simply choose the cheaper meter for each incoming interaction. Model the overall workload, and ask the account executive about the required SKU swap if you already buy Conversations. Pricing FAQ.

Employee case management: when the seat fee is harder to justify

Salesforce's case-management example assumes 100 users, each handling three cases per day across 20 working days, with three actions per case. It produces 360,000 credits and $1,800 per month, or $18 per user in action consumption. Published case-management example.

For comparison, 100 add-on seats at $125 total $12,500 per month. That does not prove the add-on is poor value: it includes other AI capabilities, and the metered route still needs appropriate underlying licenses. It does show why buying an unmetered add-on solely to cover this light workload needs justification.

The narrow consumption crossover is 1,250 eligible standard actions per user per month, calculated as $125 ÷ $0.10. Use that as a discussion point for already licensed employees, then account for included features and execution conditions. Avoid treating the $5 limited-object license as an equivalent replacement for a full sales or service seat.

What Can Increase the Bill Beyond the Headline Rate?

Testing, data processing, contract commitments and execution context can change the spend before customer traffic grows. Include them in the pilot budget.

Salesforce says creating an agent in Builder is unmetered, but chat and voice previews, Testing Center runs and other validation are metered. Sandbox does not mean free: the current rate card has separate sandbox multipliers. Agentforce Grid usage is metered across lifecycle stages. Development and testing billing.

Data 360 work can remain chargeable when the AI interaction is unmetered. Ask which data usage types your retrieval, indexing and processing will invoke. The current Flex rate card also covers other services, including speech processing and Slackbot, so an agent-action estimate should not silently stand in for every connected product's consumption.

Voice needs its own confirmation. Salesforce lists Voice Actions, but its Help documentation describes Voice Minutes for a limited eligible customer group. When enabled, minute billing takes precedence for that activity. Get the applicable voice subscription and any telephony costs quoted before using an action-only estimate.

Agentforce Vibes Pricing Uses a Separate Development Workload

Agentforce Vibes, Salesforce's AI development tooling, can consume Flex Credits or use an unmetered developer option. Its licensing guidance ties metered usage to the selected model's prompt category and token blocks. That page does not publish a dollar price for the unmetered option; request a quote.

If developers draw on the same credit budget used for the service pilot, separate that consumption in the forecast. A bigger development bill does not necessarily mean customers are using more service-agent actions.

Pre-Purchase, PayGo and Pre-Commit Change the Commitment

Salesforce describes Pre-Purchase as paying upfront for a fixed amount of usage over the contract term. PayGo has no upfront commitment and bills monthly in arrears. Pre-Commit establishes a baseline commitment, bills monthly in arrears and includes a term-end true-up if consumption falls short. The live page still labels broader Pre-Commit availability as later in the year, so confirm availability rather than assuming it. Buying models and FAQ.

PayGo and Pre-Commit are Flex Credit buying models, not alternative monthly subscriptions for the employee add-ons or Conversations. A price expressed per user per month also does not guarantee a cancellable monthly contract; Sales and Service Max explicitly bill annually.

Unused Flex Credits expire instead of rolling into the next subscription term. If you exceed your entitlement, Salesforce states that the contracted rate applies, billed monthly in arrears, without an overage penalty. Digital Wallet alerts help monitor usage, but a threshold notification should not be your entire spend-control plan.

Which Route Should an Existing Salesforce Customer Pick?

Choose the route after identifying the job, the eligible users and the billable unit. For customer self-service, compare action-based usage with Conversations or the product-specific Help Agent resolution route. For employee assistance, check existing entitlements before buying seats. For scheduled automation, forecast metered consumption even if employees have unmetered licenses.

Prefer a smaller consumption commitment while the action count and data workload are unknown. Consider employee add-ons when the licensed capabilities matter and recurring eligible use supports the fee. Consider Max when the wider edition bundle fits your business; its annual credit allowance belongs to the org, not to each licensed user.

For comparisons with non-Salesforce agents, use our AI customer-service tools comparison.

1. 1

   Name the exact pilot

   Choose a concrete workflow, such as order status or employee case summaries. Record its channel, agent type, required actions and whether work runs as a person or in the background.

2. 2

   Get the entitlement mapped

   Give the account executive your current edition and assigned licenses. Request the required additions, included allowances, applicable meter, annual commitment and any feature-specific exceptions in writing.

3. 3

   Measure consumption before expanding

   Track pilot actions, prompts, testing and data usage in Digital Wallet. Compare that observed mix with the published examples, then price the rollout using your contracted rates.

Agentforce Pricing FAQ

How much does Agentforce cost?

Salesforce lists Flex Credits at $500 per 100,000 and Conversations at $2 each. Employee options include the $5 access license requiring credits, $50 Coworker license, $125 cloud add-ons, $150 Industries add-ons and Max editions from $550 per user per month. The table above separates those fees from their usage conditions.

Is Agentforce free?

Salesforce Foundations is a $0 add-on for eligible customers with limited credits. Salesforce's current Foundations page uses both a combined Agentforce/Data 360 allowance headline and an Agentforce-specific FAQ allowance, so confirm your actual entitlement. Ongoing usage beyond included credits is chargeable.

What is the difference between Salesforce and Agentforce?

Salesforce provides the broader CRM and business-software platform. Agentforce is its AI-agent offering within that ecosystem. Having a Salesforce subscription does not by itself establish which Agentforce features, employee licenses or usage credits your company owns.

Why is Salesforce so expensive?

For an Agentforce project, the cost can combine an existing CRM subscription, specialized employee add-ons, metered agent work and data services. Separate existing spend from incremental project costs, then ask which additions are required for the exact workflow. A headline credit rate is only one part of that calculation.

If you need help turning the pricing decision into a scoped service-agent implementation, explore AI customer-service development.