Scale expertise across every account
Give CSMs instant cited answers to product questions, and give customers a self-service assistant that resolves how-tos before they land in your inbox.
Sound familiar?
CSMs are a relay between customers and product knowledge
A customer asks a setup question, the CSM asks support or engineering, and three people plus two days later the customer gets a paragraph. Multiply by every account.
Onboarding stalls on answerable questions
Time-to-value slips because customers wait on email round-trips for configuration questions your docs already cover — and slow onboarding is your most reliable churn predictor.
You find out about confusion at renewal time
You have no visibility into what customers struggle with between QBRs. The account that churned was asking warning-sign questions for months — somewhere you couldn't see.
How Kelu helps customer success
A self-service assistant for customers
The widget answers how-to and configuration questions from your docs and help center with citations, around the clock.
Instant answers for CSMs themselves
CSMs ask the internal assistant in Slack and get cited answers from product docs, release notes, and internal playbooks — no more relaying questions to engineering.
Question analytics per topic
Analytics show question volume, languages, and knowledge gaps, so you see what customers actually struggle with — a leading indicator instead of a renewal-time surprise.
Onboarding content that fixes itself
Gap analysis surfaces the missing onboarding docs, and doc proposals draft answers for them — closing the loop between customer confusion and published content.
Relevant sources & integrations
Common knowledge sources and delivery channels for customer success.
Got questions?
Frequently asked questions
Can we put the assistant inside our product for customers?
Yes. Embed the widget in your app, or build the assistant directly into it on the public REST API. React and JavaScript SDKs are on npm.
Can enterprise customers get a scoped assistant?
Yes. Client keys can be scoped with allowed source groups, so a customer-facing deployment retrieves only from the content that customer should see — useful for tiered docs or per-plan features.
How do we see which accounts or topics are struggling?
Workspace and knowledge-base analytics show questions per day, top sources, languages, and knowledge gaps, plus conversation history with feedback — signals you can act on before the renewal conversation.
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 bot installs in a few clicks.
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, 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, source groups, and hiding the widget's Kelu branding.
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.
Support Teams
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.
DevRel & Docs Teams
Turn your documentation, API reference, and community threads into a cited assistant that lives on your docs site, in Slack, and inside the IDE via MCP — and shows you exactly which docs to write next.
Bring cited AI answers to your customer success
Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.
Free to start · No credit card required