Grok Bot Slack gets a 7.8 out of 10 from me: the approval and privacy design is excellent, and setup clarity and usage control are where it drops points.
That score covers three things together: shared Bots in Slack, the Slack app connector and Slack-triggered routines.
I rated each one from the official docs at docs.x.ai and the release notes at x.ai/changelog/bot, and every rating below carries a one-line reason from those pages.
If you'd rather get a straight answer for your own business, book a free SEO strategy session with my team.
The verdict up front: 7.8 out of 10
Buy into it if your team already lives in Slack and you are on a Cursor team with Grok Bot.
Skip it for now if you are on Plus, work solo, or want an always-on listener across a busy workspace.
The 7.8 is the plain average of the eight criteria in the scorecard below.
It is an editorial rating from the documentation, not a benchmark run.
The scorecard: eight criteria, one reason each
| Criterion | Rating /10 | Why, from the docs |
|---|---|---|
| Setup clarity | 7 | Three separate connections (shared Bot app, per-person link, trigger account) plus a renamed Settings path. |
| Approval controls | 9 | A Review an action card in the thread that only the person who asked can answer. |
| Teammate privacy | 9 | Every chat with a shared Bot is private, even from the owner and Managers. |
| Slack triggers | 8 | Mention, phrase, reaction or any-message triggers, on one channel or all of Slack. |
| Usage control | 6 | Per-person billing is fair, but a busy-channel trigger can use a week of usage in a day. |
| Bot handoffs | 8 | A shared Bot passes work to the asker's own Bots and posts replies in the same thread. |
| Notification hygiene | 7 | @here and @channel never ping, user groups can, and routine posts skip your phone. |
| Admin controls | 8 | Access, Auto-add and audit events for Slack account links, from one admin page. |
Overall: 62 points across eight criteria, which rounds to 7.8.
Setup clarity: 7/10, because Slack means three things
The docs describe three different Slack pieces, and that is the main source of confusion.
The Slack app connector posts as the Slack user you connected, per Use the computer and apps.
A shared Bot has its own Slack app and handle, added by the owner or a Manager through Bring to your team's Slack.
A Slack trigger belongs to a routine and is connected on the Cursor account that owns the Bot, per the routine docs.
Then every teammate has to link their Slack account separately.
The Settings label also moved: v0.61.0 called it Team Bots, today's docs call it Shared Bots.
None of this is hard, but it's four steps where users expect one.
The docs do help: a message to the Bot before linking gets a reply with the linking steps, and since v0.78.1 unlinked people are told which features are limited.
There is also an admin gate, because the Slack app can sit at Awaiting admin approval until a Slack workspace admin approves it.
Chasing those per-person links is where most of the setup effort goes.
Approval controls: 9/10, the best part of the product
In a Slack thread, a shared Bot that needs approval posts a Review an action card with Allow once, Deny and View details.
Only the person who asked can answer it, a rule that arrived in v0.63.0 on 29 September.
Drafts are the default for outgoing Slack messages, and since v0.77.0 they show a formatted preview and who the post will notify.
Since v0.77.0, auto-review approval cards also stay open for 30 minutes instead of 10.
And since v0.75.5, a denied card makes the Bot stop until you send another message.
It loses one point only because turning drafts off hands sends to Auto Review, which the security docs describe as model-based and meant to complement other controls.
🔥 Rating tools is easy. Wiring them into a working team is the hard part. Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members comparing which agent setups hold up day to day. → Join the AI Profit Boardroom
Teammate privacy: 9/10, private by design
Privacy is per person: the owner and the Bot's Managers have no way to read a teammate's chat with it.
The Bot can save what it learns for the whole team, but it tells you when it does, and it keeps nothing about you personally for the team.
Unlinked Slack users are fenced off too: v0.77.0 stopped them from reaching the owner's logins or private data through the Bot.
In shared Slack conversations, the Bot checks each post against who can read it.
In channels and threads, a shared Bot uses only its owner's apps and asks before using yours.
The one gap: since v0.75.8, a Team Bot's routines can read any Slack channel you and the Bot are both in, so channel membership is the real privacy boundary.
Slack triggers: 8/10, flexible and well explained
Four trigger types are on offer: a mention of the Bot, a set word or phrase, your reaction to a message, or any message at all.
Each can watch one channel or the whole workspace, and When to run describes the trigger in plain words.
Since v0.77.0, message-listening Slack routines see images on the message that started them.
Since v0.75.5, a routine that replied in a thread keeps answering later replies there without an @mention.
Since v0.78.1, a Team Bot routine that needs your connector asks in its Slack thread and tags you.
It misses a 9 because only new messages count, so you can't backfill a trigger on older threads.
Usage control: 6/10, fair billing but easy to overspend
A shared Bot reply uses the usage of the person it answers, in Slack too, which is the fair way to split it.
Owners carry their own messages, along with whatever Slack apps or workflows post when no Cursor account is linked to them.
Since v0.75.5, routines can run up to 300 times an hour in total and 200 times an hour each.
The routine docs put the risk bluntly: point a trigger at a noisy channel and a week's allowance can vanish in one day.
Usage views also record activity as Grok Bot usage, not by model, according to the FAQ, so you can't see which model spent it.
That combination is why this is the lowest score on the card.
The docs do offer a clear fix: pause routines you don't need, widen schedules and narrow Slack triggers before raising any limit.
Teammates who run dry see Your usage limit has been reached, which at least makes the cause obvious.
Bot handoffs: 8/10, strong once you know the rule
Mention a shared Bot in a channel thread and it can hand work to that person's own Bots, with replies posted back in the same thread.
A personal Bot asked in a channel thread can't hand off, and says so.
A personal Bot in your own Slack DM can hand off, but the reply lands in the app chat, not Slack.
Since v0.77.0, teammates in a DM with a Team Bot can have it message other Team Bots.
The rule is logical, but the handoff docs need a table to explain it, which says something.
Notification hygiene and admin controls: 7 and 8
Since v0.68.1, a Team Bot can mention a Slack user group, while @here and @channel still don't ping anyone.
Since v0.75.8, Bot posts to Slack made for you, such as from a routine, don't notify your phone.
That keeps noise down, but it also means a routine's output can sit unread.
On the admin side, the Manage Shared Bots page handles Access and Auto-add, and the teams docs list Slack account links and routines among audit events.
Deleting a shared Bot removes its Slack app for everyone with no undo, which is correct but unforgiving.
How fast the Slack side has moved
| Version | Date | Slack change |
|---|---|---|
| v0.61.0 | 26 Sep 2026 | Team Bots launch; threads, joined channels, workflow mentions, routines managed from Slack |
| v0.63.0 | 29 Sep 2026 | Review an action card only the asker can answer |
| v0.68.1 | 7 Oct 2026 | User group mentions; @here and @channel still silent |
| v0.75.5 | 23 Oct 2026 | Routine threads followed without an @mention |
| v0.75.8 | 24 Oct 2026 | Routine posts skip your phone; routines read shared channels |
| v0.77.0 | 26 Oct 2026 | Draft previews, per-post audience check, 30-minute cards, images on triggers |
| v0.78.1 | 27 Oct 2026 | Unlinked users told how to link; connector requests asked in the routine thread |
Seven releases with Slack changes in about a month is fast, and most of them tightened safety rather than adding surface.
📞 Want a verdict on your own stack instead of mine? Book a free SEO strategy session and my team will look at how your business runs today and where an agent in Slack would and wouldn't help. → Book the free session
Strengths
- Approvals stay with the person who asked, even in a busy shared thread.
- Private per-person chats with a team-wide setup.
- Narrow, readable Slack triggers with images and thread follow-up.
- Handoffs from a channel mention to the asker's own specialist Bots.
- Steady release cadence on the Slack side.
Limits
- Four separate connection steps before a teammate gets the full feature set.
- Easy to overspend usage with a broad trigger.
- No view of which model handled a request.
- Shared Bots need a Cursor team, and Plus doesn't include Grok Bot at all.
- Silent routine posts can go unread.
Who should use it, and who shouldn't
Use it if you run a team of several people on Premium, Super or Ultra who already ask each other for summaries, drafts and lookups in Slack.
Use it if you have one person willing to own the Bot's rules, share list and weekly usage check.
Skip it if you are on Plus, work alone, or rely on email and phone more than Slack.
Skip it if you want the Bot to broadcast to everyone, because @here and @channel don't ping.
Plan details are on docs.x.ai/x-subscription/grok-bot.
Final verdict
7.8 out of 10, with an approval flow that keeps every risky step in the hands of the person who asked.
Set it up in one channel with one narrow trigger, keep drafts on for anything external, and check usage after the first week.
If you want trainings and live help building agents like this into your business, join the AI Profit Boardroom.
Also On Our Network
- 🌐 The four-step order for sharing a Grok Bot into Slack without the gotchas
- 🌐 Whether a shared Grok Bot in Slack pays off for a small team
- 🌐 Five copy-paste prompts that let your Agent OS run a Slack Grok Bot
- 🌐 The real GoldieBench scores behind the models a Slack Grok Bot might use
- 🌐 The complete Grok Bot Slack guide on the AI Profit Boardroom blog
FAQ: Grok Bot Slack Verdict
What is the weakest part of Grok Bot in Slack?
Usage control. Replies are billed fairly to whoever asked, but a Slack trigger on a busy channel can use a week of usage in a day, and usage isn't shown by model.
What is the strongest part?
Approvals. In a Slack thread the Bot posts a Review an action card that only the person who asked can answer, and outgoing Slack messages are drafts by default.
Is the 7.8 score a benchmark?
No. It is an editorial rating from the official docs and changelog, averaged across eight criteria.
Has Grok Bot's Slack support changed recently?
Yes. Releases from v0.61.0 on 26 September to v0.78.1 on 27 October 2026 added approval cards, draft previews, thread follow-up, image-aware triggers and limits for unlinked users.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Start narrow, keep drafts on and review usage weekly, then book a free SEO strategy session if you want a second opinion before you commit to a grok bot slack rollout.
