Slack is preparing a new piece of its AI strategy: interactive tools created directly within conversations, without leaving the workspace to build a report, a visualization, or a small utility application. The feature is called Slackforce Surfaces and puts Slackbot at the center of the process: users describe what they need in natural language, while the assistant gathers relevant information from messages and connected applications to generate a shareable surface.
The result can take many different forms. Slack cites reports, polls, dashboards, presentations, and microsites, but the principle is broader: turning a chat prompt into an object the team can interact with. A Surface can be published in a channel, pinned among important content, and left available to colleagues, who can view, use, and comment on it without switching contexts.
Availability with updated data is slated for October. Slackforce Surfaces will be accessible to all Slack customers, including those on the free plan, provided that Slackbot is enabled in the workspace. It is a notable detail: the company is not limiting this initial rollout to organizations with enterprise contracts or to a separate add-on, although actual usage will depend on the assistant's configuration and the data sources connected by each company.
From prompt to shared component
The workflow outlined by Slack fits into the logic of so-called vibe coding—namely, generating software or interfaces through prompts formulated in natural language. In this case, however, the goal is not to deliver code to be edited in a development environment: it is to build an operational element within the collaboration platform. Anyone working in a channel could ask Slackbot to organize a visual summary, set up tracking, or model a forecast based on data available in the workspace.
In one of the demos shared by the company, the prompt calls for an arcade-style visualization of AI token usage. Slackbot then generates an interactive dashboard that breaks down consumption across departments like sales, design, and engineering. It is a useful example because it highlights the shift in perspective: the system does not simply summarize a discussion or return a text response, but produces an artifact that can become part of the everyday conversation.
Other cited examples include a real-time dashboard for a customer support queue and a financial forecast featuring a weather-themed presentation, powered by connected apps. The potential use cases thus range from data visualization to internal communications, as well as lightweight tools built for specific needs. Slack uses the term “Surfaces” specifically to identify these interfaces that emerge from dialogue and remain right where that dialogue takes place.
Google Drive, Salesforce, and the permissions challenge
The most sensitive part of the project inevitably concerns the information Slackbot can work with. To create a useful Surface, the assistant can draw from relevant conversations and connected applications, including Google Drive and Salesforce. A sales report, for instance, is only valuable if it cross-references messages, documents, and CRM data; simple graphic generation without access to enterprise sources would have a much narrower scope.
Slack states that the system will exclusively retrieve information for which the user has granted access permissions to its AI features. This clarification establishes a crucial boundary, but does not eliminate the need for internal governance. Organizations will need to determine which apps to connect, what data to make available to the assistant, and which channels can host tools derived from sensitive sources. In environments where documents, sales accounts, and operational conversations coexist, permission accuracy matters just as much as generation quality.
There is also a practical reliability issue. A quickly generated dashboard can speed up a meeting or make a situation scattered across multiple sources readable, but it risks obscuring the choices made when selecting and interpreting the data. Interactivity is no guarantee of accuracy. For use cases involving performance, forecasting, or customer activity, teams will need to be able to verify the origin of the numbers, how up to date the sources are, and the scope of the initial request.
Moreover, Surfaces do not replace specialized tools for business intelligence, project management, or software development. The real shift is different: bringing part of those activities to the very place where people already discuss, make decisions, and share context. This can reduce the constant switching between Slack, spreadsheets, slide decks, CRMs, and external services, especially for scoped analyses and materials intended for a single team's work.
Slack expands the role of its assistant
Slackforce Surfaces arrives after a series of updates through which Slack has made Slackbot less like a support bot and closer to a day-to-day work assistant. In recent months, the company had updated the product to summarize information scattered across channels, scan messages, and help find time slots for meetings. More recently, it had also introduced collaborative channels for vibe coding.
The new feature brings these strands together. On the one hand, it requires the ability to surface context from messages and applications; on the other, it brings the creation of structured, multi-user output directly into the chat. The shift is significant because the value no longer lies merely in Slackbot's individual reply. A Surface can become a shared reference point for the channel, be pinned, and gather feedback directly alongside the conversations that sparked it.
For Slack, the challenge will be to demonstrate that this immediacy does not lead to a proliferation of ad hoc tools, difficult to maintain or understand outside their initial context. Organizations already have overlapping dashboards, documents, and automations; making them easier to create can help autonomous teams, but it can also increase the number of informal resources. The ability to share and comment on Surfaces should also be seen as an attempt to keep these new interfaces within a collective process rather than turning them into isolated AI outputs.
Starting in October, we will see how effective the experience will be with real customer data and different permission configurations. The promise of Slackforce Surfaces is to reduce the distance between a conversation and the tool needed to move it forward. The limitation, as with many generative features aimed at work, will lie in the ability to maintain control, traceability, and quality as that transition becomes increasingly immediate.
