If you buy Agentforce Coworker at $50 per user per month, first get one answer in writing: do the actions Coworker takes still draw Flex Credits? Salesforce's November 4 release put the per-user option on sale, and its pricing page lists two usage allowances for the seat: all Coworker searches, and 30 MB of indexing per user per month. Actions appear nowhere in that entry. At list, the same $50 buys 10,000 Flex Credits, which is 500 standard actions at the 20 credits per action on Salesforce's rate card.
A 1,000-person rollout at that price is $600,000 a year, and the largest usage variable has no published answer. Salesforce says customers who want per-user pricing have to go through their account executive, so that conversation is where you settle it. Prices below were read on Salesforce's and Microsoft's live pages on November 9, 2026.
What Salesforce Put on Sale on November 4
Salesforce added a standalone seat and a release schedule that moves Coworker out of the Salesforce interface and into Microsoft Teams, phones and desktops. Coworker is the company's employee assistant: it answers plain-language questions across Salesforce data and connected sources, and it can call Agentforce agents and flows, then return finished work for approval.
| Status in the release | What it covers |
|---|---|
| Available at announcement | Per-user SKU, Google Workspace and Microsoft 365 connections, Conversation History, Skills |
| Listed for general availability in November 2026 | Coworker in Microsoft Teams, iOS app, Mac and Windows apps, Coworker MCP server, free trial for Flex Credits customers |
| Expected December 2026 | Scheduled tasks, Daily Digest, Coworker in the Field Service, Consumer Goods Cloud and Life Sciences Cloud mobile apps |
Martech Notes reported the same schedule on the day of the release. Salesforce also says pricing and packaging are subject to change, and its product page still points admins to a beta setup guide.
The adoption claims are Salesforce's own: more than 185,000 users and 21x usage growth in three months. The seat went on sale with that announcement, so the 185,000 mostly reflects other licensing and tells you little about demand at $50. Salesforce also began automatically enabling Coworker on a rolling basis on August 10 for customers with unmetered AI seats, so the three-month growth figure overlaps a default-on rollout. The release's customer detail is more useful. Fulton Bank has more than 20 use cases running for about 3,000 users, and The Adecco Group is expanding across 40 countries. Salesforce says BACA Systems enabled Coworker in an environment with 1,300 custom objects and got started in 20 minutes. We covered the original launch in May, before any of this packaging existed.
What the $50 Seat Includes and What It Omits
The Coworker entry says nothing about how agent usage is billed, while the two per-user entries around it on the pricing page are explicit.
| Option | List price | Published usage terms |
|---|---|---|
| Agentforce User License | $5 per user per month | "(Requires Flex Credits)", limited CRM objects, metered usage |
| Agentforce Coworker User License | $50 per user per month | "All Coworker searches included", "30 MBs of indexing per user per month" |
| Agentforce add-ons | $125 per user per month ($150 for Industries Clouds) | Unmetered employee usage |
| Flex Credits | $500 per 100,000 credits | 20 credits per Agentforce action |
A Flex Credit is Salesforce's consumption unit, worth half a cent at list, and an Agentforce action is a unit of work an agent performs, billed against that meter. When Salesforce introduced the model on May 15, 2025, it described the add-ons as "unmetered employee-facing agent usage in a simple per user per month (PUPM) pricing model." So the company has words for this and did not use them on the Coworker line.
Salesforce may well intend actions to be covered, in whole or up to a limit: the Coworker page sells the seat as "predictable per-user pricing," and a seat that metered every action would strain that phrase. The published pages do not commit to it either way.
The one document that might settle this is Salesforce's Billing Considerations for Agentforce Coworker. It returned a 403 error to our requests on November 9, so nothing here relies on it. Have an admin read it, and check whether it has been updated for the November 4 SKU. The rate card dated August 31, the newest we could find, has no Coworker row at all.
When the $50 Seat Beats Metered Credits
The seat beats the $5 license plus credits above about 450 actions per user per month, but only if the seat covers actions. That figure is $45 of credits at $0.10 each, or about 22 actions per working day. FourWeekMBA ran the simpler version of this comparison and arrived at 500 actions, which it called a list-price yardstick.
If actions are metered on top of the seat, the math runs the other way. The $75 gap between the $50 seat and the $125 add-on buys 750 actions at list, so a user above roughly 37 actions per working day would cost less on the add-on, where usage is explicitly unmetered. Our October breakdown of Agentforce costs put the add-on's break-even against the $5 license at about 1,200 actions a month, which still holds for users who never touch Coworker.
The metered path has its own gap. The August 31 rate card prices actions and prompts but gives no rate for a Coworker search, so you cannot fully price a heavy searcher on credits from the rate card alone. Your contracted credit price also moves every threshold here, and the pricing page itself warns that its examples exclude "Data 360 credits or other consumption services."
What 30 MB of Indexing Is Worth at List
The closest public yardstick values the 30 MB allowance at $22.50 per user per month, nearly half the seat price. Coworker is powered by Data 360, and the August 31 rate card charges 150 credits per megabyte for Data 360 Unstructured Processing at the base tier. Thirty megabytes is 4,500 credits. At the Tier 4 multiplier of 30, the same allowance is worth $4.50. At the 600-credit base rate for Data 360 Intelligent Processing, it is worth $90, more than the seat.
Salesforce does not say which of those rates, if any, maps to Coworker indexing, so treat all three as bounds on a guess. Its Coworker enablement FAQ, published August 5, says indexing content in Data 360 uses Flex Credits or Data Services Credits regardless of billing plan, but that page never mentions the $50 license or the 30 MB allowance. What you need from your account team is narrower: whether the 30 MB replaces that charge, whether it is pooled across the org or stranded per user, whether unused allowance carries forward (Flex Credits do not roll over), and what happens at 30.1 MB. Pooled, 1,000 seats is 30 GB a month. Connecting Microsoft 365 or Google Workspace file stores is the fastest way to find out whether that is enough.
Where Metering Can Come Back Into a Flat Seat
Three parts of the November and December schedule are the likeliest places for credits to reappear, because each one pushes Coworker past a search box.
Orchestration comes first. Coworker brings in Agentforce agents, flows and processes, and those agents carry their own per-action price when they run elsewhere. Ask whether an agent invoked from a Coworker session is billed differently from the same agent invoked directly. Scheduled tasks, expected in December, raise the same question with no human in the loop to notice the count climbing.
MCP is the third. Salesforce lists Coworker as reachable from Claude and ChatGPT via MCP, and the rate card has a Customer 360 Platform line for "Headless Platform Interaction" with the multiplier marked TBA. Salesforce has not said whether traffic through the Coworker MCP server counts as headless usage. An unpriced line on a rate card that "may be updated from time to time" is worth a clause.
Check what you already own, too. The pricing page lists Coworker among the features of the $0 Salesforce Foundations tier, and the Foundations page warns that "Data 360 and Agentforce functionality consumes credits when used." That page also gives two different allowances, 450k credits in its feature listing and 200K in its FAQ, so confirm yours on your order form.
Microsoft shows what a published line looks like. Its enterprise Copilot page lists the add-on at $30 per user per month on top of a qualifying plan and says licensed users "can use assistive custom agents at no additional cost." Its Copilot Business page names the experiences outside that line, including Copilot Cowork, Code and Autopilot, and says they "use Copilot Credits, so you pay based on actual usage." You may dislike that split, but you can budget for it. With Coworker arriving inside Teams, many buyers will be comparing the two on the same screen, and we have already seen how quickly bundled AI changes renewal math across these vendors.
What to Do Before You Sign
This Week:
- Send your Salesforce account executive one written question: "On the $50 Agentforce Coworker User License, which Coworker activities consume Flex Credits, Data 360 credits or Data Services Credits, and which do not?" Ask for the reply to cite the governing document.
- Have a Salesforce admin read the Coworker billing considerations page and save a dated copy, so you have a record if the wording changes.
- Pull the last 90 days of Flex Credits consumption and sort users into three bands: under 450 actions a month, 450 to 750, and above 750. If you have no per-user data, that gap is the first thing to fix.
This Month:
- When the free trial for Flex Credits customers reaches your org, run it with 25 users from one team and count actions, searches and megabytes indexed per user for two weeks.
- Connect one real Microsoft 365 or Google Workspace source during that pilot, then compare indexed volume against 30 MB per user. A pilot on Salesforce data alone will not tell you this.
- Have security review the Coworker MCP server before anyone connects Claude or ChatGPT to it. Salesforce says Skills run within each user's own permissions; confirm that holds for MCP sessions, and ask which identity appears in the audit trail. Our piece on Agent Fabric spend caps covers the budget controls worth testing alongside it.
Before Renewal:
- Put four terms in the order form: a definition of what the seat covers, the overage rate for indexing, a price hold for the term given Salesforce's "subject to change" language, and treatment of MCP and scheduled-task usage.
- Assign licenses by band. Light users stay on the $5 license with credits, the middle band takes the seat if actions are covered, and the heaviest users go to the $125 add-on if they hold a Sales, Service or Field Service seat it can attach to. Our guide to per-seat, per-action and outcome pricing explains why a cap belongs on whatever stays metered.
The Bottom Line
Salesforce has now sold agent access per conversation, per action and per seat. The $2 conversation price came first, the $0.10 action and the unmetered add-ons followed in May 2025, and the $50 seat arrives 18 months later as a middle option for people who mostly search and sometimes delegate. That middle is a sensible place for a product to sit, and for many employees $50 may turn out to be cheap.
The exposure is largest in scheduled tasks, due in December, which run without a user watching the count. Salesforce can close this with a sentence on its pricing page. Until it does, get that sentence into your order form and count actions per user before you commit to a seat number.
Continue Reading
- Your Agentforce Bill Depends on How Many Actions an Agent Takes
- Agentic AI Pricing: Don't Buy Consumption Without a Cap
- AI Bundles Push Microsoft, Google and Salesforce to Raise Prices
- Test Agent Fabric Spend Caps Before Retiring Your AI Gateway
- Your Unlicensed Copilot Chat Users May Hit Limits Admins Can't See
- Salesforce Agentforce Coworker Kills the 1.8-Hour Search Tax