Put the sales playbook in every rep's pocket
Objection handling and battlecards, retrieved mid-call.
Your enablement team maintains battlecards, objection-handling guides, and pricing playbooks — and reps still improvise on calls, because nobody scrolls a 40-slide deck while a prospect is talking. New reps ramp slowly; tenured reps run on memory of last year's playbook.
Index the playbook, battlecards, and win/loss notes as a restricted internal knowledge base. Reps ask in the browser extension or Ask mid-call — "how do we counter the Kapa comparison?" — and get the current, approved answer with a citation. Knowledge base permissions keep competitive material internal, and question analytics show enablement which plays reps actually need.
How it works
- 1
Index the sales playbook, battlecards, objection-handling guides, and win/loss notes as a restricted internal knowledge base.
- 2
Turn off workspace-wide access and grant chat permission to the sales team; competitive material stays invisible to other members.
- 3
Reps ask in the browser extension's side panel or in Ask mid-call — "how do we counter the Kapa comparison?" — and get the current approved answer with a citation.
- 4
Enablement updates the playbook; the next sync updates every answer.
- 5
Question analytics show which plays and objections reps actually search for.
What you get
- Reps use the current playbook instead of last year's memory of it.
- New reps ramp with senior-quality answers from their first call.
- Competitive material stays governed behind permissions and restricted visibility.
- Enablement prioritizes content from real question data, not guesses.
Features that make it work
Got questions?
Frequently asked questions
Can we keep battlecards internal-only?
Yes. Keep them in an internal knowledge base, where every document is restricted, and scope it with per-knowledge-base chat permissions — only workspace members with access can query it, and it is never exposed through public widgets or client keys.
How do reps use this during a live call?
With the browser extension: the rep asks in the side panel and gets a cited answer in seconds without leaving the call. Ask offers the same assistant in the dashboard. Slack and Teams bots can't be connected to an internal knowledge base.
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.
Turn runbooks into an incident copilot
At 2am, the on-call asks and gets the runbook step — not a wiki search.
Make SOPs and playbooks answerable
Operational procedures people follow because they can find them.
Ready to put the sales playbook in every rep's pocket?
Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.
Free to start · No credit card required