Agentforce Coworker in Microsoft Teams Explained: Salesforce’s $50 AI Teammate Comes to Where You Work

On 5 November 2026, Salesforce announced the biggest expansion yet of its AI teammate — and the headline move was not a new model or a new feature buried in a settings menu. Agentforce Coworker Microsoft Teams integration puts Salesforce’s AI teammate directly inside the chat app where millions of American office workers already spend their day. Instead of opening Salesforce, finding the right record and running a report, an employee can now hand a job to Agentforce Coworker Microsoft Teams in a Teams conversation and get the result back, with the same Salesforce data, permissions and governance rules applying behind the scenes.

Alongside the Teams move, Salesforce added a flat $50 per user per month pricing option, connections to Google Workspace and Microsoft 365, reusable Skills, Conversation History, and new iOS, Mac and Windows apps — and it reported that Agentforce Coworker Microsoft Teams usage has grown 21 times in three months, to more than 185,000 users. This guide explains what Agentforce Coworker Microsoft Teams actually does, how delegation inside a chat works, what is live now and what is still on the calendar, what the $50 price really buys, and whether your team should adopt it now or wait.

Business team collaborating around a laptop in a modern office, the workplace where Agentforce Coworker Microsoft Teams brings Salesforce AI into daily chat

What Is Agentforce Coworker?

Agentforce Coworker Microsoft Teams is Salesforce’s AI teammate for delegating business work. The distinction matters, because it is not a chatbot that answers one question at a time and it is not a single-purpose agent that does one narrow job. An employee gives Agentforce Coworker Microsoft Teams a job in plain language — prepare the briefing for tomorrow’s renewal call, draft the follow-up for the three accounts that went quiet last month, pull together the numbers for the quarterly business review — and Coworker plans the steps, coordinates the right Agentforce agents and agentic workflows to carry them out, and brings the results back for the employee to review.

The human stays in charge of the outcome; the AI does the gathering, drafting and coordinating in between.

That framing is deliberate. Salesforce has spent the last two years building Agentforce as a platform of agents that act inside the Salesforce clouds — sales, service, marketing and the rest — and Agentforce Coworker Microsoft Teams is the layer that sits above them, the one an ordinary employee actually talks to. It works from trusted Salesforce context: the accounts, opportunities, cases, contacts and custom objects a company already keeps in its CRM, plus the documents and messages connected through Google Workspace and Microsoft 365. Crucially, it also inherits the same security, permissions and governance rules that already govern that data.

A sales rep who cannot see a particular account in Salesforce cannot get Agentforce Coworker Microsoft Teams to show it to them either, and an action Agentforce Coworker Microsoft Teams takes is logged against the same audit trail as a human one. For a company that has spent years locking down its CRM, that is the difference between an AI toy and an AI colleague.

The November 2026 expansion is best understood as Salesforce taking Agentforce Coworker Microsoft Teams out of its own walled garden. Until now, Agentforce Coworker Microsoft Teams lived mainly inside Salesforce surfaces. The new release meets employees where their working day actually happens: in Microsoft Teams, in email and calendars, on their phones, and on their desktops. That is why the Agentforce Coworker Microsoft Teams integration is the centrepiece of the announcement, and why it is the part of the story that will matter most to the hundreds of thousands of US workers whose first app of the morning is Teams, not Salesforce.

It is also worth clearing up a naming collision before it causes confusion. Agentforce Coworker Microsoft Teams is a Salesforce product, and it is not the same thing as Adobe’s CX Enterprise Coworker, which Adobe announced around the same time for customer-experience teams, nor is it the Salesforce-Cresta acquisition story that circulated in the same week. Three different products share the word “Coworker” in November 2026, and only the Salesforce one works inside Microsoft Teams for $50 per user per month.

What Is New in the November 2026 Expansion

Salesforce announced the expansion on 5 November 2026, and the package has three layers: new places to reach Agentforce Coworker Microsoft Teams, new context for it to work with, and new pricing. Here is the full picture, split into what is available now and what is scheduled.

Available now: Google Workspace and Microsoft 365 connectivity, Conversation History across devices, reusable Skills, and the new $50 per-user, per-month pricing option. These are live for customers today, and they are the parts of the release a team can actually switch on this week.

Generally available in November 2026: Agentforce Coworker Microsoft Teams integration, the Agentforce Coworker Microsoft Teams app for iOS, the desktop app for Mac and Windows, the Agentforce Coworker Microsoft Teams MCP server for connecting additional data sources, and a free trial for Flex Credits customers. The wording matters here: Salesforce lists these as generally available in November 2026, not as already live for every customer on 5 November, so a team that checks on 11 November may find the Teams app still rolling out. The rollout is the news; the exact day your tenant sees it depends on Salesforce’s staged schedule.

Expected in December 2026: Daily Digest, a morning summary of priorities, and Scheduled tasks, which let Agentforce Coworker Microsoft Teams run recurring assignments on its own. Agentforce Coworker Microsoft Teams is also expected to arrive in the Field Service, Consumer Goods Cloud and Life Sciences Cloud mobile apps in December. Neither December item should be planned around yet — they are announced, not shipped.

The shape of the release tells you Salesforce’s strategy. The company is no longer asking customers to come to Salesforce to use AI. It is placing its AI teammate inside the tools customers already pay for — Teams for chat, Outlook and Gmail for email, Word and Docs for documents — and charging a predictable per-seat price for it. That is a distribution play as much as a product play, and it is the reason this announcement matters beyond Salesforce’s existing customer base.

Agentforce Coworker Microsoft Teams: Delegation Inside a Chat

The Agentforce Coworker Microsoft Teams integration is simple to describe and significant in practice. Once it is generally available in your organisation, you hand Agentforce Coworker Microsoft Teams a job inside a Teams conversation — the same place you already ask a colleague a question — and it brings the same Salesforce context, permissions and governance to that chat. You do not switch apps, you do not open a browser tab, and you do not copy a customer name from one window into another. The conversation becomes the interface, and the CRM becomes the memory behind it.

Consider a concrete example. A sales manager is in a Teams channel with her team, and a customer has just asked for a renewal quote with updated pricing. In the old workflow she would leave Teams, open Salesforce, find the account, check the opportunity, look up the pricing history, draft the quote, and paste the result back into the chat.

With Agentforce Coworker Microsoft Teams, she types the request into the same channel, Agentforce Coworker Microsoft Teams plans the steps — find the account, pull the opportunity and pricing history, draft the quote, flag anything that needs a discount approval — coordinates the agents that do each piece, and returns the draft and the recommended actions for her review. The work still ends with a human decision, but the gathering and drafting happen without the app-switching that eats most of a knowledge worker’s day.

A laptop showing a video conference call grid, illustrating how Agentforce Coworker Microsoft Teams works inside team meetings and chats

That matters because of where work actually happens. Microsoft Teams is the daily operating system of a huge share of US office workers — it is where meetings happen, where files get shared, and where quick questions get answered. Salesforce’s own pitch for the integration is exactly this: Agentforce Coworker Microsoft Teams now meets employees where their working day happens. A CRM that only works when you remember to open it will always lose to the chat window that is already open. By placing Agentforce Coworker Microsoft Teams inside Teams, Salesforce is betting that the fastest way to get people to delegate work to AI is to put the AI in the place they already delegate work to each other.

There is a second, quieter point that matters just as much. Because the Teams integration carries the same Salesforce permissions and governance, a delegated job cannot see more than the person delegating it can see. A manager asking about her own accounts gets full detail; a colleague asking about an account outside their territory gets the same restricted view Salesforce would give them directly. That sounds obvious, but it is the feature that makes an IT department comfortable enough to switch the integration on. Many AI tools that connect to a CRM either copy data out of it — creating a second, uncontrolled copy — or ignore its permissions entirely.

Agentforce Coworker Microsoft Teams does neither, and Salesforce has made that the centrepiece of its trust argument.

One caution: the Teams integration is listed as generally available in November 2026, which means it is rolling out during this month rather than already live everywhere. If your organisation uses Salesforce and Teams, the practical next step is to ask your Salesforce account executive or admin whether the app has reached your tenant yet, rather than assuming it is switched on because the announcement is a week old.

How Delegation Works, Step by Step

Delegation to Agentforce Coworker Microsoft Teams follows the same pattern whether you talk to it in Teams, in the desktop app or on your phone, and understanding the pattern is more useful than memorising a feature list. Here is how a typical job flows through Agentforce Coworker Microsoft Teams.

Step 1: You describe the outcome, not the steps. You write the job the way you would brief a capable colleague: “Prepare a one-page brief for the Acme renewal call tomorrow, including last quarter’s usage, open support cases and the discount we offered in March.” You do not need to say which objects to query, which report to run or which agent to invoke. Agentforce Coworker Microsoft Teams takes the outcome and works out the plan.

Step 2: Agentforce Coworker Microsoft Teams plans and coordinates. Behind the scenes, Agentforce Coworker Microsoft Teams breaks the job into steps and hands each one to the right Agentforce agent or workflow — one to fetch the usage data, one to pull the open cases, one to find the March discount in the email thread or the opportunity record. This is the part of the system that separates a “teammate” from a chatbot: a chatbot would answer from whatever it happens to know, while Coworker assembles a small team of specialised agents and manages the handoffs between them.

Step 3: Results come back for review. Agentforce Coworker Microsoft Teams returns the brief, the draft or the summary, along with the recommended actions — and the sources it used. Nothing is sent to a customer or filed in the CRM without a human looking at it first. That review step is the control that makes delegation safe: the employee checks the work, corrects anything that is wrong, and approves the parts that are right. Over time, the reusable Skills feature (covered below) lets a team turn a delegation that worked well into a one-line request the next time.

Step 4: The conversation continues. Conversation History means the thread is not lost when you switch devices. You can start a job in Teams on your laptop, check the result on the iOS app on the way home, and finish the review on the desktop app the next morning. The history travels with you, which sounds minor until you have tried to reconstruct a half-finished AI task from memory the next day.

The important limitation to keep in mind is that Agentforce Coworker Microsoft Teams is only as good as the data it can reach. If your Salesforce records are incomplete, your pricing lives in a spreadsheet nobody connected, or your email history sits in a mailbox outside the Workspace and Microsoft 365 connectors, Agentforce Coworker Microsoft Teams will plan around the gaps — and sometimes it will plan badly. The November release widens the data it can reach, but a team that wants good results from Agentforce Coworker Microsoft Teams should treat the rollout as a reason to clean up its CRM data first, not as a substitute for doing so.

Google Workspace and Microsoft 365 Connections

The second pillar of the November expansion is connectivity: Agentforce Coworker Microsoft Teams can now pair Salesforce records with the email, calendars and files that live in Google Workspace and Microsoft 365. Both connections are listed as available now, and they change what Agentforce Coworker Microsoft Teams can actually do in a useful way.

Before this release, Agentforce Coworker Microsoft Teams knew what was in Salesforce. After it, Agentforce Coworker Microsoft Teams can also see the email thread where a customer explained why they were unhappy, the calendar invite that sets the deadline for a proposal, and the spreadsheet where the pricing was actually negotiated. That is the difference between an AI that can tell you what the CRM says and an AI that can tell you what is actually going on. A renewal brief built only from CRM fields is a summary; a renewal brief built from the CRM plus the last three emails and the meeting notes is preparation.

Colleagues in a conference room discussing work, the kind of meeting preparation Agentforce Coworker Microsoft Teams can assemble from Salesforce, email and calendar data

The Microsoft 365 connection is the more important of the two for most US companies, because it covers Outlook email, Teams meetings, calendars and the Office documents where so much business context lives. The Google Workspace connection covers the equivalent Gmail, Calendar and Drive surface for companies that run on Google. Many organisations use one or the other, and some use both; Agentforce Coworker Microsoft Teams now works with either, which is a deliberate choice by Salesforce to avoid forcing customers to pick a productivity suite before they can use its AI.

There is a governance point here too. Connecting email and files to an AI teammate is exactly the kind of move that makes a security team nervous, and Salesforce’s answer is the same one it gives for the Teams integration: the connections respect the permissions that already exist. Agentforce Coworker Microsoft Teams sees the emails you can see, not the emails your CEO can see, and the same applies to documents. That does not remove the need for an admin to review which connectors are switched on — it means the review is about configuration, not about trusting a new copy of your data to a new system.

For teams evaluating the release, the practical question is not whether the connectors exist but whether your organisation will switch them on. Both connections require admin setup and, in most companies, a security review. The announcement makes them available; your IT department makes them real. Budget a week or two for that review rather than expecting to delegate from Outlook on day one.

Skills, Conversation History and the Coworker MCP Server

Three smaller features in the November release deserve attention because they determine whether Agentforce Coworker Microsoft Teams becomes a daily habit or a demo that gets tried once and forgotten.

Skills turn a proven workflow into a reusable, one-line request. If your team has worked out the right way to prepare a renewal brief — which sources to check, which numbers to include, which format to use — you can save that as a Skill, and the next person simply invokes it instead of describing the whole job again. Skills are shareable across the team, which means the best way of doing a job spreads from the person who worked it out to everyone else. This is the feature that makes Agentforce Coworker Microsoft Teams compound: the first month you teach it your workflows, and from then on you reuse them.

For a sales or service team with repeatable processes, Skills are arguably more valuable than any single new surface.

Conversation History keeps Agentforce Coworker Microsoft Teams threads available across devices, so a job started in Teams can be continued on the iOS app or the desktop app without starting over. It sounds like a small convenience, and it is — but small conveniences are what decide whether people actually use a tool at 8 a.m. on a Monday. The history is tied to the same permissions as everything else, so a thread about an account you cannot see does not become visible just because it is in your history.

The Agentforce Coworker Microsoft Teams MCP server, generally available in November 2026, is the developer-facing piece. MCP — the Model Context Protocol — is the open standard that lets AI systems connect to external tools and data sources, and Salesforce’s Agentforce Coworker Microsoft Teams MCP server lets organisations connect additional data sources beyond the built-in Workspace and Microsoft 365 connectors. For a company with a data warehouse, a custom internal tool or a legacy system that holds important context, the MCP server is the route to bringing that data into Coworker’s reach.

It is not a feature most end users will ever touch, but it is the feature that decides whether Agentforce Coworker Microsoft Teams can work with the whole business or only with the Salesforce-shaped part of it.

A business professional using a smartphone in an office, showing how Agentforce Coworker Microsoft Teams also reaches users on the new iOS app

Alongside these, the new iOS app and the Mac and Windows desktop apps — both generally available in November 2026 — complete the “meet employees where they work” picture. The iOS app matters for the field: a rep between meetings, a service technician on site, a manager travelling. The desktop apps matter for the people who live in their computers all day and want Agentforce Coworker Microsoft Teams a keyboard shortcut away rather than a browser tab away. Neither app adds new AI capability on its own; their value is that they remove the friction of reaching the capability that already exists.

Pricing: The $50 Per-User Option Explained

Before November 2026, paying for Agentforce Coworker Microsoft Teams meant paying through Salesforce’s usage-metered Flex Credits model, which charges for the AI work actually consumed. That model is fair in principle and hard to budget in practice: a finance team cannot easily predict how many credits a team will burn in a month, and a manager who wants to roll Agentforce Coworker Microsoft Teams out to fifty people has to guess the bill. The November release adds a second option — a flat $50 per user per month — and for most buyers that flat number is the most important line in the whole announcement.

Here is what the $50 option covers, based on Salesforce’s announcement and its pricing page. The licence includes all Agentforce Coworker Microsoft Teams searches, so the per-query metering that made Flex Credits unpredictable goes away for day-to-day use. It also includes 30 MB of indexing per user per month for connecting enterprise data, which is the allowance for bringing outside documents and records into Agentforce Coworker Microsoft Teams’s searchable index. And it includes all of the existing Salesforce security, governance and access policies from day one — there is no cheaper tier that drops the permission controls, which is a sensible design choice for a product whose whole pitch is trusted access.

The arithmetic is straightforward. Ten users cost $500 a month, or $6,000 a year. Fifty users cost $2,500 a month, or $30,000 a year. A hundred users cost $5,000 a month, or $60,000 a year. Those are clean numbers a budget owner can put in a spreadsheet without a usage model, and that predictability is exactly why Salesforce is offering the option. It also makes the pilot conversation easier: a team can price a ten-person trial precisely, measure what it saves, and then decide whether to expand.

There are three things the $50 figure does not answer, and buyers should not assume them. First, Salesforce has not said that the $50 licence replaces Flex Credits for every use — heavy or unusual workloads may still run through usage-based billing, and the announcement does not spell out where the boundary sits. Second, the $50 option is sold through a Salesforce account executive; it is not a self-serve checkout, so the price a specific organisation actually pays may depend on its existing Salesforce agreement. Third, Salesforce’s own note applies: pricing and packaging are subject to change, and availability may vary by region and is governed by customer agreements. The $50 number is the headline, not the contract.

There is also a free trial for Flex Credits customers, listed as generally available in November 2026. If your organisation already buys Flex Credits, that trial is the cheapest way to test Agentforce Coworker Microsoft Teams in Teams before committing to per-seat licences — ask your account executive what the trial covers and how long it runs, because the announcement does not give those details.

How does $50 per user per month compare? Microsoft 365 Copilot is priced at $30 per user per month for most commercial customers, which makes Agentforce Coworker Microsoft Teams the more expensive of the two on a per-seat basis — but the comparison is not like-for-like, because Copilot is a general productivity assistant across Microsoft 365 while Agentforce Coworker Microsoft Teams is a Salesforce-grounded teammate with CRM actions built in. A company that already pays for Salesforce and wants AI that can act on its CRM data is not choosing between two identical products at two prices; it is choosing between a cheaper generalist and a more expensive specialist.

The right question is not “which is cheaper per seat” but “which one does the work my team actually delegates”. We compare the two properly in the comparison section below.

The 21x Growth Claim: What the Numbers Actually Say

Salesforce says Agentforce Coworker usage grew 21 times in three months, and that more than 185,000 users are now putting it to work. Those are the two numbers every summary of the announcement leads with, and they deserve a careful reading, because they are impressive and limited at the same time.

First, what the numbers are: they are Salesforce’s own, self-reported figures from its press release. Salesforce does not publish the starting usage baseline, so 21x tells you the growth rate, not the absolute volume of work delegated. A product that goes from 100 delegated jobs a day to 2,100 has grown 21x; so has a product that goes from 10,000 to 210,000. Both are real growth, but they are very different businesses, and the announcement does not let you tell them apart.

The 185,000-user figure is more concrete — it is a count of people, not a multiple — but Salesforce does not say how many of those users pay the new $50 price, how many are on Flex Credits, or how many are in a trial.

Second, what the numbers are not: they are not an independent benchmark of quality. No hours saved, no cost per resolved case, and no renewal or revenue outcome is published in the announcement. The three customers Salesforce names — The Adecco Group, Fulton Bank and BACA Systems — are real deployments, and the details are useful: Adecco is expanding Coworker across 40 countries, Fulton Bank runs more than 20 production use cases with about 3,000 users, and BACA Systems enabled Coworker in 20 minutes.

Those three examples are evidence that the product works in production, but three named customers are not a market, and they are not a substitute for the kind of independent evaluation that would tell a buyer how often Coworker gets a delegated job right on the first try.

None of that makes the numbers meaningless. A 21x growth rate over three months, from a company that has every incentive to be careful with its claims in a press release, is a strong signal that real teams are delegating real work and coming back for more. The honest way to read it is as a demand signal, not a quality certificate: lots of people are trying Coworker, usage is compounding fast, and the product has crossed the line from pilot curiosity to production tool at the companies Salesforce names. A buyer should treat that as a reason to run a pilot, not as a reason to skip one.

Customer service agents wearing headsets at their desks, representing the service teams whose work Agentforce Coworker Microsoft Teams can help coordinate

Who Should Use It — and Who Should Wait

Salesforce-heavy sales and service teams should look first. If your team’s work already lives in Salesforce — accounts, opportunities, cases, contracts — Coworker has the most context to work with and the most actions it can take. A sales team that spends its day in Salesforce and Teams is the ideal early adopter: the data is there, the chat surface is there, and the $50 price is easy to justify against the hours spent on manual preparation. Fulton Bank’s 3,000 users and 20-plus production use cases are the template here — a large, process-heavy team with repeatable work that Coworker can take over in pieces.

Teams-first organisations with a Salesforce deployment should look second. If your company runs on Microsoft Teams and already pays for Salesforce, the Agentforce Coworker Microsoft Teams integration removes the biggest adoption barrier, which was asking people to leave the app they live in. The value here is not a new AI capability but a new front door to a capability you already own. The pilot to run is small: ten people, one repeatable job — renewal briefs, case summaries, meeting preparation — measured over a month.

Small teams should do the maths before they commit. At $50 per user per month, a five-person team pays $250 a month, or $3,000 a year. That is a fair price if Coworker saves each person even a few hours a month, and a waste if the team’s Salesforce data is thin or its work is not repeatable enough for Skills to pay off. Small teams should use the Flex Credits free trial first and measure honestly: how many delegated jobs per week, how many came back right the first time, and how many hours were actually saved.

If the answer is “a few jobs, mostly right, a few hours”, the $50 seat is an easy yes. If the answer is “we tried it twice”, wait.

Teams that should wait include organisations that do not use Salesforce at all — Coworker is built on Salesforce context, and without that context it has little to work with — and organisations whose Salesforce data is a mess. Coworker plans from the data it can reach; if that data is out of date, duplicated or half-empty, the plans will be wrong in ways that look confident. Fix the data first, then buy the teammate.

Teams should also wait for the December features if their use case depends on them: if the whole point is a morning Daily Digest or a recurring scheduled task, the November release does not deliver that yet, and buying now means paying for a feature that arrives next month.

Agentforce Coworker vs Microsoft 365 Copilot and Other AI Teammates

The obvious comparison is with Microsoft 365 Copilot, which also works inside Teams and also answers questions from your documents and email. The difference is grounding. Copilot is grounded in Microsoft 365 — your emails, your files, your meetings — and it is very good at summarising and drafting from that material. Coworker is grounded in Salesforce — your accounts, opportunities, cases and the business processes built around them — and it is built to take actions against that data: update a record, draft a quote from a pricing history, coordinate agents that each own a piece of a business process.

A company that lives in Microsoft 365 and barely uses Salesforce will get more from Copilot; a company whose revenue runs through Salesforce will get more from Coworker. Many large companies will end up using both, with Copilot for documents and meetings and Coworker for CRM work — and the Agentforce Coworker Microsoft Teams integration makes that coexistence easier, because both assistants now meet the employee in the same chat app.

The comparison with general chatbots — ChatGPT, Claude, Gemini — is simpler. A general chatbot can draft a beautiful renewal email, but it does not know your customer’s payment history, it cannot see the open support cases, and it cannot update the opportunity when the customer agrees. Coworker can, because it sits on top of the system of record. The trade-off is scope: a general chatbot can help with anything, while Coworker is at its best inside the business processes Salesforce already models. The right mental model is not “Coworker versus ChatGPT” but “Coworker for the work that needs your CRM, a general chatbot for everything else”.

There is also a newer category to watch: agent orchestration tools that coordinate multiple coding or business agents, such as the multi-agent coding tools that have launched this autumn. Those are developer tools, built for software teams, and they solve a different problem — coordinating agents that write code — while Coworker solves the problem of coordinating agents that do business work. The two categories will converge over time, but today they serve different buyers.

For a buyer, the honest summary is this: if your question is “which AI teammate should my sales and service team use inside Teams”, and you already run Salesforce, Coworker is the natural answer at $50 a seat. If your question is “which AI assistant should every employee in the company get”, the answer is probably Copilot at $30 a seat, with Coworker added for the teams whose work runs through the CRM. The two are complements, not substitutes, and Salesforce’s decision to put Coworker inside Teams is an acknowledgement of that reality.

How to Get Started With Agentforce Coworker in Teams

Getting started is an admin-led process, not a download, so set expectations accordingly. Here is a practical sequence for a team that wants to pilot Agentforce Coworker Microsoft Teams this month.

  1. Confirm availability for your tenant. Ask your Salesforce account executive or admin whether the Teams app, the iOS app and the desktop apps have reached your organisation yet. They are listed as generally available in November 2026, which means a staged rollout, and your tenant’s date may be later in the month.
  2. Decide the billing route. Choose between the new $50 per-user, per-month option and the existing Flex Credits model. If you already buy Flex Credits, ask about the free trial first — it is the cheapest way to measure real usage before committing to seats. Remember that the $50 option is sold through an account executive, so get the quote in writing, including what happens to Flex Credits billing for workloads outside the per-seat licence.
  3. Pick one repeatable job. Do not roll Coworker out to everyone for everything on day one. Pick one job that happens every week, has a clear input and a clear output, and currently eats real time — renewal briefs, case summaries, or pre-meeting preparation are good candidates. Write the job down as a Skill so the team can invoke it in one line.
  4. Switch on the connectors deliberately. Connect Google Workspace or Microsoft 365 — whichever your company actually uses — and review the permissions with your IT or security team before going live. Confirm that Coworker respects the same access rules as Salesforce itself, and decide which document sources are in scope for the pilot.
  5. Run a four-week pilot with ten people. Measure three things: how many jobs were delegated per week, how many came back right on the first attempt, and how many hours the team estimates it saved. Hold a short review at the end of each week, because the first week’s results will be worse than the fourth week’s — people get better at delegating, and Skills get better as they are refined.
  6. Decide on evidence, not enthusiasm. If the pilot shows real hours saved and clean first-attempt results, expand to the next team and the next job. If it shows that the team’s data is too messy or the jobs are too varied, fix the data and re-pilot rather than expanding a weak result. The $50 price makes the expansion decision easy to cost; the pilot makes it easy to justify.

One more practical note: the Teams integration means your employees will meet Coworker in a place they already use, which helps adoption — but it also means the pilot’s success depends on the Teams admin as well as the Salesforce admin. Bring both into the planning conversation early, because the app has to be approved and deployed in Teams before anyone can delegate from a chat.

What Arrives in December 2026

Two features are expected in December 2026, and both change Coworker from a reactive teammate into a proactive one. Daily Digest is a morning summary of priorities — the meetings that matter, the accounts that need attention, the cases that went quiet — delivered before the working day starts. Scheduled tasks let Coworker run recurring assignments on its own: a weekly pipeline summary every Monday at 8 a.m., a monthly usage report on the first of the month, a daily check for accounts that have gone thirty days without contact. Together, they are the features that make Coworker feel less like a tool you remember to use and more like a colleague who shows up with the work done.

December also brings Coworker to the Field Service, Consumer Goods Cloud and Life Sciences Cloud mobile apps, which extends the teammate to the field technicians, retail execution teams and life-sciences reps whose working day happens away from a desk. Those are narrower audiences than the general Teams rollout, but for the companies in those industries they may matter more than the Teams integration itself.

The caution is the same as for any announced-but-unshipped feature: dates slip. Salesforce lists these as “expected in December 2026”, not as a guarantee, and a team whose business case depends on Scheduled tasks should not sign a contract that assumes they arrive on 1 December. Buy the November release for what it does today, and treat December as a bonus.

Limitations and Honest Caveats

Every product announcement is a sales document, and this one is no exception. Here are the limits that matter, stated plainly.

The growth numbers are self-reported. The 21x usage growth and the 185,000-user count come from Salesforce itself, with no published baseline and no independent verification. They are a demand signal, not a quality certificate, and they say nothing about how often Coworker gets a job right the first time.

The Teams integration is rolling out, not already everywhere. “Generally available in November 2026” means your tenant may not have it yet. Check before you promise your team a date.

The December features are not shipped. Daily Digest and Scheduled tasks are expected, not live. Do not plan a workflow around them until they arrive.

The $50 price is a headline, not a contract. It is sold through an account executive, pricing and packaging are subject to change, and the announcement does not say where per-seat billing ends and Flex Credits billing begins. Get the quote in writing.

Coworker is only as good as your Salesforce data. Incomplete records, duplicate accounts and pricing that lives in spreadsheets will produce confident-looking wrong answers. The November release widens the data Coworker can reach, but it does not clean the data it finds.

Three named customers are not a market. Adecco, Fulton Bank and BACA Systems are real deployments, but they are three examples chosen by the vendor. There is no independent benchmark of delegated-work quality yet, and no published data on hours saved or cost per resolved case.

It is not a replacement for your CRM admin, your IT security review or your own judgement. Coworker plans, coordinates and drafts; a human reviews, approves and owns the result. The review step is the control that makes the whole system safe, and skipping it is how a delegated job becomes a delegated mistake.

None of these caveats is a reason not to use Coworker. They are reasons to pilot it honestly, measure it properly, and expand it on evidence. A tool that grows 21x in three months deserves a serious look; a tool whose numbers are all self-reported deserves a serious pilot.

Frequently Asked Questions

What is Agentforce Coworker Microsoft Teams integration?

It is Salesforce’s Agentforce Coworker AI teammate working inside Microsoft Teams. You hand Coworker a job in a Teams conversation — prepare a renewal brief, summarise an account, draft a follow-up — and it plans the steps, coordinates Agentforce agents and workflows, and returns the results for your review, using the same Salesforce data, permissions and governance as the CRM itself. Salesforce lists it as generally available in November 2026.

How much does Agentforce Coworker cost?

The new flat option is $50 per user per month, available now, and it includes all Coworker searches and 30 MB of indexing per user per month for connecting enterprise data. The existing usage-metered Flex Credits model remains available, and there is a free trial for Flex Credits customers. The $50 option is sold through a Salesforce account executive, and Salesforce notes that pricing and packaging are subject to change.

Is Agentforce Coworker Microsoft Teams available now?

It is listed as generally available in November 2026, which means it is rolling out during the month rather than live for every customer on the announcement date of 5 November. If your organisation uses Salesforce and Teams, ask your Salesforce account executive or admin whether the app has reached your tenant yet.

What is the difference between Agentforce Coworker and Microsoft 365 Copilot?

Copilot is a general productivity assistant grounded in Microsoft 365 — email, files and meetings — priced at $30 per user per month for most commercial customers. Coworker is a Salesforce-grounded teammate that plans multi-step business work, coordinates agents and takes actions against CRM data, priced at $50 per user per month. Many companies will use both: Copilot for documents and meetings, Coworker for the work that runs through Salesforce.

Does Agentforce Coworker work without Salesforce?

No, not in any useful sense. Coworker is built on Salesforce context — accounts, opportunities, cases and the processes around them — and its value comes from acting on that data under Salesforce permissions and governance. An organisation that does not use Salesforce has little for Coworker to work with, and should look at a general assistant such as Microsoft 365 Copilot instead.

What data does Coworker use, and is it safe?

Coworker works from Salesforce records plus, where connected, email, calendars and files from Google Workspace and Microsoft 365, and additional sources through the Coworker MCP server. It respects the same permissions and governance rules as Salesforce itself, so it cannot show a user data that user is not allowed to see. Connecting email and files still requires an admin setup and a security review in most organisations.

What is coming to Agentforce Coworker in December 2026?

Daily Digest, a morning summary of priorities, and Scheduled tasks, which let Coworker run recurring assignments on their own, are both expected in December 2026. Coworker is also expected to arrive in the Field Service, Consumer Goods Cloud and Life Sciences Cloud mobile apps. All three are announced, not shipped, and dates may slip.

Is Agentforce Coworker the same as Adobe CX Enterprise Coworker?

No. They are different products from different companies that happen to share the word “Coworker” and were announced in the same month. Salesforce’s Agentforce Coworker is the AI teammate for delegating business work on Salesforce data, now inside Microsoft Teams for $50 per user per month. Adobe’s CX Enterprise Coworker is a customer-experience product. Do not confuse the two when evaluating either one.

The Bottom Line

The November 2026 expansion of Agentforce Coworker is Salesforce’s clearest statement yet about where AI teammates actually belong: not in a separate app you have to remember to open, but in the chat window where your working day already happens. The Agentforce Coworker Microsoft Teams integration is the headline because it changes who can use Coworker and when — anyone in Teams, in the middle of a conversation, without switching apps. The $50 per-user price is the second headline because it changes how a buyer can plan for it: a flat, predictable seat price instead of a usage meter that nobody can forecast.

And the 21x growth figure is the third, because it says that real teams are delegating real work and coming back for more.

The honest version of the story is narrower, and it is the version a buyer should act on. The growth numbers are Salesforce’s own, the Teams app is rolling out through November rather than live everywhere today, the December features are still on the calendar, and the $50 price is a headline that needs a written quote behind it. Coworker is only as good as the Salesforce data it can reach, and no independent benchmark yet says how often it gets a delegated job right the first time. Those are not reasons to ignore it — they are reasons to pilot it properly: ten people, one repeatable job, four weeks, three numbers measured.

If the pilot shows real hours saved, expand. If it shows your data needs work, fix the data and re-pilot. Either way, the direction of travel is clear. The AI teammate has moved into the chat app, and the companies that learn to delegate to it well will spend less of their day on the gathering and drafting that machines can do, and more of it on the judgement and relationships that only people can.

Leave a Comment

Your email address will not be published. Required fields are marked *