Deflect repetitive support tickets
Answer common questions before they become tickets.
Your support queue is dominated by questions that are already answered in your docs — password resets, plan limits, setup steps. Every one of them costs agent time, and volume grows faster than headcount. Agents burn out on copy-paste answers instead of solving hard problems.
Kelu indexes your help center, docs, and changelog, then answers customers instantly with cited sources in Docs AI, help center, Slack, or Microsoft Teams. Deflection analytics show exactly how many conversations were resolved without a human, so you can measure the reduction in ticket volume week over week.
How it works
- 1
Connect your help center, docs site, and changelog as sources — Kelu crawls and indexes them into one embedded knowledge base.
- 2
Drop the widget onto your site or help center with a single script tag, or install the Slack or Microsoft Teams bot for your community.
- 3
Customers ask in natural language and get instant, cited answers synthesized from your content.
- 4
Questions the AI cannot answer confidently fall back to your support channel, so nothing is blocked.
- 5
Deflection analytics show how many conversations resolved without a human, week over week.
What you get
- Deflect repetitive tickets before they ever reach your queue.
- Free agents to focus on the hard problems that actually need a human.
- Measure deflection with analytics instead of guessing at impact.
- Keep answers current automatically as your docs change, via scheduled syncs.
Features that make it work
Got questions?
Frequently asked questions
How do I know deflection is actually working?
Deflection analytics track conversations resolved without human involvement, and usage metering reports resolved/deflected counts per workspace. You can compare ticket volume trends in your helpdesk against deflected-conversation counts in Kelu to quantify the reduction.
Will the AI block customers from reaching a human?
No. Deflection is answer-first, not gatekeeping. High-confidence answers are shown with citations; anything below your confidence threshold shows nothing, and the ticket goes through to your normal support channel.
Which channels can deflect tickets?
The website widget (chat, sidebar, or Cmd+K modes), your support form via the form-deflect API, Slack and Microsoft Teams bots, and helpdesk-side deflection through the helpdesk integrations — all backed by the same knowledge index.
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.
Ready to deflect repetitive support tickets?
Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.
Free to start · No credit card required