Back to Blog Home

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

A chat where someone asks how to set folder permissions and gets a reply pointing to the right page

Keep Slack's AI for reading Slack, and add an agent when a job needs something Slackbot does not give you: more than about three requests a workday from one person (Business+ caps Slackbot at 15 messages per member per week), a start from an event in a business tool such as a failed payment or a paid invoice, or a tool Slackbot does not reach. Slack no longer sells Slack AI as an add-on, so a small firm's real decision is which plan to pay for and whom the cap will bite.

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.

FeatureProBusiness+Enterprise+
Conversation and thread summariesYesYesYes
Huddle notesYesYesYes
Search answersNoYesYes
RecapsNoYesYes
File summariesNoYesYes
TranslationsNoYesYes
Workflow automation and AI workflow stepsNoYesYes
Canvas content generationNoYesYes
Enterprise searchNoNoYes
Slackbot messagesTrial or preview15 per member per weekNo weekly or lifetime limit

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 pricing announcement puts Business+ at $15 per user per month on annual billing, with monthly billing at $18. Slack's billing policy uses $8.75 USD per member as the monthly Pro price in its worked example. Enterprise+ goes through Slack's sales team. The pricing page lists it at $45 per user per month on annual billing next to a contact-sales button, and some views of the page show no price, so confirm it with Slack.

Business+ also adds non-AI features such as posting-permission control beyond #general and message activity analytics, so the gap below covers the whole plan and not only the AI. 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.

MembersSlackbot messages a week if everyone uses all 15Business+ over Pro, monthly billingKipwise agent, monthly
10150$92.50$100
20300$185$200
50750$462.50$500

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 the context 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 cap against your busiest person, not your team average: 15 a week is about three per workday, so someone who sends five a day is out by Wednesday. Slack's CTO has called the cap a first attempt that the company needs to revisit, Techzine reported, so re-read the limits article before you plan around the number.
  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 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 and How to work with Slackbot say three, while Slack's changelog says fifteen, and Slack does not say which page governs. Plan on three and treat fifteen as a bonus. The guide to scheduling recurring agent jobs covers what to check each week.
  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. It suggests asking again in a new chat, keeping conversations short, and naming the channels or people to use. Hacker News commenters on the earlier Slack AI reported that its search covered only Slack and that one summary merged several coworkers into a single negative-toned one. Those comments predate the 2026 Slackbot releases and are single reports, not measurements.

What Slackbot can do beyond reading

Slackbot reads and writes Salesforce records, canvases, lists and calendars, and 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 cap a user at 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.

QuestionSlackbot on Business+Kipwise agent
What can start a jobA request, a schedule, or a Slack event: a message, a reaction, a list update or a new channelA request, a schedule, or an event in a connected tool, such as a new HubSpot deal, a paid invoice, a failed Stripe payment or a matching email
Tools it reachesSlack, Salesforce, calendar and email where an admin allows, and apps with an MCP server for Slackbot, up to 5 active per personBuilt-in connections to Gmail, Outlook, Drive, HubSpot, QuickBooks, Xero, Stripe, Asana, ClickUp, Linear, Jira and more
Who it acts asYour Slack access, and your own account for connected appsThe person asking, on their own connected accounts
Asking before a changePer-app settings, a Confirm click on canvas edits, ask-me-first on event tasksAn Approve or Deny card for each live change, usable only by the asker, expiring after 30 minutes
How use is metered15 messages per member per week, daily task runs, more through Flex CreditsCredits: $5 a month of each person's own, then a shared $2 per user; top-ups from 20 credits
PriceIncluded in Business+ and Enterprise+$10 per user per month, minimum 3 users, on top of your Slack plan

Slack's post lists the starts for event-triggered tasks as a message, a reaction, a list update, or a new channel, and all of those happen in Slack. 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, and an admin can cap how much team credit one person may use. An approval card expires after 30 minutes, and then the action does not run, so ask again.

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 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.

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.

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.

Topics

Related posts

Put an AI teammate in your Slack

Free trial on install: $2 of AI credit for 7 days on the fast model, or $10 for 14 days with all models on a paid Slack plan or for existing Kipwise customers.