Skip to content
Salesforce & AI

Agentforce Pricing in 2026: Which Model to Pick

August 7, 2026 · 7 min read · Updated October 30, 2026

A $5 user licence, a $125 employee add-on and a $2 conversation are three different purchases. Comparing their headline prices without checking the covered workload can produce a budget that looks precise and misses most of the bill.

Checked 30 October 2026. Salesforce lists Flex Credits at $500 per 100,000, conversations at $2, and several employee licence options. Standard actions use 20 credits; voice actions use 30. At that credit price, those are $0.10 and $0.15 respectively. These are list-price reference points, not a quote for an entire deployment.

Choose the workload before the licence

For an external support agent, compare eligible conversation billing with consumption billing. For an employee assistant, identify the users and the specific Sales, Service or Field Service entitlement. The $5 Agentforce User License requires Flex Credits. The $125 employee add-ons provide a different scope of usage; they do not make every integration, data service or external agent free. Industry and Max offers have separate prices and entitlements.

Conversation billing remains a current customer-facing offer. Salesforce says it cannot coexist with Flex Credit pricing in the same org. Ask how a switch affects existing agents before choosing a cheaper-looking model for one new workflow.

Model my Agentforce cost with TechParrot

An illustrative monthly estimate

Suppose a support agent handles 1,000 conversations. Each uses six standard billable actions, with no voice. At list, 6,000 actions consume 120,000 credits: $600. The $2 conversation alternative would be $2,000 for an eligible deployment. This is arithmetic for a fictional workload, not a measured customer result or a promise that six steps always mean six billable actions.

Now assume only 700 of those conversations are resolved without a person taking over. The consumption cost is about $0.86 per autonomous resolution before data services, licences and implementation. That measure is more useful than celebrating a low cost per conversation when many conversations still require a support agent.

The familiar twenty-action crossover is only $2 divided by $0.10. It stops being a useful rule as soon as you mix different action types, retries, voice or different contractual rates. A screen-by-screen process map is not a billing statement: use observed consumption from a representative pilot.

What the pilot should measure

Choose routine cases, ambiguous cases and cases the agent must refuse. For each, record the outcome, escalation, repeated attempts, elapsed time and wallet consumption. Keep rejected or failed attempts in the sample. Set a spend threshold and an owner who can stop the rollout when behaviour changes. Review the actual usage types in Digital Wallet rather than assuming every model call has the same price.

Budget separately for Salesforce base licences, relevant data-service operations, channels and integrations, implementation and ongoing evaluation. Foundations can support exploration, but verify the actual assigned allowance; do not plan from an unverified free-credit figure. Agentforce Vibes has its own developer billing considerations if code generation is part of the project.

Ask for these answers in the quote

Write down the exact SKU, users and workloads covered; the rate card and commitment model; what happens at the allowance boundary; and who owns monitoring. Add acceptance criteria for permission failures, handoffs and unwanted writes. A budget is ready when the commercial terms and the tested workflow describe the same thing.

Discuss an Agentforce implementation with a defined scope, a measured pilot and a rollback plan.

Work out your actions-per-resolution before you sign

Compare eligible licences, usage and operating costs against your real case mix. We will help define a measurable pilot before you commit.

Four fields, no call required. We reply within one business day.


Frequently asked questions

Is Agentforce still $2 per conversation?

Yes. Salesforce currently lists conversation billing for customer-facing agents. It is an available buying model, not merely a discontinued or legacy price. Confirm eligibility and contract terms for your deployment.

Is the $5 Agentforce User License all I need?

No. The $5 per-user monthly licence requires Flex Credits. It is different from the $125 Sales, Service and Field Service employee add-ons. Confirm your base licences and which usage the purchased SKU covers.

Do Flex Credits and conversation billing work together?

Salesforce currently says an org cannot use both conversation pricing and Flex Credits at the same time. Model the options before choosing or switching, and confirm migration terms with your account team.

Does twenty actions always equal a $2 conversation?

Only in a simplified example where every billable action costs $0.10. Voice and other usage types have different multipliers, and an unsuccessful attempt may still consume usage. Compare measured cost per resolved case, including retries and handoffs.

Ready to Take the Next Step?

Book a free strategy session with TechParrot's certified Salesforce consultants and product engineers.