# AI agents for Slack, built with Keiki Build an AI agent for Slack. It answers internal questions from your own docs and past threads, with the link, files the ticket while it is there, and tells you when it does not know instead of guessing. - Site: https://slack.onkeiki.com - Channel: Slack - Sign up: https://onkeiki.com/signup - Template: https://onkeiki.com/agents/new?template=company-brain (Company Brain) - Answers questions about: AI agent for Slack, Slack AI assistant for internal questions, AI answers from company docs in Slack, Slack support bot for IT and HR, internal knowledge bot Slack, AI triage in Slack channels ## What it is 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 your Slack agent does ### 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. ### 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. ### 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. ### 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. ### 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. ### 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. ### 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. ### Remembers the conversation It keeps the thread, so "and what about contractors?" is a follow-up rather than a fresh question with no context. ### Respects what people can see It answers from the sources you connect and does not surface what the person asking should not have. ### Hands over with the context When a human takes it, they get the question, the answer attempted, the sources used and what was promised. ## Your Slack agent vs Wiki search bot 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. - What comes back: your agent — The answer, plus the source link. / Wiki search bot — Ten results, sorted by keyword. - When it does not know: your agent — Says so, and routes the question to an owner. / Wiki search bot — Returns the closest-matching document anyway. - Follow-ups: your agent — Keeps the thread and answers in context. / Wiki search bot — Each query is independent. - Doing the thing: your agent — Files the request in the same thread. / Wiki search bot — Links to a form. - Stale content: your agent — Cites the document and its date, so you can see the age. / Wiki search bot — Ranks the 2021 page first. - Where it lives: your agent — In the channel, threaded on the question. / Wiki search bot — In a modal you had to open. ## 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. - 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 ## FAQ ### 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. ## How to connect an AI agent to Slack Full guide: https://slack.onkeiki.com/how-to-connect-an-ai-agent-to-slack (last updated 2026-08-30) Answers questions like: how to connect an AI agent to Slack, Slack AI bot setup, Slack app manifest bot token, AI assistant for Slack channels, connect AI agent to Slack workspace Pick the agent in Keiki, open the Slack setup it generates, and create the Slack app from that manifest in your workspace. Install it, paste the bot token and signing secret back into Keiki, then invite the bot to a channel and make that channel its home. The agent answers where it is mentioned from that point on. ### What you need before you start. - A Keiki account, which is free to create - Permission to create and install an app in your Slack workspace - The bot token (xoxb-…) and signing secret Slack shows after installing - A channel to invite the bot to and make its home, so it starts in one place instead of everywhere - Client ID and secret only if you plan to distribute the app to other workspaces ### Six steps from an empty channel to an agent that answers. 1. Create a Keiki account — Sign up at onkeiki.com. Slack costs nothing to connect: no phone number, no per-message fee from the channel itself. 2. Start from a template instead of a blank agent — Open the Company Brain template. It arrives able to answer from the docs your team already wrote, say when it does not know, and stay out of threads it was not asked into. 3. Let Keiki generate the Slack app — On the Channels page, add a Slack app and pick the agent. Keiki builds an app manifest with exactly the scopes and event subscriptions the agent needs and opens Slack with it, so you are not hand-checking a permissions grid. 4. Install the app in your workspace — Create the app from the manifest and install it. Slack then shows a bot token starting with xoxb- and a signing secret; both belong to your workspace, and the agent needs both to read events and prove requests came from Slack. 5. Paste the token and signing secret into Keiki — Back in Keiki, paste the bot token and signing secret. It checks them against Slack live and reports which scopes are granted. Add a client ID and secret too if you want the app installable in other workspaces. 6. Invite it to one channel, then make that channel its home — A freshly installed bot is in no channels, and Keiki only offers channels it belongs to — so invite it to one first, then pick that channel as its home and mention the bot there to prove the signing secret. Ask it something real while you are in there. ### Questions people ask while connecting an agent to Slack. #### Do I have to configure Slack scopes by hand? No. Keiki generates an app manifest for the agent with the scopes and event subscriptions it needs, and you create the Slack app from that manifest. You review one screen instead of assembling permissions yourself. #### Which Slack credentials does Keiki need? The bot token (it starts with xoxb-) and the signing secret from your installed app. The token lets the agent read and post; the signing secret proves each incoming event actually came from Slack. #### Will the agent reply to every message in a channel? No. It answers when it is mentioned and inside threads it has been brought into. A bot that comments on everything gets muted, so the default is deliberately quiet. #### Can I install it in more than one workspace? Yes, if you add the app’s client ID and secret when connecting. That turns the app into a distributable one, and each workspace that installs it shows up in Keiki against the same agent. #### What is the home channel for? It is where the agent posts when it has something to say that is not a reply — a digest, a heads-up, an escalation. Keiki only lists channels the bot has already been invited to, so invite it somewhere before you pick one. #### How do I check the connection is healthy? Keiki verifies the identity from the Channels page and reports routing status, including whether Slack is actually delivering signed events. If a token is rotated or an install is removed, you reconnect from the same row.