Salesforce spent 2026 rebuilding what Slack is for (and it is still going). Between the January release of a genuinely capable Slackbot, the February opening of Slack’s agent platform, and the announcements at TrailblazerDX in April, the product moved from a place where people talk to a place where work is truly capable of being orchestrated.
And… rumour has it there is more coming at Dreamforce this year as well.
Here are the things we think are worth knowing about:
One: Slack now arrives whether you asked for it or not
New Salesforce customers are provisioned with Slack from the outset. If your organisation has bought or expanded Salesforce recently, you may already own a collaboration platform.
That sounds like a gift. In practice it is the beginning of an ungoverned workspace, because platforms that arrive without a project also arrive without a channel model, an access policy, a retention position or an owner. Six months later somebody notices that half the organisation is in there, a third of the channels are dormant, and there is no way to work out who can see what.
Action: Name an accountable owner for Slack before the sprawl starts. Retrofitting governance onto a workspace people already live in is materially harder than setting it up once.
Two: Slackbot became a real agent, and its limits are the important part
Slackbot was rebuilt from a novelty into a personal AI agent and reached general availability in January 2026. It summarises conversations, prepares you for meetings, analyses and creates files, reaches Salesforce records, searches across connected sources, runs recurring tasks and takes notes on meetings held on Zoom or Google Meet. Later releases added reusable skills, a deep research mode, sandboxed code execution and slide generation.
That is a serious tool. Three constraints decide whether it can carry real work.
It is only on the higher tiers. Slackbot runs on Business+ and Enterprise+. It is not on Free or Pro.
There is a message allowance. As of August 2026, each person on Business+ gets fifteen Slackbot messages a week. Enterprise plans are unmetered. Fifteen messages is enough to build a habit and not enough to run a workflow. With this in mind you want to be careful about what you start, as you might not be able to finish it. Slack’s own leadership has publicly acknowledged the limit needs revisiting, so confirm it at the time you scope anything.
Included is not a promise. Slack has stated it may move advanced Slackbot capabilities released after June 2026 to consumption pricing, with thirty days’ notice. This is worth keeping in mind and potentially budgeting for.
Three: the licensing trap that catches long-standing customers
This is the one worth reading twice, because it is counterintuitive and it is expensive.
Slack retired its standalone AI add-on in mid-2025 and folded AI into the plan tiers. Customers who had been on Business+ or Enterprise Grid for years, and who never bought that old add-on, dropped back to Pro-tier AI features.
Worth knowing: enterprise search across connected third-party systems, which is the feature most organisations picture when they imagine AI in Slack, sits on Enterprise+ only.
Four: Slack became an agent platform, in both directions
In February 2026 Slack made two things generally available: a Model Context Protocol server and a real-time search API. In April, Slackbot itself became an MCP client. Salesforce’s Parker Harris described Slack at TrailblazerDX as the front door to the agentic enterprise, and architecturally that is a fair description of what was built.
Traffic now runs both ways. External agents can search your channels, send messages, manage canvases and take actions in Slack. And Slackbot can reach outward into your own systems through MCP servers, which administrators configure through Slack’s admin settings.
For an Australian organisation this is the genuinely new governance question of 2026, and it is a data question. Which of your systems should an agent operating inside a chat platform be able to reach? Under whose permissions? With what audit trail? And who reviews that list when someone connects a new one?
There is a related gap worth naming plainly. New Slackbot functionality releases automatically, and admin settings do not apply to capability that has not shipped yet. An administrator cannot pre-approve or pre-block a feature that does not exist. In a change-controlled or certified environment, that means your control is a standing review cadence, not a configuration setting. Very few organisations have set one up.
What we would actually do about it
If we were sitting in your leadership meeting, the sequence would be this.
Confirm what you own. Plan tier, AI entitlement, whether the legacy add-on issue applies to you. Half an hour, and it changes every subsequent decision.
Name an owner. One accountable person for the Slack estate, with the authority to say no to an app connection.
Decide the MCP question before you need to. Write down which systems an agent in Slack may reach, and the process for adding one. It is much easier to write this when nothing is connected yet.
Set the review cadence. Monthly or quarterly, someone reads the release notes and checks the settings still say what you meant them to say. This is the control that covers the features that have not shipped.
Then talk about agents. Agents amplify whatever data and structure you point them at, which is why we run a readiness assessment as a gate, and why that assessment is capable of recommending you do not proceed.
In Summary
The platform got substantially more capable this year but also substantially harder to govern. The organisations that will get value from it are not the ones that move fastest. They are the ones that know what they own, decided who is accountable, and set the boundary before the agents arrived.
If you are not sure which of those you have done, that is exactly what a Slack Health Check is for. Two to three weeks, a findings report and a prioritised plan, and a straight answer about what to fix first.
Not sure where you stand on any of this? Get in touch with Andrew for a Slack Health Check, and we’ll give you a straight answer about what to fix first.
Andrew France
Chief Exceutive Officer
Andrew has spent close to a decade in and around the Salesforce ecosystem, including founding Destined (acquired by Media Monks) and building one of the region's leading Salesforce consulting partners. His background covers the not-for-profit sector, healthcare, financial services and professional services, with hands-on experience in large enterprise transformation and AI-led business change.