01
Answers with the link
Every answer carries the doc or the thread it came from, so the person asking can check it and the person who wrote it gets the credit.
Your agent, on Slack
AI agents for Slack
The answer is already in the workspace.
Every team answers the same internal questions forever — expenses, access, deploys, policy, who owns this. Your agent answers them in the channel from what your team already wrote, links the source, files the request when one is needed, and says "I do not know" instead of inventing.
What it handles
Ten things it handles in the channel, without being asked twice.
02
Says when it does not know
An internal answer that is confidently wrong costs more than no answer. When the workspace does not contain it, the agent says so and routes the question.
03
Files the ticket while it is there
Access requests, laptop swaps, vendor forms: it collects what the form needs in the thread and files it, instead of pasting a link to a form nobody fills in.
04
Answers in the thread, not the channel
Replies stay threaded on the question. The channel does not turn into a wall of bot messages, and the answer stays attached to what it answered.
05
Triages the on-call question
"Is anyone seeing 500s?" gets checked against what is already known, then routed to the owner if it is new — with the context, not just a mention.
06
Handles the same question in five channels
The answer is the same in #eng, #support and a DM, because it comes from one source instead of five people remembering differently.
07
Onboards the new hire
The twenty questions every new joiner asks in week one get answered immediately, in private, without them feeling like they are interrupting.
08
Remembers the conversation
It keeps the thread, so "and what about contractors?" is a follow-up rather than a fresh question with no context.
09
Respects what people can see
It answers from the sources you connect and does not surface what the person asking should not have.
10
Hands over with the context
When a human takes it, they get the question, the answer attempted, the sources used and what was promised.
A real thread
It answers where the question was asked.
Nobody opens a knowledge base voluntarily. The question gets asked in the channel it was always going to be asked in, and the answer arrives there with its source attached.
Slack · #ask-itA Slack agent vs a search-the-wiki bot
Search returns ten documents. A colleague answers.
The usual internal bot is a search box in a Slack skin: it returns links ranked by keyword and leaves the reading to you. That is why people ask a person instead.
| Capability | Your Slack agent | Wiki search bot |
|---|---|---|
| What comes back | The answer, plus the source link. | Ten results, sorted by keyword. |
| When it does not know | Says so, and routes the question to an owner. | Returns the closest-matching document anyway. |
| Follow-ups | Keeps the thread and answers in context. | Each query is independent. |
| Doing the thing | Files the request in the same thread. | Links to a form. |
| Stale content | Cites the document and its date, so you can see the age. | Ranks the 2021 page first. |
| Where it lives | In the channel, threaded on the question. | In a modal you had to open. |
Start from a complete template
Company Brain
The complete template for internal questions: answers from what the team already wrote, with the link, and the ticket filed while the agent is already in the thread.
What comes with it
- Answers grounded in your own docs and past threads, with citations
- An explicit "I do not know", with routing to the owner
- Ticket and request filing from inside the thread
- Threaded replies that keep channels readable
- Conversation memory for follow-up questions
- Handover to a human with the sources and the promise attached
Questions
What people ask about running an agent in Slack.
- Where do its answers come from?
- From the sources you connect — docs, handbooks, past threads. Every answer cites what it used, so the person asking can verify it instead of trusting a bot.
- What does it do when the answer is not there?
- It says so plainly and routes the question to an owner in the same thread. It does not return the nearest-looking document as if it were an answer.
- Will it clutter our channels?
- It replies in threads on the message that asked, and only when it is addressed or asked something it can answer. Channels stay readable.
- Can it actually do things, not just answer?
- Yes — it collects what a request needs in the thread and files it, so access requests and internal tickets do not depend on someone opening a form later.
- How does it handle information people should not see?
- It only answers from the sources you connect it to, and it is meant to be scoped to what the channel it lives in should know. Sensitive requests are routed rather than answered.
- How long does setup take?
- Start from the Company Brain template, connect Slack and your first source, and put it in one channel. Expand once it has earned it.
Stop answering the same question.
Start from a complete template, connect Slack and the docs your team already wrote, and let the channel answer itself.