Production RAG That Ships: A Support-Bot Checklist You Can Actually Follow

Anyone can build a RAG demo. You wire an embedding model to a vector store, drop in your help docs, point a chat box at it, and within an afternoon you have something that answers questions about your product. It feels done. It is not done. The distance between that demo and a support bot you would actually put in front of paying customers is measured in weeks, and almost all of that distance is the unglamorous work nobody screenshots: retrieval quality, citations, evaluation, human fallback, and cost control.

This is the checklist for closing that gap — as of May 2026, with the patterns that have survived two years of shifting models. It is opinionated, it is ordered, and it assumes you want a bot that is useful the day it ships and still trustworthy a year later.

## Why the demo lies to you

A demo lies because you test it with the questions you already know it can answer. Real users do not. They ask things your docs do not cover, they ask in Hinglish, they paste error logs, they ask two questions in one breath, and they ask the same thing five different ways. The demo's 95% feels like production-ready. In production the same bot lands at 60% and the 40% it gets wrong is the 40% that generates angry tickets and churn.

The single highest-leverage shift in mindset: a production support bot's job is not to answer everything — it is to answer confidently what it knows and hand off cleanly what it does not. We took a RAG bot for an Indian insurance broker from a "I don't know" rate that masked confident wrong answers down to honest, grounded responses, and the win was not a better model — it was better retrieval and a stricter grounding contract. That full teardown lives in our insurance-broker RAG case study.

## The seven gates between demo and launch

Walk these in order. Each one catches a class of failure the previous gate cannot.

## Chunking and retrieval: where most bots quietly fail

If a support bot is giving confidently wrong answers, the problem is almost never the language model — it is that the wrong chunks reached the prompt. Three retrieval habits separate a shippable bot from a demo.

## Grounding and citations: the trust layer

A support bot that cites its sources is doing two jobs at once: it is being honest, and it is being debuggable. When a user can click through to the doc an answer came from, they trust it more — and when an answer is wrong, you can trace exactly which chunk misled the model.

The grounding contract is simple to state and hard to enforce: answer only from retrieved context, cite every claim, and say "I don't know" when the context does not support an answer. Enforcing it means testing for it. Your eval set must include questions your docs cannot answer, and the bot must decline them. A bot that confidently answers a question it has no source for has failed even if the answer happens to be right.

This is the same discipline that lets our in-house edtech product grade student work without inventing marks — on PenLeap the rule is identical: never assert what the source material does not support. The pattern we use there, refusing to hallucinate scores, is described in how PenLeap grades short answers without hallucinating marks, and it maps cleanly onto support RAG.

## Evaluation: the gate nobody wants to build and everybody needs

Here is the uncomfortable truth: if you cannot measure your bot, you cannot improve it, and you certainly cannot trust it in production. An eval set is the difference between engineering and guessing.

Run this eval on every change — a new model, a chunking tweak, a prompt edit. The teams that regress in production are almost always the ones who shipped a "small improvement" without re-running the suite. We treat prompt and retrieval changes the way we treat code: nothing reaches production without passing the eval gate, the same way we run a continuous eval pipeline across hundreds of prompt changes a week on our voice product.

## Human fallback and cost control: the parts that decide whether you can afford to run it

Two production realities sink bots that aced their demo: they have no graceful exit, and they cost more than the support headcount they were meant to relieve.

### Make the handoff invisible to the user

A good fallback is not a dead end that says "contact support". It is a warm transfer: the bot summarises the conversation, attaches the user's context, opens a ticket or pings a live agent, and tells the user exactly what happens next. The user should never feel demoted for hitting the edge of what the bot can do.

### Spend like the bill is yours, because it is

• Cache embeddings — re-embedding unchanged docs on every deploy is pure waste
• Cache answers to high-frequency questions and serve them without a model call
• Route by difficulty — a cheap fast model for easy queries, a strong model only when needed
• Cap retrieved context — more chunks is not better, it is just more expensive and noisier
• Set per-conversation token budgets and alert when they breach
• Track cost per resolved query weekly, not cost per API call

Cost control is not a launch-week afterthought — it is a design constraint from day one. A bot that resolves tickets but costs more per resolution than a human agent has negative ROI no matter how clever it is. Get the unit economics on a page before you scale traffic.

## The shipping checklist, one screen

Before you put a RAG support bot in front of real users, every box below should be checked.

• Corpus audited — stale, duplicate, and broken content removed
• Chunking respects semantic boundaries and preserves headings
• Hybrid retrieval (dense + keyword) with a reranker, recall@5 ≥ 90%
• Grounding enforced — answers cite sources, "I don't know" when unsupported
• Eval set of 50–200 real questions, run on every change
• Refusal and citation accuracy measured, not assumed
• Human fallback wired with full context handoff
• Caching, model routing, and context caps in place
• Cost per resolved query tracked against a budget
• Weekly read of real conversations on the calendar

None of this is exotic. It is craft. The teams that ship support bots that last are not the ones with the cleverest prompt — they are the ones who treated retrieval, evaluation, and fallback as the product, and the language model as a replaceable part. For the wider playbook on standing up a support bot end to end, our AI customer-support chatbot guide covers the operational side, and the PenLeap product case shows the same anti-hallucination discipline running in production. When you want a second set of eyes on an architecture or an eval setup, our AI automation team does exactly this.