# Salesforce Agentforce Coworker: $50 Pricing, Teams Rollout and Skills

Salesforce expands Coworker with connected productivity data and reusable Skills. Here is what ships now, what the $50 plan includes, and what buyers should test.

By Paras Madan | 2026-11-05


Salesforce's [November 4 Agentforce Coworker announcement](https://www.salesforce.com/news/stories/agentforce-coworker-surpasses-185k-users/) expands its employee assistant with Google Workspace and Microsoft 365 connections, reusable Skills and Conversation History. The company reports more than 185,000 users and 21-fold usage growth over three months. Those are adoption claims from Salesforce, not independent measurements of work completed or time saved.

For teams already running their customer operations in Salesforce, the practical question is whether employees can delegate a useful job without first learning which agent or application handles each step. The expansion makes that question worth testing, particularly where account information is scattered across CRM records, documents and conversations.

## What is available, and what is coming later

The announcement lists productivity-suite connectivity, Conversation History, Skills and the per-user SKU as available now. Microsoft Teams, iOS, Mac and Windows apps, the Coworker MCP server and a free trial for Flex Credits customers are listed for general availability during November 2026. Scheduled tasks and Daily Digest are expected in December, alongside additional industry mobile experiences.

Salesforce also says availability varies by region and customer agreement. A November rollout window does not establish access for a particular organization today. Buyers should confirm the specific surface they need before making a pilot depend on it, especially if recurring background work is central to the use case.

## What the $50 plan actually includes

The [Agentforce pricing page](https://www.salesforce.com/agentforce/pricing/) lists the Coworker User License at US$50 per user per month, including all Coworker searches and 30 MB of indexing per user per month. It separately lists a US$5 Agentforce User License requiring Flex Credits, with metered employee usage. These are different offers.

At the published Coworker rate, 100 seats imply a US$5,000 monthly license baseline. That arithmetic is useful for budgeting, but it is not a complete implementation quote. Ask Salesforce which downstream agents, actions, data services and indexing requirements fall within the proposed contract. An entitlement to unlimited searches should not be read as a blanket promise that every operation an assistant can initiate is included.

For an initial pilot, calculate cost against accepted deliverables rather than chat volume. A heavily used assistant can still create extra review work if employees must reconstruct its evidence or correct its proposed changes.

## The implementation work sits behind the conversation

Salesforce's [Coworker product description](https://www.salesforce.com/agentforce/coworker/) presents it as a coordinator for specialized Agentforce agents, flows and processes. Skills package a workflow into a reusable request that teammates run within their own permissions. That creates a useful separation between the employee's intent and the machinery needed to execute it.

The company's [admin guidance](https://admin.salesforce.com/blog/2026/meet-your-users-new-ai-teammate-introducing-agentforce-coworker) distinguishes information requests from work requiring a dedicated agent. It also explains that source access matters: Salesforce record permissions and external-system permissions determine which information a user can receive. The guide predates this expansion, so its beta-era availability details should not replace the November release schedule.

Consider a hypothetical renewal workflow. A successful run would need to associate the correct customer with current contract terms, unresolved support issues and the relevant account owner. Finding three plausible documents is insufficient if one belongs to a similarly named customer. Reusing the workflow as a Skill makes those checks more important because a mistake can recur across many users.

A useful acceptance test should therefore cover missing sources, stale records and conflicting account identities. Run the same request under different employee roles and inspect both the evidence returned and the actions offered. Check where approval occurs and what an audit record captures before allowing writes to production records.

Start with one bounded workflow whose output a person can judge. Measure whether the result is correct, how much correction it needs and whether it preserves the intended access boundaries. Those observations will tell a buyer more about expanding deployment than a rising number of conversations.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help technical founders turn enterprise AI capabilities, rollout details and customer evidence into clear technical writing and launch stories.

[Book a 30-minute call](https://cal.com/paras-madan/30min).