Slack AI: What Each Plan Includes, What It Costs, Where It Stops, and When an Agent That Acts Fits Better

Slack stopped selling Slack AI as an add-on on its website, so a small firm's decision is now which plan to pay for and how far its AI will stretch. Slack's help center says the add-on "is no longer available to purchase on the Slack website" and that the AI features now come with the plans. Below are the plans, prices and limits from Slack's own pages as of 30 October 2026, and the jobs that fit an agent that works as the person asking, inside their own business tools.

The short answer

• Pro adds conversation summaries and huddle notes. Business+ and Enterprise+ add search answers, recaps, file summaries, translations, workflow automation and Slackbot. Only Enterprise+ has enterprise search.
• Slackbot, Slack's personal AI agent, is the metered part: a trial or preview on Free and Pro, 15 messages per member per week on Business+, and no weekly or lifetime message limit on Enterprise+. Slack's pages also disagree on its daily task runs.
• Business+ is $15 a seat a month on annual billing and $18 on monthly billing, a monthly Pro seat is $8.75, and Enterprise+ goes through Slack's sales team. Switching the AI off does not lower the price.
• Slackbot now acts as well as reads, so the differences from an agent are what starts a job, which tools it reaches, and how use is metered.
• Add an agent for heavy individual use, for jobs that start in a business tool, or for tools Slackbot does not reach. Keep Slack's AI for reading Slack.

What Slack AI includes on each plan

Slack AI is the set of AI features built into Slack's paid plans, from thread summaries and search answers to the Slackbot agent. Slack lists them by plan in Updates to feature availability and pricing for Slack plans and Manage access to AI features in Slack. This table merges them and adds Slackbot's allowance from Slackbot limits and credit usage. The Free column in Slack's plan table is empty, and Free gets Slackbot only as a trial or preview.

Slack's guide to its AI features says AI responses use only information you can already see, and that search answers cite the messages or files behind them. Turning every AI feature off does not lower the plan price, so the AI is in the price whether anyone uses it.

What a seat costs

Slack's June 2025 announcement raised Business+ to $15 from $12.50 per user per month "to reflect the significant value added through new advanced AI capabilities and premium Salesforce integrations", with a footnote putting monthly billing at $18. Slack's billing policy uses $8.75 USD per member as the monthly Pro price in its worked example. For Enterprise+ the announcement says to contact your sales rep, and the pricing page showed "Contact sales for pricing" when we first read it and "€45 per user / month, when paying annually" when we read it again, so confirm that price with Slack. The page showed euro prices, so the dollar figures here come from the announcement and the billing policy.

Slack's plan article shows Business+ also adds Salesforce automations in Workflow Builder, list views and Sales Home, so the gap below covers the whole plan. This table sets the monthly gap from Pro to Business+ ($18 minus $8.75, or $9.25 a seat) beside the Kipwise agent at $10 per user per month, which sits on top of whichever Slack plan you keep and has a 3-user minimum.

Business+ buys Slack's own features and a Slackbot allowance. The agent buys work in your other tools. At these sizes the two monthly costs are close. For scale, the hire this work would otherwise go to costs about $800 a month at the $10 an hour median across 93 hourly Upwork posts, at 20 hours a week.

Where Slackbot stops

Slackbot is the part of Slack's AI that has usage limits. Slack describes it as "a personal AI agent with access to all of the context and information in your Slack workspace".

1. The plan floor. Free and Pro only get Slackbot during a trial or preview, and when the preview messages run out you must upgrade or turn on Flex Credits.
2. The weekly cap. Each Business+ member can send 15 messages to Slackbot per week, Monday to Sunday, resetting at 12 a.m. Monday in the member's time zone. Check the Slackbot cap against your busiest person, not your team average, because the limit is 15 messages per member per week, about three per workday. Someone who sends five a day is out by Wednesday. Techzine reported in April that Slack's CTO called the cap a first attempt the company needs to revisit, and the limits article still said 15 on 30 October.
3. Buying more, and who gets it. Slack's route for more usage is Salesforce Flex Credits, which need a connected Salesforce organization, and the pages we read describe no other. Guests and Frontline Members get no Slackbot, and an admin can turn it off for the whole workspace.
4. Task runs. Slackbot can run recurring tasks, and Slack's pages disagree on how many runs a day you get. The limits article says "you get three automatic task runs per day", How to work with Slackbot says "each task can run a maximum of three times per day", and the October 2026 changelog says "Slackbot can now run tasks automatically up to 15 times per day". Slack's own help pages give Slackbot two different daily task-run limits, three and fifteen, so treat any schedule you plan around either number as provisional. The changelog is the newest, so fifteen is probably current, but Slack does not say which page governs.
5. Accuracy. Slack's article on hallucinations says that if Slackbot says it does not know and you ask again without new instructions, it is likely to start hallucinating, and that you should verify information before deciding on it or sharing it. Practitioner reports predate Slack's 2026 Slackbot releases but point the same way: one Hacker News commenter said Slack's AI search "only covers a single silo (Slack)", and another reported a summary that "combined multiple people I work with into a summary that was negative in tone". These are author reports, not measurements.

What Slackbot can do beyond reading

Slackbot reads and writes Salesforce records, canvases, lists and calendars, and since October admins can let members use it to manage calendar events and draft and send email. Apps that ship an MCP server can connect: Slack's help article lets a person set each connected app to Always allow, Needs approval or Blocked, and Slack's developer docs say "Users can have up to 5 active MCP servers at a time". Slackbot's own page says you can tag it into a channel, and event-triggered tasks offer "ask me first" or auto-approval. Slackbot and an agent therefore both act, work in channels and ask for approval, and they differ in metering, triggers and reach.

Side by side: what starts a job, which tools it reaches, how it is metered

Slackbot's column comes from the Slack pages above, the agent's from Kipwise's product notes and pricing page. Both describe 30 October 2026.

Slack's post says event-triggered tasks "run on a message, a reaction, a list update, or a new channel", and all of those happen in Slack. Slackbot's event-triggered tasks start from events inside Slack, while the Kipwise agent can also watch events in your business tools directly, so check where a job's trigger happens before you choose. A failed payment, a new HubSpot deal or a paid invoice begins in another system. If a tool already posts into a Slack channel, a message-triggered task might catch it, but Slack's pages do not say whether messages from apps start tasks, so test that before you rely on it. A Workflow Builder workflow can also hand a conversation to Slackbot, and our guide to Workflow Builder or an agent covers which recurring jobs go where.

On reach, Slackbot covers Salesforce and the apps whose makers ship an MCP server for it, and Slack says its Marketplace lists them, so check each tool you use. The Kipwise agent works with each person's own connected accounts, so it reads only what the person asking can open, as our guide to per-user permissions explains.

On metering, a weekly message count and a monthly credit measure different things, so compare allowances before prices. The agent has a limit too: when a person's own $5 and the shared team credit are gone, that person pauses with a top-up link and everyone else keeps going.

When Slack's AI is enough, and when an agent fits

Stay with Slack's AI when the job is reading Slack. Summaries, recaps, huddle notes, translations and search answers with citations work on what you can already see, and Slack's guide walks through each. Stay with it as well when one of these holds:

• Each person asks a handful of times a week.
• You are on Enterprise+, where the weekly cap does not apply.
• Your CRM is Salesforce, which Slackbot reaches natively, while the agent's built-in CRM connections are HubSpot and Pipedrive.
• The question is about older history. Try Slack's own search first, because the agent's memory keeps short facts only from messages posted after install and never reads back through old history.

Add an agent when one of these holds:

• A job starts from an event in a business tool, such as a failed payment, a paid invoice or a new deal.
• One person would send more than about three requests a workday, where the Business+ cap bites.
• The tool is not one Slackbot reaches.
• You are on Free or Pro, where Slackbot is a trial. The agent's own trial is $2 of credit for 7 days on the fast model, or $10 for 14 days with all models on a paid Slack plan or with a card saved.

A worked Slack thread

Take Dana, a made-up owner of a 20-person agency on Slack Business+. The thread below is an illustration, and the real card wording will differ. Before a client call she asks Slackbot to prepare Thursday's brief and sends one follow-up, using two of her 15 messages for the week. Then she sets up recurring work in #ops with the agent:

> Dana: @Kipwise every Monday at 9, read the aged receivables report in QuickBooks and post what is over 30 days here. > > Kipwise Agent: I will post the invoices over 30 days here every Monday at 9, using your QuickBooks access. The schedule makes no changes on its own. Approve or Deny. > > Dana: Approve. And whenever a payment fails in Stripe, tell this channel. > > Kipwise Agent: I will post here whenever a payment fails in your Stripe account, after reading the record. Approve or Deny. > > Dana: Approve.

On Monday the report appears. Dana asks for a reminder to the first client, and the agent says the draft is in her Gmail drafts and shows the recipient, subject and preview on an Approve or Deny card that only she can use. She approves two reminders and denies a third.

The agent's runs draw on Dana's credit, not on her 15 Slackbot messages. If Slack's Marketplace shows a QuickBooks connection for Slackbot, a Slackbot task could do the Monday report instead. The failed-payment alert starts in Stripe, which is not on Slack's list of event starts. Every email waited for a card, so the person who owns the client relationship still decides what goes out.

When it goes wrong

• You hit the cap on Wednesday. Slackbot refuses new messages until 12 a.m. Monday. Spread the asks, move recurring jobs to tasks or an agent, buy Flex Credits if you have a Salesforce organization, or move to Enterprise+.
• A limit changes. Slack's changelog gives one task-run limit in July and another in October, so write the date next to any figure you plan around and re-read the limits article and changelog each month.
• An answer looks wrong. Slack's hallucinations article suggests asking again in a new chat, keeping conversations short and naming the channels or people to use.
• An approval card expires or a person runs out of credit. A card expires after 30 minutes and then the action does not run, so ask again. When credit runs out, only that person pauses, with a top-up link, and an admin can cap how much team credit one person may use. The guide to scheduling recurring agent jobs covers what to check each week.

How to check your own numbers

1. List your recurring jobs and what starts each: a request, a schedule, a Slack event, or an event in another tool. Our first-job filter for a small Slack team helps with the sorting.
2. Count the requests each person would send in a week, and flag anyone above 15.
3. Check Slack's Marketplace for a Slackbot connection to each tool, and ask the agent "what can you do?" for its list.
4. Price both routes for your headcount: seats times $9.25 for the Business+ gap, and seats times $10 for the agent.

What to do next

Today, ask your three busiest Slack users how many times a week they would send an AI a request. If anyone is above 15, or a recurring job starts from an event in QuickBooks, HubSpot or Stripe, mention the Kipwise Agent once in a thread and ask it to run that one job read-only first. It is $10 per user per month with a 3-user minimum, and the trial gives $2 of credit for 7 days on the fast model, or $10 for 14 days on a paid Slack plan.