Slackbot became an agent, and it kept the name
Salesforce made the rebuilt Slackbot generally available in January — a notification utility turned into an agent that searches enterprise data, drafts documents and acts on an employee's behalf, running on Claude. Thirty further AI features followed at a March event. The interface barely changed. What sits behind it changed completely.
This is the clearest example of the pattern Gartner is measuring. Nobody procured an enterprise agent. An existing chat tool, with existing permissions across an existing corpus, quietly acquired the ability to act — and the surface area of that change is the entire workspace it already had access to.
Keeping the name and the entry point is deliberate and effective product design: zero training cost, zero migration, immediate reach. It is also why the governance question is hard. Users who learned that Slackbot posts reminders have no particular reason to update their mental model to one that files documents and takes actions, and consent granted to the first is doing quiet duty for the second.
Expect this shape across every incumbent productivity suite, for the straightforward reason that it works. The competitive advantage of an incumbent was never model quality — it is already holding the data and the permissions.
Salesforce — Salesforce announces the general availability of Slackbot — your personal agent for work → · TechRepublic — Salesforce's AI assistant Slackbot gets general release → · SiliconANGLE — Salesforce transforms Slackbot into the ultimate work assistant with 30 new AI features →