- Home
- Case Studies
- RAG Knowledge-Base Search
Users Couldn't Find Answers That Were Already Documented. So the Answers Started Finding Them.
Keyword search replaced with a RAG assistant that answers in plain language, cites its sources, and says 'I don't know' instead of making things up. Support tickets down 40%.
Written by Shubham(opens in new tab), Founder at BestlaTech · Published June 25, 2026
Engagement Type
AI Integration — RAG Semantic Search
Duration
6 Weeks
Client
B2B SaaS
Client
B2B SaaS Platform
Duration
6 weeks
Category
AI Integration / Knowledge Management
Markets
US
Improved Answer Quality
90%
Measured on an evaluation set, not vibes
Fewer Support Tickets
40%
For questions the docs already answered
Answers Cite Sources
100%
Every response links its source documents
Delivered in Production
6 wks
Fixed scope, fixed price
Key Facts
BestlaTech replaced keyword search with a RAG (retrieval-augmented generation) assistant over a B2B SaaS knowledge base — vector embeddings, semantic retrieval, and grounded LLM answers that cite their source documents, validated against an evaluation set before launch. Documented-answer support tickets dropped 40%.
Client:
A B2B SaaS platformWhat was built:
A RAG pipeline: document ingestion and chunking, vector embeddings in pgvector, semantic retrieval, and a chat assistant giving grounded, cited answersTimeline:
6 weeks, including retrieval-quality evaluation before launchEngagement model:
Fixed scope, fixed priceResult:
90% improved answer quality on the evaluation set; 40% fewer support tickets for already-documented questionsThe Challenge
Search That Required Knowing the Answer
Keyword search only matched the docs' exact vocabulary. Users searching in their own words — which is all users ever do — got zero results for fully documented topics.
Tickets for Documented Questions
Failed searches became support tickets. A large share of the queue was agents copy-pasting links to articles that search should have surfaced.
Docs Investment with No Payoff
The knowledge base was genuinely good — and effectively invisible. Every improvement to the docs was gated behind a search box that couldn't find them.
Retrieval Quality First. Grounded Answers Always. Measured Before Launch.
A RAG assistant is only as trustworthy as its retrieval and its restraint. We tuned the ingestion and retrieval against a real evaluation set before shipping, and constrained the assistant to answer only from what it retrieved — with citations, and with 'I don't know' as a first-class answer.
Chunking Tuned to the Docs, Not Defaults
Ingestion and chunking were designed around the knowledge base's actual structure — articles, steps, and version-specific sections — because retrieval quality is decided at ingestion time, not query time.
An Evaluation Set Before a Launch Date
We built a test set of real user questions (many mined from support tickets) with known correct answers, and measured retrieval and answer quality against it until the numbers justified shipping.
Grounded Answers with Citations
The assistant answers only from retrieved documents and cites them. If retrieval comes back weak, it says it doesn't know and offers the support path — a wrong answer is worse than no answer.
A Feedback Loop That Keeps It Honest
Thumbs up/down on every answer feeds the evaluation set. Weak spots show up in the data, get fixed in chunking or prompts, and get re-verified against the same benchmark.
Technologies Used
Key Features
Document ingestion and chunking tuned to the knowledge base's structure
Vector embeddings stored in pgvector — no new database infrastructure to operate
Semantic retrieval matching user vocabulary to docs vocabulary
Grounded LLM answers constrained to retrieved content, with source citations on every response
'I don't know' behavior with a support handoff when retrieval confidence is low
Automatic re-indexing pipeline as documentation is updated
Evaluation harness with a real-question test set, handed over at delivery
User feedback loop (thumbs up/down) feeding the evaluation set
Results & Impact
90% improvement in answer quality, measured against an evaluation set of real user questions
40% reduction in support tickets for questions the documentation already answered
Every answer cites its source documents — users can verify instead of trusting blindly
Docs vocabulary mismatch eliminated — users search in their own words
Evaluation harness handed over, so the team can measure every future change
Delivered in 6 weeks on fixed scope, fixed price
The knowledge base finally pays for itself. Users ask questions in their own words and get real answers with sources — and the support team spends its time on problems that actually need a human, not on copy-pasting links to page four of the docs.
Before vs After
| Before | After | |
|---|---|---|
| Search | Exact-keyword matching only | Semantic — users' own words work |
| Answers | A list of maybe-relevant links | Plain-language answer with citations |
| Unknown questions | Irrelevant results, dead end | Honest 'I don't know' + support handoff |
| Documented-question tickets | A large share of the queue | Down 40% |
| Quality measurement | None | Evaluation set gating every change |
If Your Users Open Tickets for Documented Answers, This Is Solvable.
Any product with a real knowledge base and a keyword search box has the same gap: the answers exist, and users can't find them. RAG closes that gap — when it's built with retrieval evaluation and grounding, not just a demo on top of an API.
B2B SaaS with a Real Knowledge Base
Your docs are good; your search is the bottleneck. A RAG assistant makes the existing investment findable — and ticket deflection is measurable within weeks.
Support Teams Above Capacity
If a meaningful share of tickets are answered with a docs link, that share is automatable — honestly, with citations, and with a clean handoff for everything else.
Internal Knowledge & Ops Teams
The same architecture works over internal wikis, policies, and runbooks — grounded answers with citations, so people trust what they're told.
Your Docs Already Have the Answers. Make Them Findable.
Most discovery calls take 30 minutes. By the end, you'll know whether your knowledge base is a fit for RAG, what retrieval evaluation looks like, and what a fixed-scope build involves.
Book Your Free Discovery Call (opens in new tab)Fixed scope. Fixed price. Zero surprises. Serving US, UAE & Singapore.
Frequently asked questions
How do you stop the assistant from hallucinating answers?
Does our documentation train the model?
What happens when we update our docs?
Which embedding and LLM stack does the RAG search use?
How long does a RAG build take?
Who builds RAG systems and AI-powered documentation search?
RAG or fine-tuning — which do I need for a documentation assistant?
How do you stop an AI assistant from making up answers about our product?
Talk to an expert
Get expert advice from our official advisors
More of Our Case Studies
Explore our diverse portfolio of successful projects and innovative case studies that showcase our expertise in delivering top-notch solutions.



