The short version
- Slackforce is the Slack surface of [AIforce](/blog/aiforce). Its headline feature, Slackforce Surfaces, turns a plain-language request into a live, interactive interface, a dashboard, report, or executive deck, built from your Salesforce and Slack context.
- The interface lives in Slack, can be pinned to a channel, stays connected to the data, and refreshes on its own. No technical skill is required; Slackbot decides the best format.
- It caps a year: Slackbot went generally available in January 2026, gained about 30 AI features in March, and became an MCP client that can route work to Agentforce and thousands of apps.
- Parker Harris, now Slack’s CTO, calls Slackbot "the front door to the Agentic Enterprise." It is powered by Claude and runs on your existing Salesforce permissions with Zero Data Retention.
- Caveats: Slackforce is reported as beta, always-live refresh may not fully land until around October 2026, and the reference customers are large enterprises, not mid-market proof yet.
Salesforce Has One Argument, and It Keeps Making It
For most of 2026, Salesforce has been repeating a single idea: the place your team already works is Slack, so that is where Salesforce should come to them. At Dreamforce, the argument got a name and a feature. Slackforce is the Slack surface of AIforce, and Slackforce Surfaces is the part that makes people sit up. It was one of many launches at the event, which we round up in our Dreamforce 2026 recap.
We have written before about Slack becoming the CRM. Slackforce is that idea, shipped.
What Slackforce Surfaces Actually Does
You ask Slackbot, in ordinary language, for something like "show me this quarter’s pipeline by region and flag anything slipping." Instead of a text answer, it builds a live, interactive interface, a dashboard, a report, a microsite, even an executive deck, assembled from your Salesforce and Slack data. As Salesforce describes it, there is "no fixed template or prescribed format"; the system decides how best to express the work.
The result lives inside Slack, can be pinned to a channel for the whole team, stays connected to the underlying data, and refreshes as that data changes. Teammates can filter it, comment on it, and act on it together. The data spans Sales Cloud, Service Cloud, Data 360, and Tableau, and because Slackbot is now an MCP client, it can reach past Salesforce into Agentforce and other connected apps.
Engine, which handles over 800,000 customer inquiries a year, put the value plainly through its CEO Elia Wallen: "anyone on our team can just describe what they need and get a real, working interface back, without ever leaving the conversation."
The Year That Led Here
Slackforce did not appear from nowhere. Three moments built to it:
- January 13, 2026: the reimagined Slackbot goes generally available as a personal AI agent, for Business+ and Enterprise+, phased through February.
- March 31, 2026: roughly 30 new AI features, including reusable skills, meeting transcription, an MCP client, and a native CRM built into Slack for smaller teams.
- September 2026 (Dreamforce): Slackforce and Slackforce Surfaces launch as part of AIforce.
Slackbot is the personal-agent layer underneath. Salesforce’s own example: it can notice an account going quiet, read the support cases and Slack threads behind it, reassign the owner, create a follow-up task, and draft a win-back email, without you leaving Slack. It is powered by Claude, and testers during the general-availability period reportedly saved 30 to 90 minutes a day.
The Strategy: Slack as the Front Door
Parker Harris, co-founder of Salesforce and now Slack’s CTO, has been unusually direct about the ambition: "Slackbot isn’t just another copilot or AI assistant. It’s the front door to the Agentic Enterprise."
At the March event he went further: "Why should I ever log into Salesforce again? I built the Lightning UI. Maybe you never will. Maybe you will go into Slack." That is the whole thesis of AIforce, delivered through the tool that a million businesses already keep open all day.
The Honest Read
Slackforce Surfaces is the most genuinely useful piece of the Dreamforce lineup for a smaller team, because it attacks a real, everyday problem: getting a trustworthy report without waiting on an analyst. Self-serve, live, in the tool people already use is a good idea.
The caveats are the usual ones. Slackforce is reported as beta, and the always-live refresh may not fully roll out until around October 2026. "Stop logging into Salesforce" is aspirational; someone still has to configure the data model, permissions, and automations that make the describe-to-render output correct. And every new surface is a new place data can travel, so the Zero Data Retention and permission-inheritance promises are exactly the things to verify, not assume.
What a Mid-Market Team Should Do
Check what you already have. If you are on Business+ or Enterprise+, Slackbot is likely included. Model your Flex Credit consumption before you scale Surfaces across other tiers.
Pilot Surfaces against one real reporting need, not a demo. A weekly pipeline or case-load view a manager actually uses is the right first test.
Map Slack access to Salesforce permissions first. Before you let agents route work, confirm which channels and users correspond to which sharing rules, so an agent in Slack never surfaces what a person should not see. That mapping is exactly the kind of setup our Salesforce and Slack practice handles, and a free scoping call is the place to start.