📅 04 Nov 2026 • Salesforce Newsroom
Agentforce Coworker at 185,000 users
Salesforce published adoption metrics for Agentforce Coworker, the AI coworker product that sits next to employees inside the applications where work happens. Per Salesforce Newsroom on 4 November 2026, explicitly company-reported: more than 185,000 users, usage that grew 21 times over 3 months, pricing at $50 per user per month. The product positions an AI coworker as a colleague with its own usage curve, not a feature toggle inside an existing app.
Skills, history and a scheduler
The update matters as much as the metrics. Reusable Skills are packaged skill sets a team builds once and shares across the organization. Conversation History carries context across sessions instead of resetting every time. Deferred tasks on a schedule (expected from December 2026) are the architecturally significant piece: work runs unattended while the employee is away, on a timetable the agent owns. A worker that holds context between sessions and executes on a schedule stops being a chat window and starts being staff.
Orchestration surface
Coworker works inside Microsoft Teams, in mobile and desktop applications, and coordinates specialized Agentforce agents running on Data 360 data. The pattern is a generalist coworker orchestrating specialists: the human talks to one interface, and the orchestrator decomposes the request across agents that each hold a narrow skill and the relevant slice of company data. Integration cost stays low, since the agent arrives inside software the workforce already opens every morning.
Who is expanding
Company-reported expansions include The Adecco Group, Fulton Bank and BACA Systems. Named deployments at this stage of the agent product cycle are a sales signal: enterprises move agent workers into production rather than keeping them in pilots. For architects the takeaway: the agent worker is a standard, seat-priced role inside everyday tools — read the adoption figures as company-reported vendor data, and watch orchestration, shared context and scheduled execution as the features that make an agent count as a colleague.
Sources:
Continue the conversation: https://t.me/AIAutomationArchitecture · Bluesky
Top comments (0)