Salesforce Agentforce Pricing: The Full Cost Breakdown

Created time

Jul 11, 2026 11:25 AM

Title length (<60)

Author

Mike Heap

Last optimised

Ecomm?

How does Salesforce Agentforce pricing actually work?

⚡

TL;DR: Three pricing meters run in parallel: $500 per 100,000 Flex Credits charged per action, $2.00 per conversation, or a per-user license from $5 to $550 a month. Every one of them sits on top of a Service Cloud seat you also pay for.

Agentforce sells three ways at once, and they don't cost the same for the same work.

The headline consumption model is Flex Credits: $500 buys 100,000 credits, and you spend them per Action. That works out to $0.005 a credit, so a standard 20-credit action is $0.10 and an Agentforce Voice action (30 credits) is $0.15.

The older model, and the one everyone still quotes, is Conversations at $2.00 each. But that's customer-facing agents only, and it's sold on just one buying model. On top of those two consumption meters sit three per-user licenses that range from $5 to $550 a user per month.

The Salesforce Agentforce pricing page showing the Salesforce Foundations, Flex Credits and Conversations plans, each ending in Contact us

And underneath all of it, every human still working the queue needs a Service Cloud seat. That last line is the one buyers forget.

This is the bit I end up walking people through on calls. Salesforce's own worked examples model a support case at three actions, the obvious kind: look something up, summarize it, update the record. Three actions on Flex Credits is 60 credits, or $0.30 a ticket.

That identical customer-facing ticket, bought on the Conversations SKU, is $2.00. That's a ~6.7x spread on the same work, and the only variable is which line your AE put on the contract.

It's the arithmetic most buyers never get walked through, which is why so many think the product costs $2 a ticket when, on the model Salesforce now leads with, it can cost 30 cents.

Four statistics: a Flex Credit costs $0.005, a standard action costs 20 credits, a three-action ticket costs $0.30, and the same ticket costs 6.7 times more on the Conversations SKU

The whole pricing picture on one screen, worth a screenshot before your next procurement call:

Component	Price	How it's billed	Notes
Salesforce Foundations	$0	—	Free entry point (Agent Builder, Prompt Builder, Agent Script, Agentforce Coworker, Vibes). Enterprise Edition or above only.
Flex Credits	$500 / 100,000 credits	per Action	= $0.005/credit. Standard action 20 credits ($0.10); Voice action 30 credits ($0.15). Buying-model flexible. Unused credits do not roll over.
Conversations	$2.00	per conversation	Customer-facing agents only. Pre-Purchase buying model only. Runs from the agent's first response until resolved and closed, or 24 hours of inactivity, whichever comes first.
Agentforce User License	$5 / user / mo	per user	"Requires Flex Credits" — cannot be bought on its own. Metered employee usage, limited CRM objects.
Agentforce add-on	$125 / user / mo	per user	Sales / Service / Field Service. Unmetered employee agent usage.
Agentforce Industries add-on	$150 / user / mo	per user	Industries Clouds; includes the Sales and Service add-ons.
Agentforce 1 Editions	from $550 / user / mo	per user	Add-on included + 2.5M Flex Credits per org per year.

Salesforce is precise about what an Action is, and I'd read their definition closely, because the whole Flex Credit bill turns on it:

"Each Action — a specific function that an AI agent executes on the platform, such as updating a record, summarizing a complex case, answering a product inquiry, or executing a custom prompt or flow — draws from a pool of Flex Credits."

Every "specific function" is a meter tick. A ticket that needs the agent to check an order, summarize the history, and post an update burns three of them.

Agentforce has cycled through three pricing models in eighteen months: $2 per conversation at launch in late 2024, Flex Credits in May 2025, then the per-user add-ons later in 2025. As SaaStr covers it, that churn is Salesforce iterating on its pricing fast in response to how the market reacted. But it also means the "price" you find in a blog post from six months ago is probably describing a model Salesforce has since moved on from, which is half the reason this category is so confusing to shop.

What are you actually paying for in each Agentforce line item?

⚡

TL;DR: The cheapest-looking line on the page, the $5 user license, cannot be bought on its own: it says "Requires Flex Credits". The Service Cloud seat underneath is the line that actually moves the bill.

Every consumption row on that pricing page has a surprise buried in it. Let me take each one with the vendor's own definition and where the meter bites.

Three common misreadings of Agentforce pricing set against what the contract actually says

Flex Credits: $0.005 a credit, but you're billed per action

Flex Credits are the model Salesforce now leads with, and on paper they're the reasonable one: $500 per 100,000 credits, a standard action metered at 20 credits ($0.10), a Voice action at 30 ($0.15). Sandbox actions run in the Testing Center at 16 credits, so you can rehearse a little cheaper than you run.

It all turns on the word "action". Billing follows each function the agent executes, so one ticket can spend several, and Salesforce's own Service (Case Management) example assumes three actions per case ($0.30).

So if your agent needs five actions to handle a complex case, that ticket is $0.50; if a workflow fans out to eight, it's $0.80. You're effectively signing up to a meter whose rate depends on how chatty your agent's internal plumbing is, which isn't something a CX buyer can forecast from a demo.

And unused Flex Credits don't roll over, so if you over-buy a quarter, that capacity just evaporates.

Conversations: the flat $2.00, and the 24-hour clock

The Conversations SKU is the one everybody still quotes: $2.00 per conversation, customer-facing agents only. A "conversation", in the definition ecosystem consultants have documented, runs "from the AI agent's first response until the issue was resolved and closed… or after 24 hours of inactivity, whichever came first." So one back-and-forth thread is one $2 charge, however many messages it contains (a 40-message epic and a two-message ping cost exactly the same).

Buyers often worry that per-conversation pricing will spiral on long chats, picturing one customer who won't stop typing and racking up a huge bill. Having watched a lot of locked-down business agents run, I'd gently retire that fear: a support agent constrained to your knowledge and your tasks isn't ChatGPT, and only a tiny fraction of conversations ever run into the tens of messages.

The trouble with the Conversations SKU is the flat rate itself: $2.00 for a thread that would cost $0.30 in actions on the Flex model is the 6.7x gap again, and it's baked in from the first message.

Agentforce User License: the cheapest line that can't be bought

The $5-per-user-per-month Agentforce User License looks like the entry point, and it isn't one. The page carries three words next to it, "Requires Flex Credits", which means you can't buy it on its own (this is the line I see mis-read on quotes most often).

It's a metered employee-facing license that draws down a Flex Credit pool and touches a limited set of CRM objects. So if you're eyeing the $5 line as your way in, I'd read it as "$5 plus a credit balance you also have to fund."

Agentforce add-on and Industries add-on: the unmetered employee route

The $125-per-user-per-month Agentforce add-on (for Sales, Service, or Field Service) is the flat-rate alternative for employee-facing agents: unmetered usage, so your internal team can lean on it without watching a credit meter. The Industries add-on is $150 and folds in the Sales and Service add-ons.

These are the SKUs to look at if the use case is agents helping your own staff rather than resolving customer tickets. The economics flip from per-action to per-seat.

Agentforce 1 Editions: $550 a user, with credits included

At the top, Agentforce 1 Editions start at $550 per user per month, bundle the add-on, and include 2.5 million Flex Credits per org per year. For a large deployment, that bundled pool is the number I'd anchor on. At 2.5M credits, you've got roughly 125,000 standard actions a year absorbed into the seat price before consumption charges start.

It's the one place Agentforce pricing stops feeling like a taxi meter.

The Service Cloud seat underneath, the line the buyer misses

One line item turns a reasonable-looking AI quote into a big one. Agentforce always sits on top of Service Cloud, and Service Cloud seats are billed per user per month, annually: Enterprise $175, Unlimited $350, Agentforce 1 Service $550. The Starter Suite ($25) and Pro Suite ($100) don't include Agentforce at all, so you can't bolt it on down there.

The Salesforce Service Cloud pricing page showing Starter Suite $25, Pro Suite $100 and Enterprise $175 per user per month

I say this on every pricing post and it's never once been wrong. Count the whole stack, seats included. The $0.10 action is not the big line.

Twenty agents on Enterprise seats is $3,500 a month before the AI has answered a single ticket, and that number tracks the size of your human team. Automating more tickets doesn't shrink it. When a buyer tells me Agentforce came in far higher than the "$2 a conversation" math suggested, the seat stack is almost always where the surprise lived.

What does Agentforce cost at typical volumes?

⚡

TL;DR: At 10,000 tickets a month with 20 agents, Flex Credits land near $6,500 a month all-in. The same volume on the Conversations SKU is about $23,500.

Now the calculator. Let me lay out the assumptions in plain sight so you can swap in your own.

I'm modeling three actions per support ticket, because that's what Salesforce's own Service worked example uses ($0.30 a ticket on Flex). I'm putting the human team on Service Cloud Enterprise seats at $175, at 5 / 20 / 50 agents for the three volume tiers. And I'm showing the AI charge on both consumption SKUs side by side, because that SKU choice is the biggest single lever on the bill.

Neither Agentforce SKU's bill moves with your resolution rate, which is what separates it from a true outcome-based pricing model. Flex Credits meter actions attempted, so the agent burns credits whether or not it lands the answer.

Conversations bill from the first response. You're charged the $2 the moment the agent replies (resolved or not). Both meters run on activity, so you pay whether the ticket succeeds or fails, and the AI's misses cost you too.

That's why I show the AI-charge columns below as flat regardless of how good your agent is. The resolution rate only changes the cost per resolved ticket: how much you paid for each ticket the AI actually closed.

I've anchored that on the ~70% field-median resolution rate from our AI resolution-rate benchmarks (195 rated deployments; the figure is an aggregate, directional not apples-to-apples, and self-selected, so take the number with a grain of salt), and shown a deliberately conservative 50% floor underneath.

Volume	Seats (Service Cloud @ $175)	Flex Credits AI charge	Conversations AI charge	Monthly bill (Flex)	Monthly bill (Conversations)	$/resolved @70% (Flex / Conv)
1,000 tickets · 5 agents	$875	$300	$2,000	$1,175	$2,875	$1.68 / $4.11
10,000 tickets · 20 agents	$3,500	$3,000	$20,000	$6,500	$23,500	$0.93 / $3.36
50,000 tickets · 50 agents	$8,750	$15,000	$100,000	$23,750	$108,750	$0.68 / $3.11

The math is deliberately simple so you can check it yourself: Flex = tickets × 3 actions × 20 credits × $0.005 = tickets × $0.30. Conversations = tickets × $2.00; seats = agents × $175.

And the $/resolved figure is just the monthly bill divided by the tickets the AI actually closed (70% of them).

A spectrum of AI resolution rates from 0 to 100 percent, marking a conservative 50 percent floor, the 70 percent field median, and a mature 95 percent rollout

At the conservative 50% floor, the bills don't change at all. Only the cost per resolved ticket climbs, because you're closing fewer of the tickets you already paid for: Flex lands at $2.35 / $1.30 / $0.95 across the three tiers, and Conversations at $5.75 / $4.70 / $4.35. That's resolution-rate independence in one line, and a worse agent costs you the same invoice at a higher price per win.

At 1,000 tickets a month (small team)

At the small end the seat stack dominates the Flex bill, with $875 of Service Cloud seats against a $300 AI charge. On Flex you're looking at about $1,175 a month all-in; on Conversations that jumps to $2,875, and the AI line is now the big one.

At this size the SKU choice already bites, and the “$2 a conversation” framing is the one I’d watch hardest. The same 1,000 tickets is $300 of AI or $2,000 of AI depending on the contract.

At 10,000 tickets a month (mid-market)

At mid-market volume the SKU choice drives the whole bill. Same tickets, same team, same product. That's $6,500 a month on Flex Credits versus $23,500 on Conversations.

That's a $17,000-a-month, $204,000-a-year decision that comes down to a single line on the order form. It's the number I'd want any mid-market buyer to walk into the room already knowing. The Flex effective rate here is a competitive $0.93 per resolved ticket; the Conversations rate, $3.36, is not, so I'd make that gap the headline of any procurement deck.

Video preview — I Let AI Agents Resolve 10,000 Support Tickets, Here's How Much It Cost

At 50,000 tickets a month (high volume)

At high volume the two models diverge hard. Flex Credits hold a low effective rate, $23,750 a month at about $0.68 per resolved ticket.

Conversations, at the same volume, is $108,750 a month. At that point you renegotiate.

If you're at this scale, the Flex model (and quite possibly an Agentforce 1 Edition where 2.5M credits are bundled into the seat) is the only version of Agentforce that makes financial sense.

What the Agentforce pricing page doesn't tell you

⚡

TL;DR: Five costs land after signature and never show up on the pricing page: unused Flex Credits expire, the SKU choice locks at signing, Conversations is Pre-Purchase only, implementation runs $50K to $150K upfront, and Data Cloud credits meter your data ingestion.

The sticker prices are only half the invoice. These are the line items I see show up after the signature, the ones that turn a clean quote into a surprise.

Four hidden Agentforce costs: expiring credits and true-ups, no mixing of consumption models, Conversations sold Pre-Purchase only, and implementation fees

Hidden cost 1: unused Flex Credits don't roll over, and Pre-Commit trues up against you

Flex Credits are marketed as the fix for the forecasting problem, but the fine print recreates it. Unused credits don't roll over (buy too many this quarter and they're simply gone), and on the Pre-Commit buying model, the live page trues up at term end if usage is below commitment. If you commit to a baseline and don't hit it, you pay the difference anyway.

I'd treat that true-up as the single number to negotiate hardest. It puts a price on how badly you forecast.

You're back to forecasting a meter you can't predict, which is exactly the pain the model claims to remove.

Hidden cost 2: you can't mix Flex Credits and Conversations in one org

You pick one consumption model per org. As Constellation Research notes in its Flex Credits explainer, you can't run some agents on Flex and others on Conversations under the same roof.

So the 6.7x SKU decision is one you commit to at signature. Realize later that you chose wrong and your only fix is to reopen the contract, which is exactly as painful as it sounds. (I'd model both SKUs before signing either one.)

Hidden cost 3: the Conversations SKU is Pre-Purchase only

If you do go Conversations, note that it's sold on Pre-Purchase only: you buy a block of conversation volume upfront, for the full term, before you've served a single ticket. That's the least flexible of the three buying models sitting behind the least flexible consumption SKU. You're forecasting twice: how many conversations, and how far in advance.

Hidden cost 4: implementation, and the systems-integrator dependency

Agentforce is not a switch you flip. One third-party consultancy that implements it pegs the build at $50K to $150K upfront plus $10K to $25K a month in ongoing services, and Salesforce's own executives have talked about the "deep, multi-day workshops with our top global systems integrators" the rollout needs, a dependency No Jitter covered at launch. Add it up and a realistic Year-1 all-in cost lands somewhere between $200K and $600K, most of which never appears on the pricing page.

Hidden cost 5: Data Cloud credits to feed the thing

Agentforce answers from your data, and getting your data in burns a separate meter, the Data Cloud / Data 360 credits charged as content is crawled and ingested. To put a number on the scale of it: Salesforce's own internal "Customer Zero" deployment ingested roughly 740,000 pieces of content to get its support agent working (fun fact). Your corpus won't be that big, but "load your knowledge base" is not a free step, and it's easy to leave off the budget.

These line items turn up mid-deployment, and they recur right across the category; we catalogued the pattern in the hidden costs of AI customer service.

And the meta-gotcha behind all of them: nothing above $0 is self-serve. Every real SKU on the pricing page ends in "Contact us", under a disclaimer that the page "is provided for information purposes only and is subject to change."

The one useful thing about that is bartering: Pre-Commit Flex rates and Conversations volume discounts are negotiable, and I've never seen the sticker be the floor. So don't treat any of these numbers as fixed until you've pushed on them.

What real Agentforce customers actually pay (and complain about)

⚡

TL;DR: Buyers rarely complain about the headline rate; they complain that it keeps changing. Agentforce has cycled through three pricing models in eighteen months, and admins say they still can't forecast the spend.

I went looking for what customers actually say about the Agentforce bill itself. The recurring complaint is about unpredictability. The rate keeps changing, and the whole thing is hard to forecast.

The $2-per-conversation launch is where the backlash started, and SaaStr captured the mood:

"The original $2/conversation model immediately priced out nonprofits, SMBs, and any organization without a large AI budget. Even enterprise customers called it unpredictable and disconnected from the real cost of serving AI actions."

I'd call that a brutal read on a flagship launch, and the analysts weren't softer. Valoir's Rebecca Wetteman, speaking to CX Today, noted that the two-dollar consumption rate had "scared a lot of people", which, for a flagship product's headline price, is a fairly remarkable thing to do to your own market.

The biggest cost people forget is the setup. Freelance Salesforce developer Peter Chittum, writing via Salesforce Ben, described the on-ramp like this:

"But all the blocking and tackling of getting an org ready for Agentforce, just to have it ready to create an agent, I have found fiddly and not well thought through in the setup experience."

That "fiddly" is the $50K to $150K implementation line I flagged earlier, in the words of someone who does this for a living. And the adoption numbers back him up: Salesforce Ben reports that of roughly 5,000 Agentforce deals closed by early 2025, only 3,000 were paying customers. The other 2,000 were still testing.

I read that split as the market pricing in its own uncertainty: plenty of teams wanted the agent, fewer were willing to sign a meter they couldn't forecast.

The r/salesforce pricing threads, as summarized in ecosystem write-ups, tell the story you'd guess from all of the above: proofs of concept that came back cost-prohibitive, and admins struggling to estimate usage well enough to justify the spend to a boss. When two in five closed deals are still kicking the tires, the pricing model is doing some of that hesitating for them.

Does Agentforce have a free trial, and what are the contract terms?

⚡

TL;DR: Salesforce Foundations gets you Agentforce for $0, but only if you're already on Enterprise Edition or above. The three buying models (Pre-Purchase, Pre-Commit, PayGo) decide how much you lock in.

There's a genuine $0 way in, with strings attached, plus three buying models I'd want you to understand before you sign.

The free tier is Salesforce Foundations: Agent Builder, Prompt Builder, Agent Script, Agentforce Coworker, and Agentforce Vibes, all for nothing, but only if you're already on Enterprise Edition or above. So if you're not on Enterprise, Foundations is more a perk for existing Salesforce customers than a real way in.

Beyond that, Developer Edition is free forever for building and testing, there's a standard 30-day Service Cloud trial, and the Agentforce Testing Center lets you rehearse agents in a sandbox where actions cost 16 credits, a small discount on the live 20.

The three buying models are what decide your lock-in, so slow down here:

The three Agentforce buying models: Pre-Purchase, Pre-Commit and PayGo, ordered from most to least committed

Pre-Purchase: "Buy a set amount of usage for the full contract term and pay upfront." It saves the most and is the only model available on the Conversations SKU. It's also the most committed: you forecast, you pay, you draw down.

Pre-Commit: commit to a baseline of Agentforce usage with no upfront payment, billed monthly in arrears, with a true-up at term end if usage is below commitment. The page notes it's "widely available later this year." Softer cash-flow, same forecasting risk (that true-up again).

PayGo: no upfront commitment. Pay only for what you use, billed monthly in arrears. The flexible one, and the one to start on if you can't yet predict your own usage.

Underneath, every Service Cloud edition above Starter is billed annually, and even the Pro Suite carries a "contract required" note. There is no month-to-month version of the seat stack. Whatever you sign for the humans is an annual commitment.

So I'd budget the seats as a fixed annual floor and treat the consumption meter as the only line you can still move.

How does Agentforce pricing compare to alternatives at the same volume?

⚡

TL;DR: At 10,000 tickets a month, Agentforce is roughly $6,500 on Flex Credits and $23,500 on Conversations. My AskAI runs about $1,299 with no seat fee, though it does not integrate with Salesforce.

So let's put the 10,000-ticket month next to the alternatives, using the same vocabulary as our breakdown of AI customer service pricing models. One structural difference separates these models. Agentforce and My AskAI both bill flat on the resolution axis (the invoice doesn't move as the agent improves), while Intercom Fin and Zendesk AI bill per resolution, so their bills rise as their AI gets better.

Paying more the better your automation gets is the trap I'd steer you clear of.

Vendor	Pricing model	Cost at 10k tickets (~70%)	Effective $/resolved
Agentforce (Flex Credits)	per action ($0.30/3-action ticket) + Service Cloud seats	~$6,500/mo (flat)	~$0.93
Agentforce (Conversations)	$2.00/conversation + Service Cloud seats	~$23,500/mo (flat)	~$3.36
My AskAI (Scale)	flat $0.10/ticket, no per-resolution charge, unlimited seats	~$1,299/mo (flat)	~$0.19
Intercom Fin	$0.99/outcome • Intercom seats (rises with resolution)	~$8,630/mo	~$1.23
Zendesk AI	~$1.50/automated resolution + Suite seats + add-on (rises with resolution)	~$13,500/mo	~$1.93

My AskAI at 10k tickets is the Scale plan: $499 base (which includes 2,000 credits) plus 8,000 more tickets at $0.10 each, so $1,299 a month, with unlimited team seats and no per-resolution charge. Because it's flat per-ticket, the bill doesn't move with your resolution rate; the effective cost lands at about $0.19 per resolved ticket at 70%, and it falls as your agent improves rather than rising.

That's the deliberate opposite of the outcome model: we bill on usage, so the upside from your own knowledge and tuning work stays with you. Our own pricing is broken down line by line if you want to check the math against this table.

Agentforce has one advantage the alternatives here can't touch. It runs natively inside Salesforce, with full CRM context and the ability to take Salesforce-native actions on your records.

If Service Cloud is your system of record, that native depth is the product, something a third-party agent bolted onto a different helpdesk can't replicate. My AskAI does not integrate with Salesforce.

We run inside five helpdesks (Zendesk, Intercom, HubSpot, Freshdesk, and Gorgias), and Service Cloud isn't one of them. If your support team lives in Service Cloud, we're not a substitute. Better you know that now than three weeks into a trial.

Where we do fit, you can prove it before you pay: the trial is 30 days, all features unlocked, unlimited tickets, no card. You can see what that looks like at volume in our high-volume AI support case study and this telehealth support rollout, and the rest sit in our case studies.

Is Salesforce Agentforce actually worth the money?

⚡

TL;DR: Worth it if Service Cloud is already your system of record and the CRM context is the product you're paying for. Not worth it if you just want an AI support agent and happen to be a Salesforce shop.

It comes down to one question: are you buying an AI agent that happens to sit on Salesforce, or are you buying Salesforce's CRM intelligence that happens to answer tickets?

✅

Salesforce Agentforce is worth it if:

Service Cloud is already your system of record, and the CRM context (full customer history, native actions on records) is where the real value sits.

You need the agent to do things inside Salesforce (update records, trigger flows), beyond answering from a knowledge base.

You're at Agentforce 1 Edition scale, where the 2.5M bundled Flex Credits absorb most of the consumption cost into the seat.

You have the systems-integrator budget for a $200K to $600K Year-1 rollout and the internal team to run it.

You want one vendor, one contract, and one throat to choke across CRM and support AI.

❌

It isn't worth it if:

You're SMB or mid-market: there's no Agentforce SKU on the Starter or Pro Suites, so the entry tiers are simply closed to you.

You want a price you can see and sign yourself; every real SKU here is "Contact us", and nothing above $0 is self-serve.

You can't forecast your volume confidently enough to commit to a Pre-Purchase block.

Your helpdesk isn't Salesforce: the native-CRM advantage that justifies the price evaporates the moment you're not on Service Cloud.

You want to pay only for outcomes: Agentforce bills for actions attempted and conversations opened, so you're paying for the tickets it fails on as well as the ones it lands (that's the resolution-rate independence again, cutting the other way).

If you've read this far and you're on Salesforce with the budget and the CRM use case, Agentforce is a serious, defensible buy, so go in on Flex Credits, barter the rate, and give the Conversations SKU a wide berth. If you're shopping an AI support agent and just happen to be a Salesforce shop, price the alternatives at your real volume first. For the full feature picture see our Salesforce Agentforce guide, and for what else fits your stack, the Agentforce alternatives breakdown.

FAQs

How much does Agentforce cost?

There's no single price. Agentforce sells three ways: Flex Credits at $500 per 100,000 credits ($0.10 a standard action, so roughly $0.30 for a 3-action support ticket), Conversations at $2.00 each, or per-user licenses from $5 to $550 a user per month.

Every one of those sits on top of a Service Cloud seat that runs $175 to $550 per user per month. At 10,000 tickets a month with 20 agents, Flex Credits land near $6,500 all-in; the same volume on Conversations is about $23,500.

Salesforce keeps a pricing help article that lists every SKU if you want the raw reference.

What is a Flex Credit and how many does one action use?

A Flex Credit is Agentforce's consumption unit, priced at $500 per 100,000 credits, so $0.005 each. A standard Agentforce action costs 20 credits ($0.10), an Agentforce Voice action costs 30 credits ($0.15), and a sandbox action in the Testing Center costs 16 credits. An "action" is any specific function the agent executes (looking up a record, summarizing a case, answering a question), so a single ticket usually spends several.

What is the Salesforce Agentforce $2 per conversation pricing?

$2.00 per conversation is Agentforce's original consumption model, still sold but only for customer-facing agents, and only on the Pre-Purchase buying model. A conversation runs from the agent's first response until the issue is resolved and closed, or until 24 hours of inactivity, whichever comes first. It's the most expensive way to buy the same work: a 3-action ticket that costs $0.30 on Flex Credits costs $2.00 here (about 6.7x more for the identical ticket).

What counts as a conversation in Agentforce?

Per Salesforce's definition, a conversation is the period from the AI agent's first response until the issue is resolved and closed, or after 24 hours of inactivity, whichever comes first. However many messages pass inside that window, it's one $2 charge. Note the meter starts at the agent's first response, well before any resolution, so you're billed whether or not the conversation ends successfully.

Do I need Service Cloud to use Agentforce?

Effectively yes. Agentforce runs on a Salesforce edition, and a Service (or Sales) Enterprise or Unlimited license is the practical prerequisite, since the free Foundations tier is only open to Enterprise Edition customers and above. The entry-level Starter Suite ($25) and Pro Suite ($100) don't include Agentforce at all, so there's no cheap Salesforce seat that includes it.

What does the Agentforce User License include?

The $5-per-user-per-month Agentforce User License is a metered, employee-facing license with access to a limited set of CRM objects. The important caveat is printed right next to it: "Requires Flex Credits." It can't be bought on its own. You also have to fund a Flex Credit pool for it to draw down, so treat the $5 as a floor you build on, with a funded credit balance on top.

How much does Agentforce for Service cost?

The Agentforce Service add-on is $125 per user per month for unmetered employee agent usage, on top of an Enterprise or Unlimited Service Cloud seat ($175 to $350). Customer-facing resolution is billed separately, via Flex Credits or the $2 Conversations SKU. So "Agentforce for Service" combines a seat add-on with a consumption meter, and there's no single number to quote.

How much does Agentforce for Field Service cost?

Field Service uses the same $125-per-user-per-month add-on as Sales and Service. Salesforce's own Field Service worked example assumes more actions per task than a support case, at five actions per appointment (100 credits, $0.50) in their model, so if you're metering on Flex Credits, budget for a higher per-request cost than the 3-action support case.

What is the difference between Flex Credits and Conversations pricing?

Flex Credits bill per action ($0.10 a standard action, roughly $0.30 for a 3-action ticket) and cover customer-facing, employee-facing, and Voice agents. Conversations bill a flat $2.00 per customer-facing conversation regardless of how many actions it takes. The same 3-action ticket is about 6.7x more expensive on Conversations, and you can't mix the two models in one org, so the choice is a real commitment.

Is there a free version of Agentforce?

There are three no-cost entry points, each with limits. Salesforce Foundations is $0, but only for Enterprise Edition customers and above; Developer Edition is free forever for building and testing; and there's a standard 30-day Service Cloud trial. None of them is a free production tier, though; the moment you're serving real customer tickets at volume, you're on the paid meters (I'd budget for that from the start).

What does Agentforce 1 Edition include at $550 per user per month?

Agentforce 1 Editions start at $550 per user per month, billed annually, and bundle the Agentforce add-on plus 2.5 million Flex Credits per org per year. For a large deployment, that included credit pool changes the math. Roughly 125,000 standard actions a year are absorbed into the seat price before consumption charges kick in, which makes the effective per-ticket cost at high volume much lower than buying credits à la carte.

Salesforce Agentforce pricing explained: what a ticket really costs on Flex Credits vs $2 conversations