Resolve tickets before they exist, draft the rest
Deflect repetitive questions at the widget and the support form, and give agents cited draft replies inside the helpdesk — so humans handle only the tickets that need them.
Sound familiar?
The queue is 60% questions the help center already answers
Password resets, plan limits, setup steps — customers skip the docs, file a ticket, and wait hours for an answer that was one search away. Your agents copy-paste the same links all day.
First response time keeps slipping
Volume grows with every signup while headcount stays flat. SLAs slip first on nights and weekends, exactly when frustrated customers are most likely to churn.
Macros rot, tribal knowledge walks out the door
Saved replies drift out of date with every release, and the agent who knew the billing edge cases just left. Every departure resets your team's answer quality.
How Kelu helps support teams
Ticket deflection at every entry point
The website widget and Support Form Agent answer questions as they are typed, grounded in your help center and docs with citations. Confidence scoring ensures only well-grounded answers deflect — everything else becomes a ticket as usual.
Copilot drafts inside your helpdesk
Connect Zendesk, Freshdesk, Front, Intercom, or Jira Service Management, and Kelu drafts cited replies from your knowledge base for agents to review, edit, and send.
Deflection analytics you can put in a QBR
Usage metering shows resolved-versus-escalated conversations, top questions, and the knowledge gaps behind escalations — real numbers for ticket volume impact.
Relevant sources & integrations
Common knowledge sources and delivery channels for support teams.
Frequently asked questions
How does deflection avoid annoying customers who really need a human?
Every answer carries a confidence score. Low-confidence questions are never blocked — the form submits or the conversation escalates to your support channel as normal. You tune the threshold, and simulations let you test deflection behavior against historical tickets before going live.
Which helpdesks does the copilot support?
Zendesk, Freshdesk, Front, Intercom, and Jira Service Management. The integration reads the ticket, retrieves from your knowledge base, and produces a cited draft reply for the agent to review — it never sends on its own.
Can we test the AI against past tickets before turning it on?
Yes. Simulations replay historical tickets through the assistant and produce reviewable results, so you can see exactly which tickets would have deflected and audit the answers before customers ever see one.
How long does setup take?
Most teams are live the same day. 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/Discord bots install in a few clicks.
Are answers backed by citations?
Yes. Every answer includes a structured citations list with the URL, title, and excerpt of each source used, so users can click through and verify any claim against the original document.
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.
Is there a free plan?
Yes. The Free plan includes 1 knowledge base and 100 AI questions per month — no credit card required. Pro comes with a 14-day free trial, and Enterprise plans add SSO, audit logs, and advanced governance features.
Solutions for other teams
Documentation Teams
Docs teams are judged on questions their pages actually resolve, not on word count. Kelu layers an AI assistant on top of your existing docs (Mintlify / Docusaurus / GitBook / ReadMe / VitePress / any HTML) — so the same pages answer questions on your site, in Slack, in the IDE, and via API — and closes the loop with gap analytics that turn unanswered questions into a prioritized editorial backlog.
DevRel & Docs Teams
Turn your documentation, API reference, and community threads into a cited assistant that lives on your docs site, in Discord, and inside the IDE via MCP — and shows you exactly which docs to write next.
Engineering Teams
Runbooks, ADRs, READMEs, and postmortems become a cited assistant in Slack and the IDE — so senior engineers stop being the search engine for the rest of the team.
Bring cited AI answers to your support teams
Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.
Get Started Free