NewHelpdesk automation for Zendesk, Intercom & more

Turn your docs & helpdesk into verified AI answers

Kelu reads your docs, help center and past tickets, then answers customers and your team wherever they ask. Every answer from your docs links to its source.

Try:

Free to start · No credit card required

One knowledge base, answering in 8 places

Connects to the tools your team already uses

Zendesk logo
Zendesk
Intercom logo
Intercom
Freshdesk logo
Freshdesk
Front logo
Front
Linear logo
Linear
Jira Service Management logo
Jira Service Management
Salesforce logo
Salesforce
Slack logo
Slack
Microsoft Teams logo
Microsoft Teams
Notion logo
Notion
Confluence logo
Confluence
Zendesk logo
Zendesk
Intercom logo
Intercom
Freshdesk logo
Freshdesk
Front logo
Front
Linear logo
Linear
Jira Service Management logo
Jira Service Management
Salesforce logo
Salesforce
Slack logo
Slack
Microsoft Teams logo
Microsoft Teams
Notion logo
Notion
Confluence logo
Confluence
Google Drive logo
Google Drive
GitHub logo
GitHub
OpenAPI logo
OpenAPI
Mintlify logo
Mintlify
Docusaurus logo
Docusaurus
GitBook logo
GitBook
ReadMe logo
ReadMe
Discourse logo
Discourse
Stack Overflow logo
Stack Overflow
YouTube logo
YouTube
Google Drive logo
Google Drive
GitHub logo
GitHub
OpenAPI logo
OpenAPI
Mintlify logo
Mintlify
Docusaurus logo
Docusaurus
GitBook logo
GitBook
ReadMe logo
ReadMe
Discourse logo
Discourse
Stack Overflow logo
Stack Overflow
YouTube logo
YouTube

1. Add to your site or docs in one line

<script async src="https://widget.kelu.dev/kelu-widget.js" data-widget-id="…" data-client-key="kl_pk_…"></script>

2. Your visitors get verified AI answers

docs.acme.dev/api-keys
Ask Acme AI
Answers from Acme docs
How do I rotate an API key without downtime?

Create the new key first, then retire the old one. Rotating keeps the old key valid for 24 hours so running jobs do not fail1.

Call POST /v2/keys/:id/rotate, deploy the new key, and revoke the old one when traffic has moved2.

Sources

1API keys › Rotate a key
2Keys API reference
Was this helpful?
Step 1 · Read

Kelu reads everything your team has already written

Point it at your docs site, help center, past tickets, repos and wikis. Kelu turns each page into a clean document, keeps its headings, and keeps it in sync when the page changes.

Webhooks

docs.acme.dev/webhooks · re-checked daily · unchanged pages skipped

## Create an endpointchunk 1

Add your URL under Settings → Webhooks and pick the events to send.

## Verify signatureschunk 2

Each request carries an Acme-Signature header. Compare it with an HMAC of the raw body.

## Retries and timeoutschunk 3

A failed delivery is retried 5 times with backoff, then marked failed.

## Event typeschunk 4

payment.succeeded, payment.failed, payout.paid and 14 more.

Answers cite1docs.acme.dev/webhooks › Create an endpoint

The handoff

Every channel answers from the same knowledge base, so nothing drifts

docs/webhooks.mdhelp/billing-email.mdtickets/3920.mdopenapi.yamlrunbooks/payouts.md
Step 3 · Connect

Connect your stack once

Connect your helpdesk, wiki, repos and docs platform from the dashboard. Kelu keeps them in sync from then on.

Zendesk logo
Zendesk
Intercom logo
Intercom
Freshdesk logo
Freshdesk
Front logo
Front
Linear logo
Linear
Jira Service Management logo
Jira Service Management
Salesforce logo
Salesforce
Slack logo
Slack
Microsoft Teams logo
Microsoft Teams
Notion logo
Notion
Confluence logo
Confluence
Google Drive logo
Google Drive
GitHub logo
GitHub
OpenAPI logo
OpenAPI
Mintlify logo
Mintlify
Docusaurus logo
Docusaurus
GitBook logo
GitBook
ReadMe logo
ReadMe
Discourse logo
Discourse
Stack Overflow logo
Stack Overflow
YouTube logo
YouTube

Why teams trust the answers

Answers you can check, from a system that won't guess

Every answer from your docs shows its sources

Numbered links point to the page and section each part of the answer came from, so anyone can check it in one click.

It says "I don't know"

When your content does not cover a question, Kelu does not guess. In a helpdesk it posts nothing and tags the ticket for your team.

It stays in sync on its own

Zendesk tickets, Notion and GitHub issues every 5 minutes, help centers and Confluence every 10, GitHub repos hourly, websites daily. Unchanged pages are skipped.

A bad sync can't empty it

If one sync would remove more than 45% of a source's pages, Kelu holds the removals until a person approves them.

Private stays private

Internal knowledge bases have no public surface at all. To keep past tickets private, add them to an internal knowledge base.

Credentials are encrypted

Connection secrets are sealed with AES-256-GCM. If one can't be opened, the sync stops instead of running without it.

The $11,500/mo job, for $99/mo

What Kelu replaces vs. what it costs

What needs doing
Without Kelu
With Kelu
Support agent answering the same questions again
$4,000/mo
Engineer building and running your own RAG pipeline
$6,000/mo
Separate docs chat, Slack bot and helpdesk AI tools
$1,500/mo
Keeping answers in step with every docs change
manual
Answers at 3 a.m. on a Sunday
not possible
Total per month
$11,500+
$99/mo

Costs on the left are typical US rates. The price on the right is Kelu Pro. See pricing

Live on your docs in one script tag

  1. 1. Enter your docs site. Kelu crawls it and builds the knowledge base.
  2. 2. Ask it a few questions in the Playground and check the sources.
  3. 3. Enable Docs AI and paste its one-line script tag on your site.

<!-- in <head> or before </body> -->

<script async src="https://widget.kelu.dev/kelu-widget.js"

  data-widget-id="YOUR_WIDGET_ID"

  data-client-key="kl_pk_..."></script>

Got questions?

Frequently asked questions

All questions
One knowledge base, every channel

Ready to answer every question?

Enter your docs site and see Kelu answer from it in minutes.

Free to start · No credit card required