If your team decides in chat but reports in another tool, you know the gap. By the time someone builds the dashboard, exports the slide, and shares the update, the numbers have already moved.
That lag is expensive. It turns live work into stale summaries, and someone always ends up doing manual cleanup just to keep everyone looking at the same picture.
Salesforce moves live reporting deeper into Slack
Salesforce is trying to remove one of the most common workflow breaks in business software: the jump from conversation to reporting. In its announcement, the company said Slackforce Surfaces can turn chat context plus business data into live, interactive outputs directly inside Slack.
That matters less as a design flourish than as an operating model. If the surface updates itself and stays in the team’s working thread, the report stops being a one-time artifact and starts acting more like a shared control panel.
- AI-built surfaces. Salesforce introduced Slackforce Surfaces, which lets users ask Slackbot in plain language to create dashboards, reports, executive HTML decks and other interactive views inside Slack.
- Live data connection. Salesforce says those surfaces stay connected to underlying Salesforce and other data sources, and refresh automatically as the data changes instead of acting like static snapshots.
- Work stays in chat. The pitch is that teams can create and use these outputs without leaving the conversation, then ask follow-up questions about the live data in the same place.
- Part of a broader Slackforce push. The launch builds on earlier moves Salesforce described as Slack CRM and Slackbot actions across Salesforce through MCP, extending the idea of Slack as the working interface for business systems.
The real shift is from summaries to shared operating views
For a business owner, the important question isn't whether AI can generate a dashboard. It's whether your team can keep one trustworthy view in front of everyone while work is still moving.
Most teams don't struggle to produce a report once. They struggle to keep the report aligned with changing tasks, customer updates, approvals, and exceptions without creating a second layer of manual admin work.
Putting a live surface inside the conversation helps because it cuts down the delay between noticing an issue and acting on it. But it also raises a management question: what sources feed that view, what rules shape the output, and what happens when someone needs to turn the insight into an action?
That's where many AI demos stop short. A useful interface is only part of the workflow; the business still needs context, controls and repeatable follow-through.
Where Metomorph fits
Metomorph approaches the same business problem from the work object outward rather than from chat alone. Instead of creating a live view in a general conversation space, a team can organize the work inside Projects, where chats, documents, tasks, people and connected tools share one boundary.
Imagine your team is preparing a weekly revenue and delivery review for a client-facing project. In Metomorph, the assistant already has the project's context, so it doesn't need the team to restate the account history, the current tasks and the relevant documents each time they ask for an update.
From there, Dynamic reports can generate a live summary from the records Metomorph has access to, combining the numbers with a short explanation of what changed. If a manager sees a delay or a quiet deal, the team can move straight into the project's tasks and discussions instead of jumping between a report and a separate execution system.
That becomes more practical when the output has guardrails. With Business rules, a company can require approval for certain actions or enforce how updates are phrased before they leave the system, which is useful when AI-generated reporting starts getting close to customer communication or executive review.
The bigger lesson from Salesforce's move is that businesses want fewer handoffs. Metomorph is strongest when that same principle extends beyond the dashboard into the governed workspace where the follow-up work actually happens.
What to do next
- Map one reporting workflow that still depends on copying updates out of chat and into slides, dashboards or status emails. That's the clearest place to test whether a live AI-generated surface would actually save time.
- Separate the viewing problem from the action problem. A dashboard that refreshes automatically is useful, but decide in advance how issues found in that view become tasks, approvals or owner-specific follow-ups.
- Keep the data boundary tight. Start with one project or one team so the assistant is working from a defined set of records and documents rather than a vague mix of sources.
- Build a weekly review inside a single governed workspace first. The next step is to generate one live report from project records and task state, then see where your team still relies on manual follow-up.
Explore Projects, Project context, Dynamic reports in Metomorph.
Source: Salesforce, Slackforce Surfaces: AI-Built Dashboards, Decks & Reports in Slack (September 18, 2026).