Agentforce Pricing Models Explained: How to Choose the Right One for Your Organization

If you’re still building the internal case for Agentforce adoption, start with our companion piece: Agentforce Isn’t a Software Cost. Stop Budgeting It Like One.

Why did Salesforce change its Agentforce pricing in the first place?

When Agentforce first rolled out, the model was simple: $2 per conversation in a 24-hour window. It worked for early demos and light customer-chat use — but quickly showed its limits. 

A “conversation” could drag on, split across threads, or remain a single, simple question. The cost stayed the same regardless. Teams quickly realized the pricing didn’t reflect the actual value being created, and budgeting became a guessing game. 

The core question Salesforce had to answer: how do you price AI agents in a way that feels fair, predictable, and tied to real business value — without creating fear of runaway costs or unclear bills? 

Salesforce’s answer was to redesign Agentforce pricing around measurable work units and multiple flexible models. The goal: reduce complexity and get more of its 150,000+ customers onto the platform by giving them options that match how they work. 

What are the Agentforce pricing models available today?

Along with the original conversation-based model, Salesforce now offers several complementary options — each designed to align cost with how value is measured in different use cases. 

Salesforce Foundations is a free entry point. Teams can build basic agents and prompts and get free credits to test things beyond the basics, without paying anything upfront.  

Best for: Teams who want to try AI in Salesforce before spending money. 

Conversation-Based Pricing ($2/conversation) charges a flat rate each time a full interaction occurs between a user and an AI agent — regardless of whether it’s a simple question or a long back-and-forth. The price is the same either way.  

Best for: Simple customer-facing chatbots with short, predictable interactions. Note: Short questions can feel overpriced because they cost the same as complex ones. 

Flex Credits (pay-per-action) charges only when the agent actually does something useful. For instance, updating a record, summarizing a case, or routing a request. Also note that voice actions cost a bit more.  

Best for: Workflows where the amount of work varies a lot from task to task. Note: You can’t use Flex Credits and the $2 conversation model in the same org. Credits also expire at the end of the term. 

Per-User Agentforce Add-Ons ($125–$150/user/month) give each employee unlimited AI usage at a fixed monthly rate. The $150 tier adds industry-specific features.  

Best for: Employees like sales reps or support agents who use AI heavily throughout the day. 

Agentforce 1 Editions (from $550/user/month) bundle unlimited per-employee usage with a large org-wide annual credit pool into an all-in-one enterprise package. 

Related Add‑On Pricing 

Since Agentforce 1 Editions follow the per‑user structure, they align with Salesforce’s add‑on pricing: 

• Agentforce Add‑Ons — $125/user/month: Unmetered internal AI usage for Sales, Service, and Field Service teams.  

• Agentforce Industries Add‑Ons — $150/user/month: Industry‑specific AI capabilities with unmetered usage for regulated or specialized clouds. 

Best for: Large organizations that want predictable annual costs and don’t want to track usage line by line. 

Agentforce User License ($5/user/month) is a low-cost way to give basic AI access to a lot of employees. Usage is still metered through Flex Credits, but the license itself is affordable. 

Best for: Employees who use AI occasionally and don’t need unlimited access. 

How do you choose the right Agentforce pricing model?

There’s no single model that works for every use case, which is exactly why Salesforce introduced the options. A useful starting point is one simple question: is this agent built for customers or for employees? 

For customer-facing interactions: support chats, service requests, public-facing bots — conversation-based pricing or Flex Credits tend to fit best, since cost scales with real customer activity rather than internal headcount. 

For internal use: employee onboarding, internal ticketing, knowledge base queries, office workflows — per-user licenses or bundled plans keep costs steady and predictable without tracking every individual action. 

From there, it narrows quickly: 

• If the agent primarily handles customer conversations, the $2/conversation model is usually sufficient. 

• If the agent performs multi-step or variable work, Flex Credits align cost more closely with output. 

• If employees use AI heavily every day, a per‑user license, Agentforce Add‑On ($125/user/month), or Agentforce Industries Add‑On ($150/user/month) keeps spending predictable through unmetered internal usage. 

• If usage is occasional, the $5 user license paired with Flex Credits is the more cost-effective path.

How do you measure ROI on Agentforce investment?

Salesforce’s pricing philosophy is built on a straightforward premise: AI should do real work — work that humans would otherwise spend time and money on. That makes ROI relatively concrete to calculate. 

Agent ROI = (Value of work done – Cost of agent usage) / Cost of agent usage 

Value of work means the measurable outputs the agent produces: cases resolved without escalation, leads qualified, tasks completed without human involvement, hours saved. 

Cost is whatever you’re spending on Flex Credits or licenses to produce that work. 

But the basic formula only tells part of the story. A few other things worth tracking: 

• Cost per action vs. cost per conversation: compare spend against what the agent actually delivers, not just usage volume. 

• Efficiency over time: as agent design improves, cost per task typically decreases while total value increases. 

• Avoided costs: fewer escalations, faster SLA resolution, reduced error rates, and improved customer retention all contribute to ROI even when they don’t show up as direct savings. 

• Scalability: the ability to scale usage up or down without proportional cost increases is itself a form of value. 

What pricing mistakes should you avoid with Agentforce?

Choosing the right model is only half the battle. A few pricing mistakes come up repeatedly that can inflate costs regardless of which option you pick: 

No piloting: Usage forecasts built on assumptions rather than real test data almost always miss — sometimes badly. Running a contained pilot first gives you actual numbers to plan around. 

Poor agent design: Inefficient workflows trigger more actions than necessary, inflating spend. Fewer actions per outcome means lower cost — so design matters from day one. 

Unclear use case segmentation: Teams that don’t distinguish between customer-facing and internal use often pick the wrong pricing model for each scenario, which makes costs feel unpredictable even when they aren’t. 

Hidden add-on costs: Data integrations, voice features, and third-party connectors can add meaningful spend if not scoped upfront. These are easy to overlook in early planning and harder to absorb once a deployment is live. 

Where should you start with Agentforce?

The right starting point is simpler than it sounds after all these options.  

Pick one high-value use case, choose the pricing model that fits it, and run a pilot. Real usage data will tell you more about which direction to scale than any forecast will. It will also give you something concrete to bring back to leadership when it’s time to expand. 

The organizations that get the most out of Agentforce aren’t the ones who mapped out every pricing scenario upfront. They’re the ones who started somewhere specific, measured what the agent actually delivered, and built from there.

Need help getting started?