Salesforce Agentforce License Cost: What Admins Need to Know

TL;DR: Agentforce is priced on a conversation-consumption model, not per-seat. Capacity allocations appear as Permission Set Licenses in your org. Waste looks different here — it's over-provisioned capacity and PSL assignments on users who never activated the feature, not just inactive login counts. Audit both before your renewal.

If you've logged into Setup lately and noticed new license types appearing under Company Information — “Agentforce,” “Einstein AI,” “Agentforce Platform” — you're not alone. Salesforce began rolling out Agentforce broadly in late 2024 and accelerated through 2025, and with it came a new licensing model that behaves differently from anything in a standard Salesforce contract.

Understanding that model matters before your next renewal. Agentforce costs can compound in ways that per-seat licenses don't, and the standard inactive-user audit only catches part of the waste.

How Agentforce Licensing Is Structured

Traditional Salesforce products — Sales Cloud, Service Cloud, Experience Cloud — are priced per user per month. Agentforce is different. It uses a consumption-based model where the unit is a conversation, not a seat.

A “conversation” in Agentforce terms is typically a session where a user or customer interacts with an AI agent — a service deflection chatbot, a sales assistant, an internal ops helper. Each resolved or attempted conversation draws down from your purchased conversation pool.

Salesforce sells Agentforce conversation capacity in volume pools. Pricing varies by edition, volume commitment, and contract terms — list rates for individual conversations have been published at ranges that scale down with volume. Your actual rate depends on what your AE negotiated when the SKU was added to your order.

The two layers of Agentforce cost

When Agentforce appears on a Salesforce contract, there are typically two things being purchased:

• Conversation capacity — the pool of agent interactions your org can run per year or per month, priced at a per-conversation rate
• Platform access / Permission Set Licenses — entitlements that allow specific users to build, configure, and administer agents in Agent Builder, or that unlock Agentforce capabilities within specific clouds

The second layer is where admins most commonly see waste: PSL assignments to users who were granted access during a pilot, never activated the feature, and are still occupying a licensed slot months later.

Why New License Types Are Appearing in Your Org

If you opened Setup → Company Information → Permission Set Licenses recently and saw Agentforce-related SKUs you don't remember purchasing, there are a few likely explanations.

1. Salesforce included Agentforce capacity in your renewal without explicit line-item visibility

Starting with some 2025 renewal cycles, Salesforce began bundling limited Agentforce conversation capacity into certain Enterprise and Unlimited editions as an included entitlement. These show up in Company Information as available licenses even if you didn't explicitly add them as a paid line item.

This is worth verifying: pull your current contract and compare the SKUs listed there against what appears in Setup. If you see Agentforce licenses that aren't in your contract, they may be provisioned as a trial or included bundle — and Salesforce may attempt to convert that usage into a paid renewal line at your next negotiation.

2. Your AE added Agentforce during a mid-term upsell

Agentforce has been a top expansion motion for Salesforce AEs throughout 2025 and 2026. If your org went through any mid-year business review, pilot, or product demo, it's common for conversation capacity to be provisioned as part of a trial or small add-on — sometimes before procurement fully understands what was agreed.

Check your Order Form amendments alongside the Company Information panel. Anything provisioned that isn't on a signed order is a conversation to have with your AE before the next renewal anchor is set.

3. Einstein and Agentforce PSLs are bundled with other products

Several Salesforce product suites — Sales Cloud Unlimited+, Service Cloud Unlimited+, Einstein 1 editions — include Einstein and Agentforce PSL entitlements as part of the base package. If your org recently upgraded tiers or renewed into a new bundle, these PSLs appear automatically and can be assigned to users without a separate purchase step.

They're still trackable as assignments. The fact that a PSL came bundled doesn't mean it's free to leave assigned to 40 people who never use it — at renewal, Salesforce will use that utilization data to argue you need more capacity, not less.

How Agentforce Waste Is Different From Standard PSL Waste

The standard PSL waste pattern is straightforward: a user is assigned an Einstein or Revenue Intelligence PSL, stops logging in, and the assignment stays active. Multiply dormant assignments by per-unit cost and you have a recoverable number.

Agentforce waste has two forms, not one.

Form 1: Over-assigned PSLs (the familiar pattern)

Agentforce platform PSLs — the ones that let users build and manage agents — follow the same dormancy pattern as Einstein PSLs. Run the standard PSL audit query against Agentforce-labeled licenses:

SELECT
  psla.Assignee.Name,
  psla.Assignee.Username,
  psla.Assignee.IsActive,
  psla.Assignee.LastLoginDate,
  psla.PermissionSetLicense.MasterLabel,
  psla.CreatedDate
FROM PermissionSetLicenseAssign psla
WHERE psla.PermissionSetLicense.MasterLabel LIKE '%Agentforce%'
   OR psla.PermissionSetLicense.MasterLabel LIKE '%Einstein%'
ORDER BY psla.Assignee.LastLoginDate ASC NULLS FIRST

Filter for users who haven't logged in for 60+ days. These are your over-assigned Agentforce PSLs — the ones you can reclaim before renewal.

Form 2: Over-purchased conversation capacity

This is the harder one. Unlike per-seat licenses, there's no simple “who isn't logging in” query for conversation pools. You need to compare your purchased conversation volume against actual consumption from your Agentforce analytics dashboard or the BotSession object in your org.

If you purchased 50,000 conversations annually and consumed 8,000, you have a structural over-purchase that needs to surface before your AE sets the renewal anchor. Unused conversation capacity doesn't roll over — it expires, and your AE will use the “you bought 50K” baseline to justify renewaling at the same or higher volume.

What to Audit Before Your Next Renewal

The same license management framework that applies to your core Salesforce estate applies to Agentforce — you just need to add two steps.

Step 1: PSL dormancy audit (same as Einstein)

Run the query above. For any Agentforce or Einstein PSL assignment where the user hasn't logged in for 60+ days, flag it for reclamation. Pull the per-unit cost from your contract and calculate the annualized waste per dormant assignment.

Step 2: Conversation consumption audit

Pull 90 days of conversation usage from Agentforce Analytics or via SOQL on theBotSession object. Calculate your monthly consumption rate and project it annually. Compare against your purchased volume. If you're running at <50% of purchased capacity for 3+ months, that's your negotiation lever.

Step 3: Contract vs. provisioned reconciliation

Print the Agentforce and Einstein rows from your signed Order Form. Open Setup → Company Information → Permission Set Licenses and find the matching rows. Verify that provisioned volume matches contracted volume. Discrepancies in either direction — provisioned more than you contracted, or contracted more than you can find — need to be resolved before your next renewal conversation.

What to Watch for at Renewal

Agentforce renewal conversations are different from standard seat renewals in a few specific ways.

Volume ratchet clauses

Some Agentforce contracts include automatic volume escalation tied to usage. If your consumed conversations cross a threshold, the agreement may auto-expand into the next pricing tier. Read your Order Form carefully for any auto-escalation or minimum commitment language. If it's there, your AE will cite any usage spikes (even one month's peak) as evidence you need the higher tier at renewal.

Baseline anchoring from trial capacity

If Agentforce capacity was provisioned as a trial or bundled inclusion, Salesforce's renewal playbook often converts that to a paid line at the same volume. Counter this with actual consumption data. If you used 10% of trial capacity, that's the starting point for your purchased volume — not the trial allocation.

Platform PSLs bundled into seat upgrades

AEs frequently propose renewal packages that “right-size” your base edition to one that includes Agentforce PSLs as a bundle. The per-seat price looks comparable, but you're now committed to paying for Agentforce capacity whether or not you build agents. Before accepting a bundle, ask for an itemized version so you can evaluate the Agentforce component separately.

Agentforce for specific clouds vs. Agentforce Platform

Salesforce sells Agentforce in cloud-specific variants (Agentforce for Service, Agentforce for Sales) and as a standalone platform SKU. If you're being upsold from a cloud-specific variant to the full platform, understand what the expanded scope actually buys you — and whether you have the admin capacity to build against it. Unused platform entitlements become renewal leverage for your AE, not for you.

Connecting Agentforce to Your Existing Audit Workflow

If you're already running regular license audits on your Salesforce estate, adding Agentforce is an extension of the same process — not a separate one. The same pattern applies: pull current assignments, compare against actual usage, calculate waste, bring data to the renewal table.

The difference is that Agentforce requires a second data source (conversation consumption) that traditional license audits don't touch. Building that into your regular audit cadence — ideally starting 90+ days before your renewal — gives you the trend lines you need to negotiate from a position of actual data rather than Salesforce's utilization summary.

Salesforce's AE team is well-trained on Agentforce expansion conversations. By the time they bring you a renewal quote with Agentforce volume baked in, they've already decided what number they want. Your job is to have a different number ready — one built on 90 days of your actual consumption data, your dormant PSL count, and your real utilization rate.