Internal helpdesk for IT and HR
"How do I get a laptop repaired?" answered without a ticket.
IT and HR answer the same internal questions on repeat — VPN setup, expense policy, parental leave — while the answers sit in a wiki nobody searches. Internal ticket queues have the same deflection problem as customer support, with none of the tooling.
Kelu indexes your Confluence, Notion, OneDrive, and Google Drive policy docs and answers employees in Slack or the internal Ask portal with citations to the policy source. Per-knowledge-base permissions keep HR knowledge separate from IT runbooks, and gap analytics show which policies are confusing enough to rewrite.
How it works
- 01
Index policy docs from Confluence, Notion, OneDrive, and Google Drive.
- 02
Separate HR and IT knowledge into distinct knowledge bases with their own permissions.
- 03
Employees ask in Slack or the internal Ask portal and get cited policy answers.
- 04
Gap analytics show which policies confuse people enough to be worth rewriting.
What you get
- Deflect repeat internal questions — VPN setup, expense policy, leave — without a ticket.
- Give employees the citation to the actual policy, not hearsay.
- Keep HR knowledge separate from IT runbooks with per-knowledge-base permissions.
- Find the confusing policies with data and fix them at the source.
Features that make it work
Got questions?
Frequently asked questions
Can HR content be kept separate from IT content?
Yes — run them as separate knowledge bases with independent sources and per-knowledge-base chat permissions, so each team's knowledge is queryable only by the right audience.
Do employees need another tool to learn?
No. The Slack bot answers where employees already ask, and the internal Ask portal is available for those who prefer a dedicated surface — both with the same cited answers.
What about sensitive policy documents?
Document-level visibility (public vs. restricted), knowledge base permissions, SSO, and audit logs govern access — restricted docs are only retrievable by authorized workspace members and in Slack or Teams channels with a bot.
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.
Related use cases
Compliance-safe AI answers
PII masking, access controls, and audit trails built in.
Learn moreSeparate knowledge across products and versions
Source groups keep Product A answers out of Product B chats.
Learn moreStop losing knowledge when people leave
Institutional memory that survives offboarding.
Learn moreReady to internal helpdesk for IT and HR?
Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.
Free to start · No credit card required