Cited answers where your team already asks
Install the Kelu bot in your Slack workspace and every channel becomes a front door to your knowledge bases. Questions get instant answers with citations — instead of pinging the one person who knows.
What the Slack bot does
The same RAG pipeline as the widget and API, delivered in-channel
In-Channel Answers
- Answers questions in channels and threads
- Citations link to the exact source document
- Grounded strictly in your indexed knowledge bases
- Low-confidence fallback instead of guessing
- Works for internal teams and shared customer channels
Simple Administration
- Installed per workspace from the dashboard
- Requests verified with Slack's HMAC signing
- Scoped to the knowledge bases you choose
- No per-user setup — everyone in the channel benefits
- Remove or reconfigure anytime
Knowledge Flywheel
- Every question is logged with analytics
- Gap analysis shows what the bot couldn't answer
- 👍 and 👎 reactions on an answer count as ratings
- Answered threads stop scrolling into oblivion
- Feedback on answers shows up in analytics
Ask the way your team already works
Mention @Kelu in a channel and it answers in a thread. Message it directly for a private answer, or use /kelu to post the answer for the whole channel. Turn on forum auto-reply mode and it answers new posts without a mention.
- Follow-ups in the thread remember the conversation
- Mentioned in someone else's thread, it reads the earlier messages first
- Files attached to a question help answer it and are never indexed
- Run several bots in one workspace, each with its own knowledge bases
- Answers include restricted documents, so pick each bot's knowledge bases with care
Maya10:42
@Kelu what’s the retry policy for failed webhooks?
KeluAPP10:42
A failed delivery is retried 5 times, with exponential backoff, over about 24 hours [1]. After the last try the event is marked failed and can be resent from the event log [2].
Sources:
• Webhooks: retries and timeouts
• Event log
Maya10:44
@Kelu can I resend one from the API instead?
KeluAPP10:44
Looking through the docs…
Answers you can check, from a system that won't guess
Every answer from your docs shows its sources
Numbered links point to the page and section each part of the answer came from, so anyone can check it in one click.
It says "I don't know"
When your content does not cover a question, Kelu does not guess. In a helpdesk it posts nothing and tags the ticket for your team.
Private stays private
Internal knowledge bases have no public surface at all. To keep past tickets private, add them to an internal knowledge base.
Got questions?
Frequently Asked Questions
Common questions about Slack Bot
The integration is scoped to the knowledge bases you select when installing it. Every answer is retrieved from that indexed content only, with citations back to the source — the bot never answers from the open internet.
Yes. Many teams run the bot in Slack Connect channels so customers get instant, cited answers from public docs, while a separate internal knowledge base serves employee-only channels.
Yes. Incoming requests are verified against Slack's HMAC request signing, credentials are stored per workspace integration, and answers draw only from your workspace's indexed content.
It says so. When retrieval confidence is low, the bot returns a transparent fallback rather than hallucinating, and the question is logged as a knowledge gap so you can fix the underlying docs.
Not for new setups. Slack can no longer be added as a new source; Slack sources added earlier keep syncing. The bot answers from your other sources, such as docs, wikis, repos and tickets.
Put answers in every channel
Install the Slack bot in a few clicks and connect it to your knowledge bases.
Free to start · No credit card required