Turn runbooks into an incident copilot
At 2am, the on-call asks and gets the runbook step — not a wiki search.
During an incident, the on-call engineer knows a runbook exists but not where, and wiki search returns three stale versions. Minutes of outage are spent finding the document instead of following it, and the engineer who wrote it is asleep.
Index your runbooks, postmortems, and architecture docs from GitHub, Notion, and Confluence, and the on-call asks the Slack bot in the incident channel: "how do I fail over the payments DB?" The answer comes back in seconds with steps and a citation to the canonical runbook — and gap analytics show which incidents had no runbook at all.
How it works
- 1
Index runbooks, postmortems, and architecture docs from GitHub, Notion, and Confluence into one knowledge base.
- 2
Install the Slack bot and switch it on in your incident channels.
- 3
During an incident, the on-call asks in-channel — "how do I fail over the payments DB?" — and gets the runbook steps with a citation in seconds.
- 4
Questions with no runbook behind them are logged as knowledge gaps, becoming your runbook backlog.
- 5
GitHub webhook syncs re-index runbooks on every push, so answers always match the latest revision.
What you get
- On-call engineers get the runbook step, not a wiki search, at 2am.
- Answers cite the canonical runbook, eliminating stale-version confusion.
- Every incident with a missing runbook surfaces in gap analytics.
- Runbook edits propagate to answers automatically via webhook syncs.
Features that make it work
Got questions?
Frequently asked questions
How current are the runbook answers?
GitHub sources can re-index via webhook on every push, and other sources sync on a fixed schedule. Answers always retrieve from the latest indexed revision, with a citation so the engineer can open the full runbook.
Can this run inside our existing incident channel?
Yes. The Slack bot answers on @-mention in any channel a Slack admin switches it on in with /kelu-enable-channel, including ad-hoc incident channels, and threads its answer under the question so the incident timeline stays readable.
How long does setup take?
Most teams are live the same day. You connect a source — a docs URL, GitHub repo, Notion workspace, or a file upload — and Kelu crawls, normalizes, chunks, and embeds the content automatically. The website widget is a single script tag, and the Slack bot installs in a few clicks. There is no model to fine-tune and no infrastructure to run.
Are answers backed by citations?
Yes. Every answer from your docs includes a structured citations list with the URL, title, and excerpt of each source used, and the answer text cites sources inline. Users can click through to verify any claim against the original document — which is what makes the answers trustworthy enough for support, sales, and internal use.
Is my content used to train AI models?
No. Your indexed content, embeddings, and conversations are isolated to your workspace and are only used to answer your own questions. Content is never shared across customers, and data is encrypted at rest and in transit. Enterprise plans add OIDC/SAML SSO, a widget without Kelu branding, and a custom SLA.
Which knowledge sources can I connect?
24 source types: websites, GitHub (docs files, source code, issues, pull requests, discussions), Notion, Confluence, Google Drive, OneDrive, Zendesk (Help Center and solved tickets), Jira, Jira Service Management, Linear, Salesforce Knowledge articles, Salesforce Cases, Discourse, Stack Overflow for Teams, YouTube, OpenAPI specs, S3, curated Q&A, and direct file uploads (PDF, DOCX, XLSX, CSV, Markdown, TXT, HTML). Sources sync on a schedule, and GitHub sources can re-index automatically via webhook on every push.
What happens when the AI is not confident in an answer?
Answers are grounded in your sources. When they do not cover a question, Kelu returns a transparent, configurable fallback — typically pointing users to your support channel — instead of guessing. Those unanswered questions are logged in knowledge gap analytics so you can close the gap in your docs.
Does Kelu work in languages other than English?
Yes. Kelu can answer in the language of the question (set it in a customization's Language field) while retrieving from your knowledge base, even if your docs are English-only, with citations back to the original pages. Workspace analytics break questions down by language so you can see which markets are asking what.
Related use cases
AI answers for company policies
"Can I expense this?" answered from the actual policy, with a citation.
Make SOPs and playbooks answerable
Operational procedures people follow because they can find them.
Put the sales playbook in every rep's pocket
Objection handling and battlecards, retrieved mid-call.
Ready to turn runbooks into an incident copilot?
Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.
Free to start · No credit card required