Skip to content
← Writing

What Is Slackbot? Slack's AI Agent and How to Roll It Out

What is Slackbot? Plain-English guide to the AI agent in Slack: old vs new, what it does with Salesforce data, and a checklist before you switch it on.

26 Oct 2026·7 min read·Salesforce AI

Key takeaways

  • What is Slackbot now? Not the reminder bot you remember: since its general availability on 13 January 2026, it's Slack's built-in AI agent, powered by Anthropic's Claude.
  • It can search your conversations, prepare you for meetings and, with Salesforce connected, work with your CRM data and update records.
  • My central claim: Slackbot is only as safe and useful as your Slack and Salesforce housekeeping. Fix access first, then switch it on for one team.
  • Decide with a short checklist (below), not with a demo.

Salesforce says its highest-adopting employees save 20 hours a week with Slackbot, according to its March 2026 customer story. That number is why every Salesforce admin I know is being asked the same thing: what is Slackbot, and should we turn it on?

This is my plain-English answer, written for admins and leaders whose teams already live in Slack. I'm not going to review the features. I'm going to tell you how to decide.

What is Slackbot? A plain-English definition

Slackbot is Slack's built-in AI agent: you talk to it in normal language, and it finds information, summarises work and takes actions inside Slack.

Slack describes it as a personal AI agent for work that helps you find information, prepare for meetings and organise work directly in Slack. Salesforce's own announcement of general availability came on 13 January 2026.

The useful way to think about it: chat is where you ask, an agent is where you assign work. Slackbot sits between the two. You ask it something, and it can go and do the digging.

Salesforce's argument is that the advantage isn't the AI model. It's that Slackbot lives where people already work, with the context, conversations and permissions to surface and synthesise information quickly. I agree with that logic. I'd add the part vendors skip: that context includes every messy thing your people have ever typed.

Old Slackbot vs the new AI Slackbot

The old Slackbot notified you; the new one reasons over your work and acts on it.

Salesforce's announcement says Slackbot is built directly into Slack, understands your conversations, files, channels and the people you work with, and has nothing to install.

Old SlackbotNew AI Slackbot
What it isA notifier and helper botA built-in AI agent, powered by Claude
How you use itTriggers and canned repliesPlain-language requests
What it knowsLittle beyond its own settingsYour conversations, canvases and lists, within your access
What it doesReminds and respondsSearches, summarises, prepares you for meetings, takes actions
SetupBuilt inBuilt in; nothing to install, per Slack

If a colleague says "Slackbot told me to take a break", they're remembering the old one. That's a different product with the same name, and it's worth saying out loud in your rollout comms. Names that stay the same while the product changes cause real confusion.

Can Slackbot update Salesforce records and use CRM data?

With Salesforce connected, Slackbot can read CRM context, update records and turn live Salesforce data into interactive surfaces inside Slack.

Salesforce's Slackbot page says it can update CRM records, automate workflows, work across third-party apps and turn your Salesforce data into live, interactive app surfaces. Salesforce's Slackbot page also says it can turn your Salesforce data into live, interactive app surfaces in Slack.

At Dreamforce 2025, Salesforce unveiled Agentforce 360 with Slack as the conversational interface where people and agents work together.

Here are three examples of the kind of work this touches. They're hypothetical, so test them in your own org before promising them to anyone:

  • Sales: a rep asks Slackbot to summarise the deal thread and propose a next step, then approves an update to the opportunity.
  • Service: a support lead asks what changed on an escalated account since Monday, drawing on channel history and case context.
  • Operations: a manager asks for the week's open approvals and gets a list in the channel instead of opening three tabs.

One distinction matters for budgeting. Slackbot is a personal agent inside Slack. Agentforce is the Salesforce platform where you build agents for customers and employees. They connect, but they aren't the same purchase. If you're not sure where the line sits, read what Agentforce is and how Agentforce pricing works, and try the Agentforce pricing calculator, before you add anything to a budget.

My take: Most teams will judge Slackbot by how clever it sounds in a demo. They should judge it by what it's allowed to touch. The model is the easy part. Permissions, channel hygiene and who approves a CRM write are where rollouts succeed or quietly fail.

Should you turn Slackbot on? A six-point checklist

Turn it on for one team, with a named owner and a test you can fail, rather than for everyone on a Friday.

My rule for any agent is the same one I use in client work: start with one boring, frequent, low-risk task, keep a human approving, and let the agent earn wider access. Here's how that looks for Slackbot.

  1. Name the job. Write one sentence: "Slackbot helps the [team] do [task] so they save [hours]." If you can't write it, you're not ready.
  2. Audit channels and access. Look at private channels, shared channels and any channel that holds HR, finance or client data. An agent that searches Slack will find what people can already find, so tidy up what they shouldn't.
  3. Check your Salesforce sharing model. If a user can see an account in Salesforce, assume Slackbot can discuss it with them. If that makes you uncomfortable, fix sharing first.
  4. Run the permission test. Create a test user without access to a sensitive channel or record. Ask Slackbot questions designed to surface that content. If anything leaks, stop and escalate.
  5. Limit actions first. Begin with search and summaries. Add CRM updates only once the team trusts the answers, and keep a human approving writes.
  6. Measure hours saved. Pick a baseline now. Salesforce's own number comes from its highest adopters, so expect your average to be lower than the headline.

Don't skip the training. Salesforce's Trailhead has a Slackbot quick-look module that covers how Slackbot uses context, its key features and how to write effective prompts. Ten minutes of that will beat a long internal memo.

I haven't given menu paths for the admin settings. They change, and plan availability differs, so check Slack's current admin documentation and your contract before you promise a date.

What are the most common Slackbot rollout mistakes?

Most failures come from rollout habits, not from the technology.

  • Treating it as a chatbot. It's an agent with reach into your conversations and, if you connect it, your CRM. Govern it like a new hire with access.
  • Skipping the leak test. Years of "temporary" channels and open threads become searchable context.
  • Starting with write access. Let it read and summarise before it changes records.
  • No owner. Someone needs to own prompts, feedback and the metric. Otherwise it drifts.
  • Confusing it with Agentforce. Teams then budget for one and expect the other.
  • Declaring success on vibes. "People like it" isn't a result. Hours saved is.

If you're building agents beyond Slackbot, my three questions before you build apply here too. For a wider view of Salesforce AI guides, see the Salesforce AI hub. And if you want a second pair of eyes on your rollout plan, get in touch.

My take: Slackbot will be the first agent most of your staff actually use, and that's exactly why it deserves the strictest pilot. A weak first experience will colour how people feel about every agent you launch after it.

Try this week:

  • Write the one-sentence job for your pilot team and pick a baseline metric.
  • List every private and shared channel with sensitive data, and fix access.
  • Run the permission test with a low-access user.
  • Have your pilot team complete the Trailhead Slackbot module.

Frequently asked questions

What is Slackbot in simple terms?

Slackbot is Slack's built-in AI agent. You ask it questions or give it tasks in plain language, and it finds information, summarises conversations and helps organise work. It runs on Anthropic's Claude, according to press coverage of the launch.

Is the new Slackbot the same as the old Slackbot?

No. The old Slackbot was a simple notifier. The AI version, generally available since 13 January 2026, understands your conversations, files and channels and can take actions.

Is Slackbot the same as Agentforce?

No. Slackbot is a personal agent inside Slack. Agentforce is Salesforce's platform for building and running agents across the business. Salesforce positions Slack as the front door to its agentic enterprise, so the two connect, but you should plan and price them separately, and it's worth reading up on Salesforce Claude fees and Agentforce pricing before you do.

Can Slackbot update Salesforce records?

Salesforce says Slackbot can update CRM records, automate workflows and show live Salesforce data as interactive surfaces in Slack. I'd keep a human approving any write while you pilot.

Is Slackbot free?

At general availability, Salesforce said Slackbot is available to Business+ and Enterprise+ customers. Plans can change. Salesforce's page offers existing Salesforce customers a free Slack workspace to connect, but check Slack's pricing page and your contract for what's included.

Want to put this to work in your business?

Join one of my live sessions, or tell me what you're trying to do with AI.

Newsletter

Get the next one by email.

New writing on Salesforce AI, AI agents and the AI-Native Enterprise. Confirm by email; unsubscribe any time.

Keep reading