A Team Bot your whole team uses in Slack
Publish one Bot to your team. Each person chats with it privately in the app or in Slack, it answers in threads, and each teammate’s use counts against their own allowance.
How it works
- Choose Publish to Team in a Bot's Share menu, either with its chat and memories or starting fresh. Your original Bot stays private.
- Teammates find it under Team Bots, each in their own conversation. The Bot keeps private notes for each person across the app, Slack and routines.
- In Slack it replies in threads, reads channels it has joined and answers workflow mentions. Approvals appear as a card only the requester can answer.
- A Team Bot asks before using a teammate's connected plugins. The owner and any Managers edit its plugins, secrets, skills and Slack app.
Starter prompt
You're our team's [operations / support / research] Bot in Slack.
In #[channel], answer questions using [Notion handbook / Drive folder]. Link the source for every answer.
If the answer isn't in our docs, say so and tag [owner] instead of guessing.
Once a week, post the 5 questions you couldn't answer, so we can fill the gaps in our docs.
Only reply in threads you're asked in.Business fit
Which businesses benefit, and how:
- StartupsSmall teams get a shared assistant that answers from the handbook instead of pinging the founder.
- AgenciesAccount managers share one Bot that knows each client's docs, with private notes per person.
- Local & serviceBusinesses with several locations on Slack answer staff policy questions the same way everywhere.
Watch-outs
- Team Bots are marked as a Teams feature in the changelog. Check your plan before you design around them.
- In Slack, @here and @channel from a Team Bot don’t notify anyone; it can mention a Slack user group instead.
- A shared Bot can read whatever its plugins reach. Connect the handbook, not the founder’s inbox.