<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kelu blog</title>
    <link>https://www.kelu.dev/blog/</link>
    <description>Guides on RAG, support AI and company knowledge from Kelu.</description>
    <language>en</language>
    <atom:link href="https://www.kelu.dev/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Test an AI Support Agent on Past Tickets First</title>
      <link>https://www.kelu.dev/blog/test-ai-support-agent-before-go-live/</link>
      <guid>https://www.kelu.dev/blog/test-ai-support-agent-before-go-live/</guid>
      <pubDate>Tue, 27 Oct 2026 00:00:00 GMT</pubDate>
      <description>Replay resolved tickets through the AI, run Draft only for a week, and set the confidence threshold from real answers before an AI support agent goes live.</description>
    </item>
    <item>
      <title>AI Search for Your Docs Site: Mintlify, Docusaurus</title>
      <link>https://www.kelu.dev/blog/replace-docs-site-search-with-ai/</link>
      <guid>https://www.kelu.dev/blog/replace-docs-site-search-with-ai/</guid>
      <pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate>
      <description>Swap keyword docs search for search with cited AI answers. Setup on Mintlify and Docusaurus, what works on GitBook, and how to measure the change with gaps.</description>
    </item>
    <item>
      <title>Company Brain: What It Means and How to Build One</title>
      <link>https://www.kelu.dev/blog/company-brain-how-to-build/</link>
      <guid>https://www.kelu.dev/blog/company-brain-how-to-build/</guid>
      <pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate>
      <description>Why wiki migrations fail, and how RAG builds a company brain across GitHub, Jira, Confluence, Notion and Drive, answering in Slack and Teams.</description>
    </item>
    <item>
      <title>Permission-Aware AI Knowledge Base With RBAC</title>
      <link>https://www.kelu.dev/blog/permission-aware-ai-knowledge-base/</link>
      <guid>https://www.kelu.dev/blog/permission-aware-ai-knowledge-base/</guid>
      <pubDate>Wed, 30 Sep 2026 00:00:00 GMT</pubDate>
      <description>Stop AI assistants leaking confidential docs across teams with document-level visibility, role-based access and scoped retrieval.</description>
    </item>
    <item>
      <title>Best Kapa.ai Alternatives for AI Docs in 2026</title>
      <link>https://www.kelu.dev/blog/kapa-ai-alternatives/</link>
      <guid>https://www.kelu.dev/blog/kapa-ai-alternatives/</guid>
      <pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate>
      <description>The top Kapa.ai alternatives for technical docs, developer portals and support automation in 2026: Kelu, Inkeep, Chatbase, Mintlify, GitBook and Glean.</description>
    </item>
    <item>
      <title>How to Deflect Support Tickets Before Submission</title>
      <link>https://www.kelu.dev/blog/how-to-deflect-support-tickets/</link>
      <guid>https://www.kelu.dev/blog/how-to-deflect-support-tickets/</guid>
      <pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate>
      <description>Auto-replies come too late: the ticket is already filed. Form deflection answers the question when the user presses submit.</description>
    </item>
    <item>
      <title>AI for Company Policies: From PDFs to Instant Answers</title>
      <link>https://www.kelu.dev/blog/ai-for-company-policies/</link>
      <guid>https://www.kelu.dev/blog/ai-for-company-policies/</guid>
      <pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate>
      <description>Policies only work if people find them at the moment of decision. How retrieval-augmented AI turns a policy library into answers employees actually use.</description>
    </item>
    <item>
      <title>Playbooks That Answer Back: Making SOPs Operational</title>
      <link>https://www.kelu.dev/blog/playbooks-that-answer-back/</link>
      <guid>https://www.kelu.dev/blog/playbooks-that-answer-back/</guid>
      <pubDate>Wed, 22 Jul 2026 00:00:00 GMT</pubDate>
      <description>A playbook nobody consults is documentation theater. Turning SOPs into an answer engine is how process actually changes behavior.</description>
    </item>
    <item>
      <title>RAG for Runbooks: Faster Incident Response</title>
      <link>https://www.kelu.dev/blog/runbooks-rag-incident-response/</link>
      <guid>https://www.kelu.dev/blog/runbooks-rag-incident-response/</guid>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
      <description>During an incident, the cost of finding the runbook is paid in downtime. Retrieval turns your runbook library into an on-call copilot.</description>
    </item>
    <item>
      <title>How to Evaluate RAG: Recall, Grounding, Abstention</title>
      <link>https://www.kelu.dev/blog/how-to-evaluate-rag/</link>
      <guid>https://www.kelu.dev/blog/how-to-evaluate-rag/</guid>
      <pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
      <description>Without a golden set and the right metrics, you can't tell a RAG improvement from a regression. The stack: retrieval metrics, answer metrics, abstention tests.</description>
    </item>
    <item>
      <title>Rolling Out Internal AI Without Scaring Legal</title>
      <link>https://www.kelu.dev/blog/governed-ai-for-internal-knowledge/</link>
      <guid>https://www.kelu.dev/blog/governed-ai-for-internal-knowledge/</guid>
      <pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
      <description>The fastest way to get an internal AI assistant blocked is to skip governance. Here is the checklist that gets policy and playbook Q&amp;A approved.</description>
    </item>
    <item>
      <title>Sales Playbooks That Answer Questions Mid-Call</title>
      <link>https://www.kelu.dev/blog/sales-playbooks-in-the-flow/</link>
      <guid>https://www.kelu.dev/blog/sales-playbooks-in-the-flow/</guid>
      <pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate>
      <description>Enablement content fails at the moment of the objection. Putting the playbook behind retrieval puts the approved answer in the rep's hands mid-call.</description>
    </item>
    <item>
      <title>The Employee Handbook Nobody Reads, and How AI Helps</title>
      <link>https://www.kelu.dev/blog/employee-handbook-ai-assistant/</link>
      <guid>https://www.kelu.dev/blog/employee-handbook-ai-assistant/</guid>
      <pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate>
      <description>Handbooks fail because they are optimized for legal completeness, not for answering questions. An AI assistant lets both goals coexist.</description>
    </item>
    <item>
      <title>Slack AI Knowledge Bot: Answers Where Work Happens</title>
      <link>https://www.kelu.dev/blog/slack-ai-knowledge-bot/</link>
      <guid>https://www.kelu.dev/blog/slack-ai-knowledge-bot/</guid>
      <pubDate>Tue, 05 May 2026 00:00:00 GMT</pubDate>
      <description>Knowledge tools fail when they demand a context switch. Putting a grounded AI assistant inside Slack meets questions where they are already being asked.</description>
    </item>
    <item>
      <title>Knowledge Gap Analysis: Build a Docs Roadmap</title>
      <link>https://www.kelu.dev/blog/knowledge-gap-analysis/</link>
      <guid>https://www.kelu.dev/blog/knowledge-gap-analysis/</guid>
      <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
      <description>A knowledge gap is a real question your content can't answer. Tracked systematically, gaps turn gut-feel docs planning into a ranked, evidence-based backlog.</description>
    </item>
    <item>
      <title>MCP Server Guide: Your Docs in Cursor and Claude</title>
      <link>https://www.kelu.dev/blog/mcp-server-for-docs/</link>
      <guid>https://www.kelu.dev/blog/mcp-server-for-docs/</guid>
      <pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate>
      <description>The Model Context Protocol lets AI assistants query your live docs instead of guessing from training data. What an MCP docs server does and why it matters.</description>
    </item>
    <item>
      <title>GEO for Documentation: Get Your Docs Cited by AI</title>
      <link>https://www.kelu.dev/blog/geo-for-documentation/</link>
      <guid>https://www.kelu.dev/blog/geo-for-documentation/</guid>
      <pubDate>Tue, 17 Mar 2026 00:00:00 GMT</pubDate>
      <description>Generative engine optimization is SEO's successor problem: your docs now need to win citations inside AI answers, not just rankings on a results page.</description>
    </item>
    <item>
      <title>How to Build an Internal Knowledge Assistant</title>
      <link>https://www.kelu.dev/blog/build-internal-knowledge-assistant/</link>
      <guid>https://www.kelu.dev/blog/build-internal-knowledge-assistant/</guid>
      <pubDate>Tue, 03 Mar 2026 00:00:00 GMT</pubDate>
      <description>The five-layer anatomy of an internal AI assistant — connectors, indexing, retrieval, governance, and interfaces — and a build-vs-buy framework for each.</description>
    </item>
    <item>
      <title>Hybrid Search Explained: Vector + Keyword with RRF</title>
      <link>https://www.kelu.dev/blog/hybrid-search-explained/</link>
      <guid>https://www.kelu.dev/blog/hybrid-search-explained/</guid>
      <pubDate>Tue, 17 Feb 2026 00:00:00 GMT</pubDate>
      <description>Semantic search misses exact IDs; keyword search misses paraphrases. How hybrid search fuses both with reciprocal rank fusion, and why to start with it.</description>
    </item>
    <item>
      <title>Why AI Chatbots Hallucinate: Citations and Abstention</title>
      <link>https://www.kelu.dev/blog/why-ai-chatbots-hallucinate/</link>
      <guid>https://www.kelu.dev/blog/why-ai-chatbots-hallucinate/</guid>
      <pubDate>Tue, 03 Feb 2026 00:00:00 GMT</pubDate>
      <description>Hallucination is a property to engineer around, not a bug to patch. How grounding, citations, and enforced abstention make a chatbot a trustworthy answerer.</description>
    </item>
    <item>
      <title>RAG vs Fine-Tuning for Docs Q&amp;A: Which Do You Need?</title>
      <link>https://www.kelu.dev/blog/rag-vs-fine-tuning/</link>
      <guid>https://www.kelu.dev/blog/rag-vs-fine-tuning/</guid>
      <pubDate>Tue, 20 Jan 2026 00:00:00 GMT</pubDate>
      <description>For Q&amp;A over your own docs, retrieval-augmented generation beats fine-tuning on freshness, citations, and cost. A decision framework for choosing between them.</description>
    </item>
    <item>
      <title>What Is Ticket Deflection? Definition and Formula</title>
      <link>https://www.kelu.dev/blog/what-is-ticket-deflection/</link>
      <guid>https://www.kelu.dev/blog/what-is-ticket-deflection/</guid>
      <pubDate>Tue, 06 Jan 2026 00:00:00 GMT</pubDate>
      <description>Ticket deflection is the share of support questions resolved without creating a ticket. Here is how to define it, measure it honestly, and raise it.</description>
    </item>
  </channel>
</rss>
