Salesforce Coworker: Check Availability Before Rollout

Salesforce’s Agentforce Coworker expansion needs a feature-by-feature purchasing decision, not a single rollout date. Its November 5, 2026 Singapore announcement separates capabilities available now from November general availability and features expected in December. For a business considering a CRM pilot, that distinction should determine what goes into the initial scope.

Our recommendation: approve one useful job using features confirmed in your Salesforce environment. Treat other interfaces and recurring automation as separate acceptance decisions. The checks below are proposed rollout controls, not claims that we have tested a customer deployment.

Make availability the first purchasing question

Salesforce describes Coworker as a way to delegate work using Salesforce records, metadata and connected data. It can coordinate supported Agentforce agents, flows and business actions, then return results and recommended actions for review. The primary announcement gives investigating an at-risk renewal as an example: gathering service history, finding unresolved cases and preparing customer follow-up.

That is a relevant starting point for sales and service teams already using Salesforce. However, do not turn the product description into a promise that every proposed workflow or interface is ready for your organisation.

Use the announcement’s availability section as the starting register:

Announcement status	Features listed by Salesforce	Recommended rollout treatment
Available now	Google Workspace and Microsoft 365 connectivity, Conversation History, Skills and the per-user pricing option	Verify access and suitability before including them in a pilot.
General availability during November 2026	Microsoft Teams, iOS, Mac and Windows apps, Coworker MCP server and a free trial for Flex Credits customers	Confirm the specific feature is available to your organisation; a month is not a tenant-specific activation date.
Expected December 2026	Daily Digest, scheduled tasks and Coworker in Field Service, Consumer Goods Cloud and Life Sciences Cloud mobile apps	Keep these outside the initial acceptance criteria unless subsequently released and verified.

These statuses come from Salesforce’s dated regional release, not a live check of your environment. Salesforce also says availability can vary by region and customer agreement, and purchasing decisions should rely on currently available products.

For each desired feature, record the announcement status, your administrator’s availability check, licensing confirmation and the job that depends on it. Leave unverified entries explicitly marked as unverified rather than treating the announcement as a completed deployment checklist.

Check the prerequisites before enabling access

The official setup guide provides more specific requirements than the announcement’s invitation to turn Coworker on in Setup. It lists Enterprise, Unlimited and Agentforce 1 Editions, and requires Data Cloud or Data 360 to be provisioned and activated.

It distinguishes usage-based access, with entitlements of Flex Credits, Einstein Requests or Data Services Credits, from seat-based access using the listed eligible licences. Turning on, configuring or granting access requires the System Admin Profile and Agentforce Coworker Admin Permission Set. Check your actual licence against that guide rather than assuming all Salesforce users qualify.

After an authorised administrator has confirmed those prerequisites, the documented activation sequence is:

1. Open Setup and enter Agentforce Coworker in Quick Find.
2. Select Get Started with Agentforce Coworker in the side panel.
3. Select Turn On, then Confirm.
4. Review any warnings from automated setup steps and follow their completion instructions.
5. Verify that Einstein also turned on automatically.

The same guide says user-access assignment varies by licence type. Treat activation and granting pilot access as separate checkpoints. Do not make every employee a pilot participant just because setup has finished.

Salesforce’s regional announcement lists the new option at US$50 per user per month and directs buyers to their Salesforce account executive for per-user pricing. It also says pricing and packaging can change. Ask for the terms applicable to your organisation before approving spend; the headline price is not a verified total project cost.

Use the renewal example as a bounded acceptance test

Start with the renewal investigation described by Salesforce, but define a narrower deliverable for your pilot: a service-history review and proposed customer follow-up for human assessment. Do not assume that preparing follow-up and sending it have the same approval requirements.

Salesforce says its new productivity connections combine email, calendars and files with CRM data. It also describes Skills as reusable workflows and Conversation History as a way to resume work. Those are announced capabilities, not evidence that every relevant source has been connected correctly in your environment.

Before running the renewal job, ask the business owner and administrator to agree on:

• Required context: which service records and approved connected materials the reviewer should expect the job to consider.
• Permitted output: a reviewable summary and follow-up draft, with any proposed business action assessed separately.
• Review responsibility: who checks the summary against the underlying material and decides whether the follow-up is appropriate.
• Failure handling: who takes over when relevant information is missing or the proposed action cannot be verified.

Then compare the returned work with the approved source material. Record omissions, corrections and the reviewer’s decision. This is our recommended acceptance method, not a Salesforce-provided guarantee of accuracy.

If data connections need work before that test, make them a distinct CRM integration task rather than expanding Coworker access to compensate for an unresolved requirement.

Verify approval coverage for the actual action

Salesforce says Coworker uses applicable employee permissions, sharing rules and configured access controls. Crucially, its announcement describes approval and audit capabilities as available for supported operations. It does not establish universal approval coverage for every action a business might request. See the primary release’s governance description.

For any action beyond producing a reviewable draft, ask the administrator to demonstrate the control that applies to that operation. Record the permitted user role, the approval requirement where supported, the evidence available after execution and the person responsible for reviewing the result.

Test with the intended employee access rather than treating an administrator’s successful demonstration as sufficient. If approval or audit behaviour for a required operation remains unverified, keep that operation outside the pilot. This is a rollout recommendation based on the announcement’s limited wording, not a report of a product vulnerability.

Expand only after the job earns acceptance

The independent Martech Notes report dates the expansion announcement to November 4, 2026 and also distinguishes released features from the November and December schedule. That coverage corroborates the staged announcement; it does not verify a particular customer’s access or return on investment.

For an SMB, our recommended expansion decision is therefore operational: did the selected job return reviewable work, use the intended information and stay within the approved action boundary? Keep an acceptance record with the tested feature, licence confirmation, reviewer findings, unresolved limitations and business owner’s decision.

Consider reusable Skills or additional interfaces only after that first job passes review and those features are confirmed available. Keep scheduled tasks as a separate decision against their release status, not an assumed part of today’s pilot. A broader business automation scope should follow demonstrated usefulness and verified controls—not the breadth of the announcement.