Slackbot is getting a broader job description. On September 17, 2026, the value of the Slackbot AI agent expanded with the introduction of Slackforce Surfaces, a feature that allows users to create custom views of data inside and outside Salesforce.
The change gives Slackbot a wider role around business data. Instead of limiting its value to a single existing experience, Slackforce Surfaces lets users shape how data appears across Salesforce and beyond it — a useful distinction when information refuses to stay in one system, as information tends to do.
The verified details are spare, but the central point is clear: Slackforce Surfaces is built around custom views. Users can create those views rather than relying on one fixed presentation, and the feature covers data inside Salesforce as well as data outside Salesforce.
A Broader Role for Slackbot
That expands what Slackbot represents within the Slack platform. The AI agent is no longer described only through its existing value; the introduction of Slackforce Surfaces adds a way for users to work with selected views of data connected to Salesforce and information beyond it.
The feature’s name also draws a line between the assistant and the data experience around it. Slackbot supplies the AI agent, while Slackforce Surfaces supplies the custom views. Together, the introduction places those two ideas in the same business workflow without requiring a new claim about how the feature operates.
Salesforce sits at the center of the announcement, but it is not the full boundary of the feature. Slackforce Surfaces allows users to create custom views of data inside and outside Salesforce, making the scope broader than a Salesforce-only presentation.
That distinction matters because the announcement does not describe a new data source, a new model, or a new numerical performance result. It describes a new way to create views. In enterprise software, that may sound less theatrical than a grand promise about artificial intelligence, but it is also the part users can understand without consulting a slide deck and a thesaurus.
Why the Expansion Matters
Gregg Willsky said, “The introduction will raise the utility of the Slack platform and further cement the starring role Slack has come to play at Salesforce.” His statement frames Slackforce Surfaces as an expansion of Slack’s practical value within Salesforce’s environment.
The quote also makes the strategic message plain: Slack is being positioned as an important part of how Salesforce users access and view data. Slackforce Surfaces supports that position by giving users custom views that extend beyond Salesforce itself.
The available facts do not provide pricing, user limits, release stages, technical specifications, or performance figures for Slackforce Surfaces. They also do not describe the exact controls users will receive when creating views, so the feature should be judged on the stated capability rather than imagined details.
What is established is narrower and more useful. Slackbot’s value has been expanded through Slackforce Surfaces; users can create custom views of data inside and outside Salesforce; and Gregg Willsky expects the introduction to raise the utility of the Slack platform while reinforcing Slack’s role at Salesforce.
That leaves Slackforce Surfaces with a straightforward pitch: give users a custom way to see relevant data across the Salesforce boundary, then place that capability alongside Slackbot. The idea is not flashy. It is also exactly the kind of practical expansion enterprise platforms use to become harder to ignore.
Based on
