Salesforce has unveiled more than 30 new Slackbot capabilities, with CEO Marc Benioff using the announcement to settle an old argument and make a bold new one.
When Salesforce acquired Slack in 2021, the deal drew widespread scepticism. Critics saw an overpriced messaging app. Writing on LinkedIn this week, Benioff was characteristically direct:
“Some saw a messaging app. We saw the foundation for the Agentic Enterprise.”
Salesforce’s answer to the growing competition from Microsoft, Workday, and Oracle is a repositioned Slackbot, pitched not as a chatbot but as what Benioff calls “the ultimate teammate.”
For more on Slack’s evolution into an agentic platform, read Is Slack’s ‘Agentic OS’ Reinvention the Future of Work Platforms?
What the new Slackbot can actually do
The new Slackbot capabilities go well beyond automated responses and keyword search. It can now listen to meetings and update CRM records without user intervention, take action across enterprise apps on the user’s behalf, and connect into Agentforce to route employees to the right specialised agent without them needing to know which one to ask.
For businesses managing a growing catalogue of purpose-built agents across sales, HR, IT, and finance, that last point matters. Rather than employees hunting for the right tool, Slackbot acts as an orchestration layer across all of them.
Salesforce describes the vision as Slack becoming the “agentic work OS”, where deploying agents “instantly makes them accessible to millions of daily users, embedding AI directly in the flow of work.” The announcement also confirms an open ecosystem approach, with partners including Anthropic already previewing agent integrations inside Slack.
Slackbot productivity gains: What the early data shows
Salesforce has been running Slackbot internally ahead of any external rollout. “We’re Customer Zero for everything we build,” Benioff wrote, adding that Slackbot is “on track to become the fastest-adopted feature in our history.” The company’s own data puts the figure at up to 20 hours saved per week among its highest adopters.
Customers including Anthropic, Wayfair, and reMarkable are reporting employees saving 90 minutes a day. Benioff puts the annual equivalent simply:
“That’s more than two months of working hours back every year.”
Starting this month, access is being extended to Free and Pro plan users, a significant widening of the addressable base.
Slack vs Microsoft Teams: The battle for enterprise agent orchestration
Microsoft has made Teams the home for Copilot, weaving it into document creation, meetings, and communications across Microsoft 365. Salesforce’s argument is that a dedicated orchestration layer with deep CRM context and an open agent ecosystem built on Model Context Protocol is more durable than productivity software with AI added on top.
As Benioff puts it:
“Work has become agents. Not one agent. Hundreds of them across every department, every workflow, every customer interaction. All of those agents need somewhere to live. They need to talk to each other. And the people using them need one place to orchestrate it all. That place is Slack.”
Teams retains a dominant installed base, and Salesforce has ground to make up. But extending Slackbot to free users suggests the priority right now is proving the concept at scale. For IT and operations leaders, the practical question is which platform can manage an expanding roster of agents running across the business simultaneously. After five years of questions about the Slack acquisition, Salesforce now has a concrete answer.
What this means for IT and operations leaders evaluating slack
If your organisation is already on Slack, the case for piloting Slackbot is straightforward given that Free and Pro plan access starts this month. The more pressing question is whether your current agent infrastructure is set up to take advantage of orchestration at this level.
A few things worth considering before you do:
- CRM integration: Slackbot’s ability to update records mid-meeting is only as useful as the quality of your Salesforce data. Organisations with inconsistent CRM hygiene may find the automation creates as many problems as it solves.
- Agent governance: As Benioff notes, businesses are now running hundreds of agents across departments. Without a clear ownership and auditing framework, routing everything through a single orchestration layer adds complexity rather than removing it.
- Microsoft 365 dependencies: For organisations where Teams and Copilot are already embedded across workflows, switching costs are real. The open ecosystem approach via Model Context Protocol means Slack can sit alongside rather than replace existing tools, but that integration work needs resourcing.
For further reading, the UC Today guide to Slack AI and Agentforce is a useful primer on how the platform has developed, and our 2026 workplace automation trends piece sets the broader context for where enterprise automation is heading.
