Slack has three different things it calls AI, and only one of them is an agent in the sense most people mean. The confusion is not your fault: Slack's own pricing page contributes to it. The plan cards for Free and Pro both print the line "Slackbot (personal AI agent)", which reads like an included feature. Slack's full comparison table, further down the same page, shows that row as empty for Free and empty for Pro.
What Slack actually ships under "AI agent"
Three distinct products wear the word agent, and telling them apart resolves most of the confusion.
Slack AI features are the assistive layer: thread and channel summaries, huddle notes with transcripts and action items, and AI search. These are not agents. They compress information that already exists so you read less. They are genuinely useful and they are the tier most teams actually have.
Slackbot is the personal agent. Slack's own description in the feature matrix is "Your personal AI agent that understands conversations, files and projects in Slack." That phrasing is precise and worth reading closely: the scope of its understanding is Slack. It knows what has been said, what has been shared, and what channel it happened in. Slack marks the row New and appends "Subscription limits apply."
AI assistant apps are the third-party layer: "Embed third-party agents and modern AI apps to work alongside you in Slack." This is where an outside agent platform appears as a participant in a channel, and it is available from Pro upward. It matters more than it looks, because it is the supported route to having an agent in Slack that can act outside Slack.
Alongside these sits Agentforce, the Salesforce agent layer that operates in Slack channels and DMs. If your company is already a Salesforce shop, that is the path Slack will steer you toward, and the economics are decided on the Salesforce side rather than the Slack side.
Which plan unlocks what
This is the table we wish Slack led with. Every cell below is taken from the "Compare all features" matrix on Slack's public pricing page, which is the authoritative version when it disagrees with the summary cards above it.
| AI capability | Free | Pro | Business+ | Enterprise+ |
|---|---|---|---|---|
| Thread and channel summaries | Not included | Included | Included | Included |
| Huddles notes | Not included | Included | Included | Included |
| AI assistant apps (third-party agents) | Not included | Included | Included | Included |
| Slackbot (personal AI agent) | Not included | Not included | Included | Included |
| Daily recaps | Not included | Not included | Included | Included |
| File summaries | Not included | Not included | Included | Included |
| AI language translations | Not included | Not included | Included | Included |
| AI workflow generation | Not included | Not included | Included | Included |
| Workflow Builder | Not included | Included | Included | Included |
| Conditional branching in Workflow Builder | Not included | Not included | Included | Included |
Two conclusions follow. The first is that Pro is the summaries plan, not the agent plan. If your reason for upgrading to Pro was the personal AI agent, the upgrade you actually need is Business+.
The second is about the size of that step. We are deliberately not printing dollar figures, for a reason explained in the next section, but the ratio is currency-independent: on Slack's own published list prices, Business+ is roughly 2.3 times Pro per user per month. For a twenty-person team that is a material line item, and it buys an agent whose reach is bounded by the workspace.
What we found researching this post
Two things surfaced while checking Slack's pages against each other, and both are the kind of thing you only find by reading the small print.
The plan cards contradict the comparison table. We pulled Slack's pricing page and read the per-plan bullet lists first. Under both Free and Pro, the string "Slackbot (personal AI agent)" is printed as a line item, along with "AI daily recaps", "AI file summaries" and "AI workflow generation". Read as a feature list, that says Free includes a personal AI agent. Then we read the "Compare all features" matrix on the same page and found those rows blank for Free and Pro, and marked Included only from Business+. The cards are a superset checklist showing what exists across the product, not what your plan grants. If you are budgeting from the cards, you will budget wrong.
Prices are geolocated harder than most vendor pages. This one is a caution about method as much as about Slack. Our fetch of slack.com/pricing returned Indian rupee prices. We then requested the explicitly US path and appended a US geocode parameter, and both still returned rupees: zero dollar-denominated prices appeared anywhere in over 690,000 characters of markup. So we have not printed USD figures we could not verify from the source. If you see a Slack price quoted in a blog post without a note about region, treat it as unverified. The safe move is to open the pricing page yourself, from your own billing country, and read the number it shows you.
The third observation is smaller but practical: Slack attaches "Subscription limits apply" to the Slackbot row and links out to a separate availability article. Included does not mean uncapped, and if you are planning to lean on the agent daily, that article is the page to read before you commit a team to it.
Slack AI agent use cases, and how to build each
Here is the part most overviews skip. Below are the four Slack agent jobs that come up most often, what the native tooling does with each, and where you need something with reach beyond the workspace.
Answering "has anyone dealt with this before?" This is the strongest native use case, because the answer genuinely is already in Slack. Slackbot and AI search read across channels, threads and shared files, and surface the prior discussion. It works best in workspaces with a real history and honest channel hygiene. Our walkthrough of an AI agent for Slack knowledge search covers how to scope this so it returns the decision rather than the argument that preceded it.
Collecting and posting standups. A recurring prompt, a set of people, a formatted summary. Slack's Workflow Builder handles the scheduling and collection natively, and AI workflow generation at Business+ lets you build it from a prompt. The part that usually breaks is what happens afterwards: the standup is meant to update a ticket, a board or a status doc that does not live in Slack. Our guide to running standup collection with an agent works through both halves.
Triaging inbound requests in a channel. A shared help channel fills with mixed requests, and someone has to route each one. Classification is a natural agent task, and doing it in-channel keeps the context. The catch is that useful triage ends by creating a ticket or paging an owner, which is an action in another system. See the Slack triage pattern for how to structure that hand-off.
Acting on something said in Slack. Someone posts "the Henderson invoice is wrong", and the actual work is in your billing system. No Slack-native agent finishes this task, because the finish line is outside Slack. This is what AI assistant apps exist for, and connecting an external agent to Slack is the mechanism.
The pattern across all four: Slack is an excellent place to ask and an excellent place to be told. It is not, on its own, the place where cross-system work gets finished.
Where a Slack-native agent stops
The boundary is the workspace, and it is a design decision rather than an oversight. Slackbot is defined by Slack as understanding conversations, files and projects in Slack. Everything it is good at follows from that, and so does everything it cannot do.
Concretely, the shapes that do not fit:
- The trigger is in Slack, the work is not. "Customer says the invoice is wrong" needs a billing system, not a channel.
- The work spans three tools. Read the thread, update the CRM, send the email. Each step is trivial; the sequence is the product, and it crosses boundaries the native agent does not.
- The answer lives outside Slack. If the authoritative record is in your data warehouse or your helpdesk, an agent that reads Slack is reading discussion about the answer rather than the answer.
- Nobody is asking. Slackbot is on demand. Work that should happen on a schedule, whether or not a human thinks to request it, is a different kind of agent.
None of this makes Slack's AI bad. It makes it a very good assistant for a specific surface. Problems start when a team buys Business+ expecting cross-tool automation and gets an excellent search-and-summarise layer instead.
How to decide, by situation
- You are on Pro and want the personal agent. Price the Business+ upgrade at roughly 2.3x your current per-user cost and multiply by seat count before deciding. Ask whether summaries plus a cross-tool agent would serve you better than the same spend on seats.
- You are already on Business+ or Enterprise+. Use Slackbot. You are paying for it, and it is strong at recall across a workspace with real history. Read the subscription-limits article so you know the ceiling.
- You are a Salesforce shop. Look at Agentforce in Slack first, and settle the economics on the Salesforce side, where they are actually decided.
- Your work crosses tools. Stay on the Slack plan you have and add an agent that reaches outward, connected via AI assistant apps. Our roundup of the cheapest AI agent platforms compares entry-level options on real all-in cost, and the best personal AI agents covers the assistant-shaped alternatives.
- You are on Free. There is no AI tier to evaluate. The comparison matrix shows the whole AI-powered work section unavailable, so the question is Pro versus an external agent, not which Slack AI to use.
Where Gravity fits next to Slack
Gravity is not a Slack replacement and has no interest in being one. Slack is where your team talks, and an agent native to that conversation is a reasonable thing to want. Gravity is for the work that starts in a conversation and has to finish somewhere else: you describe the task in plain language, and the agent carries it across the systems you already use, with Slack as one of them. Our walkthrough of connecting an agent to Slack shows the mechanics from the other direction.
On price, Gravity has a free tier at $0 a month with one agent, and paid plans start at $20 a month with a lot of usage included; buy more usage if you run out. The structural difference from a per-seat model is that Gravity's $20 is a workspace-level starting point rather than a per-person charge. Adding the eleventh person to a Slack Business+ workspace adds another full seat cost; adding the eleventh person who can ask an agent for something does not work the same way.
The honest recommendation: if your work genuinely lives in Slack and you are already on Business+, use the agent you have bought. If Slack is where your work is discussed but not where it is done, put your money on something that can reach the systems where it is done.
Frequently asked questions
Is Slackbot free?
Not as a personal AI agent. Slack's plan cards print "Slackbot (personal AI agent)" under Free and Pro, but the "Compare all features" matrix on the same pricing page shows that row as included only from Business+ upward. The older reactive Slackbot has existed in Slack for years; the AI agent version described as understanding your conversations, files and projects is the Business+ feature.
What is the difference between Slack AI and a Slack AI agent?
Slack AI is the assistive layer: thread and channel summaries, huddle notes and AI search, which compress information that already exists. A Slack AI agent, meaning Slackbot, reasons over your workspace and carries out multi-step requests. Summaries start at Pro; the agent starts at Business+.
Which Slack plan do I need for AI agents?
Business+ or Enterprise+ for Slackbot, daily recaps, file summaries, AI translations and AI workflow generation. Pro gets thread and channel summaries, huddle notes and the ability to embed third-party AI assistant apps. The Free plan does not include the AI-powered work features.
Can a Slack AI agent take actions in other tools?
Slackbot itself is scoped to Slack: Slack defines it as understanding conversations, files and projects in Slack. To act in another system you either build it in Workflow Builder with custom steps, or you embed an external agent through AI assistant apps, which is supported from Pro upward.
How much does Slack Business+ cost?
Slack localises pricing by billing country, and its pricing page served us regional rather than US pricing even on the explicitly US path, so we are not quoting a dollar figure we could not verify at source. The currency-independent fact is the ratio: Business+ is roughly 2.3 times Pro per user per month on Slack's published list prices. Check the page from your own country for the exact number.
What is Agentforce in Slack?
Agentforce is Salesforce's agent layer operating inside Slack channels and DMs, using conversational context to answer questions and take action. Because Salesforce owns Slack, it is the enterprise agent path Slack promotes, and its licensing and cost are determined on the Salesforce side rather than by your Slack plan.
Sources
- Slack pricing, specifically the "Compare all features" matrix, for AI feature availability by plan and the "Subscription limits apply" note on Slackbot, checked 8 September 2026. Prices on this page are localised by billing region.
- Introducing Slackbot, your context-aware AI agent for work, Slack, for the scope and positioning of Slackbot as a personal agent, checked 8 September 2026.
- Slack AI agents with Agentforce, Slack, for the Agentforce-in-Slack model, checked 8 September 2026.
- AI in Slack overview, Slack Developer Docs, for how third-party agents and AI apps integrate, checked 8 September 2026. Vendor plans and pricing change often, so confirm current terms before building a cost model.