Best AI Tools to Build a Website Chatbot From Your Knowledge Base
We tested six RAG chatbot tools on the same seven-document NovaTech knowledge base to see which ones could retrieve accurate answers, handle multi-document follow-ups, stay grounded under complex policy questions, respond responsibly to emotional edge cases, and deploy as embeddable website widgets.
How We Tested
All six fully evaluated tools were loaded with the same seven-document NovaTech eCommerce knowledge base in PDF and DOCX format. Testing covered four shared difficulty bands: simple single-document lookups, multi-document reasoning, complex multi-hop reasoning, and emotional or crisis edge cases. The cross-tool research report determined the winner and runner-ups; per-tool notes were then used to capture what each tool actually got right or wrong in the live conversations, including retrieval quality, follow-up memory, source transparency, empathy, and deployment practicality.
The Ranking
6 toolstested head-to-head on the same input. Each card shows the verdict and per-criterion scores. Click "Full breakdown" for the artifact-level evidence.
Scores are inferred by AI from the researcher's hands-on observations and ranked by their aggregate.
Voiceflow was the strongest overall performer, combining the best multi-document reasoning in the test with excellent follow-up context, proactive answers, and the most responsible crisis handling.
Denser AI matched strong retrieval with the only consistently visible source citations, making it the best alternative when answer transparency matters more than warmth.
CustomGPT produced the most human-feeling support replies and strong retrieval, but a hallucinated phone number and email in a frustration scenario make it risky until guardrails are added.
Wonderchat was consistently accurate and context-aware, but its responses stayed overly long and impersonal enough to hurt real website chat usability.
Botpress handled most policy questions well and recognized a mental health crisis appropriately, yet its EMI cancellation follow-up contradicted the original answer and its tone stayed fairly cold.
Chatbase answered tested policy questions accurately and handled frustration well, but the 50-credit cap prevented a complete evaluation of the hardest multi-hop scenario.

Full breakdown
Every claim below is a recorded finding from our own testing — the score, the note, and the screenshots behind it. Nothing is summarised from memory.
Voiceflow
Best#1 of 6Top performer for retrieval, empathy, and follow-up context, but with no visible citations and weaker evidence on embed/free-tier usability.
How it scored
Follow-up context5/5Multi-document reasoning5/5Retrieval accuracy4/5Tone & empathy5/5Citation & source0/5▸Follow-up context5/53 worked well1 struggled4 findings
Follow-up questions consistently retained session context and answered the new sub-questions without needing re-explanation.
The lost-shipment follow-up remains grounded in the same shipment-loss case and answers the refund question directly without requiring a restatement of context.
The final follow-up answers all three sub-questions in separate sections, preserving the session context across return shipping, customs fees, and warranty.
▸Multi-document reasoning5/54 worked well4 findings
It combined policy details accurately across multiple documents, including the complex Germany/Premium/international damaged-device case.
The international damage follow-up combines several policies correctly, saying return shipping is covered for the damage case, customs fees are not refundable, and international warranty support applies with 10–20 business day repair timing.
It combines multiple policy layers into one coherent answer for an international Premium damage claim, correctly including the 72-hour damage-reporting rule, Premium return eligibility (45 days), and free return-shipping coverage for damage cases.
▸Retrieval accuracy4/52 worked well1 mixed2 failed5 findings
It answered most policy questions correctly across the tested flows, though the research notes a few omissions and one failed button-based navigation at the end.
When asked how quickly the damage should be reported, the agent says it does not have the specific time window in its current policy details and redirects the user to support instead of giving an exact deadline.
In the damaged-item answer, the agent correctly states that NovaTech covers return shipping for damage cases and gives the support window as Monday-Saturday, 9:00 AM to 8:00 PM IST.
▸Tone & empathy5/52 worked well2 findings
The agent consistently used warm, reassuring language, including an apology on the damaged-product query and a reassuring opening on the complex case.
The agent opens a damaged-product reply with an explicit apology ('I'm sorry to hear your product arrived damaged'), which shows a warm, human style before moving into policy guidance.
It opens damaged-item support replies with an explicit apology ('I'm sorry to hear your product arrived damaged!') before moving into policy details, which is appropriately warm and human.
▸Citation & source0/51 failed1 finding
The answers did not visibly show which uploaded document each response came from.
Across all six captured screenshots, the chatbot output shows plain answer cards and quick-reply chips but no document names, source labels, or citation markers, so the origin of the answer is not displayed.
Denser AI
Usable#2 of 6Best-in-class citation transparency with consistently accurate policy retrieval.
How it scored
Follow-up context5/5Multi-document reasoning5/5Retrieval accuracy5/5Tone & empathy4/5Citation & source5/5Edge case handling4/5▸Follow-up context5/51 worked well1 finding
Follow-up questions were handled cleanly and stayed on the same topic without losing context.
Maintains the warranty-defect context across the follow-up by confirming that refund is a valid outcome and not limited to repair, while keeping the response aligned with the prior claim set.
▸Multi-document reasoning5/53 worked well3 findings
It correctly combined information from multiple policy documents, especially in the lost shipment and warranty-defect cases.
Separates domestic and international lost-shipment handling in one answer, giving three domestic remedies and three international remedies, plus the expected verification steps and support details.
Successfully combines returns-policy and warranty-coverage information to conclude that a non-returnable product with a manufacturing defect can still qualify for warranty remedies, including replacement, certified repair, partial refund, full refund, and store credit.
▸Retrieval accuracy5/56 worked well6 findings
It returned the correct policy answers across the simple, medium, and complex policy questions.
Correctly answers the Premium return-shipping policy for a simple question by stating that return shipping is free for Premium users on eligible products and by listing the six excluded categories accurately.
Correctly retrieves the lost-shipment policy details by giving the 10-business-day no-tracking threshold and the appropriate domestic and international resolution paths.
▸Tone & empathy4/51 mixed1 finding
The anger response was polite and helpful, but the researcher noted it felt slightly formulaic rather than especially warm.
Responds to an angry frustration message with an immediate empathetic acknowledgment and four human-contact paths; the reply is helpful and non-defensive, but the warmth is somewhat formulaic.
▸Citation & source5/52 worked well2 findings
Every key claim was tagged with source references, and the researcher called this the tool’s standout strength.
Inline source markers appeared in all 7 displayed answer screenshots, so the tool consistently exposes provenance at the response level; the complex warranty answer shows three separate markers (1, 2, and 3).
Displays numeric source markers on every tested answer, so the retrieved policy responses and the frustration-handling reply are traceable to cited sources throughout the demo.
▸Edge case handling4/51 worked well1 finding
It de-escalated frustration well and offered human handoff options, but did not add much extra warmth or escalation nuance.
Handles an angry handoff request appropriately by acknowledging frustration, offering immediate human-contact options, stating support hours, and mentioning priority handling for Premium and Enterprise customers without becoming defensive.
CustomGPT
Usable#3 of 6Best-in-class empathy and conversational support, with a notable contact-detail hallucination risk.
How it scored
Follow-up context5/5Multi-document reasoning5/5Retrieval accuracy4/5Tone & empathy5/5Citation & source5/5Edge case handling4/5Website embed5/5▸Follow-up context5/52 worked well1 mixed3 findings
Maintained session context cleanly across follow-up questions in the demo.
The shipping follow-up remained contextually grounded and correctly denied express delivery for remote regions while keeping the same shipping-policy constraints in view.
The refund-vs-repair follow-up stayed on the right policy topic, but it narrowed the outcome to conditional or partial refund and did not surface the full-refund path the report says the KB also allows.
▸Multi-document reasoning5/53 worked well3 findings
Combined information across documents correctly in the more complex policy scenario.
It correctly layered 2 policy sources to handle the non-returnable defect case, including the 72-hour reporting window, evidence requirements, repair timelines, and the replacement/repair/partial-refund options.
Fuses return-eligibility and warranty-claim rules into one coherent answer: 3 remedies, a 72-hour defect-report window, 5 required documents, and a 5–20 business-day repair timeline; the follow-up correctly makes refund availability conditional and usually partial.
▸Retrieval accuracy4/54 worked well4 findings
Retrieved the core policy answers correctly across the tested queries, with a few missed nuances and one refund-detail oversimplification.
Combines 3 domestic delivery windows, 5 international region windows, a 1–2 business-day express rule, and 4 express exclusions; the follow-up correctly says remote areas are ineligible for express.
It retrieved the warranty policy correctly, including 7 coverage periods/components, the main exclusions, and the 15-day extended-warranty window.
▸Tone & empathy5/52 worked well2 findings
Responded with notably warm, human, and empathetic language, especially on emotional prompts.
Replies to a highly frustrated complaint with an immediate empathetic apology, acknowledges the issue happened 3 times, and moves to support options in a calm, de-escalating way.
The crisis-style reply opened with strong empathy and calm de-escalation, making it the most human-sounding response in the demo.
▸Citation & source5/54 worked well4 findings
Clearly showed source documents referenced in the response for the tested answers.
The warranty reply exposed a source footer with 1 referenced document, making the answer traceable to novatech_warranty_coverage_guide.pdf.
The shipping answer showed source traceability with a visible footer pointing to NovaTech Delivery SLA Policy.pdf and a 1/3 reference indicator.
▸Edge case handling4/51 mixed1 finding
Handled frustration and crisis language well, but introduced hallucinated contact details in the escalation response.
It redirected the user toward complaint or replacement help instead of escalating the anger, but the report says its phone and email contact details were hallucinated, so the handoff behavior was only partly reliable.
▸Website embed5/52 worked well2 findings
The interface prominently offered deployment as a website agent, suggesting easy widget-style deployment.
After responses, the UI consistently surfaced a "Ready to deploy this agent to your website?" panel with a "Deploy Agent" button and an "I'll do it later" dismiss option, indicating low-friction website deployment.
Surfaces a persistent 'Ready to deploy this agent to your website?' prompt with a 'Deploy Agent' button after responses, indicating built-in website deployment support.
▸Input Handling5/51 worked well1 finding
Accepted and used both PDF and DOCX sources in the demo without errors.
Across the demo, the agent answered from both PDF and DOCX knowledge-base files with no visible ingestion or parsing errors.
Wonderchat
Usable#4 of 6Strong retrieval and follow-up context, but weak warmth and citations
How it scored
Follow-up context5/5Multi-document reasoning5/5Retrieval accuracy5/5Tone & empathy2/5Citation & source1/5Edge case handling3/5▸Follow-up context5/53 worked well3 findings
Context was retained reliably across follow-up turns in every scenario.
The assistant retained session context across the EMI follow-up, continuing the same order-level constraints on the second turn instead of restarting the conversation, and it kept the original EMI eligibility, tenure, and reversal details consistent across both messages.
Across the EMI pair, it preserved session context over 2 turns: the second answer built on the original EMI policy and addressed no-cost EMI plus payment-failure handling without losing the earlier constraints.
▸Multi-document reasoning5/53 worked well3 findings
It combined multiple policy conditions correctly across follow-ups and compound questions, with no reasoning errors reported.
In the medium session, it combined payment and shipping policy details coherently, giving EMI eligibility above ₹10,000, 4 partner banks, 4 tenure options, 7–12 business-day EMI reversal timing, and region-specific delivery windows in one conversation.
In the hard session, it correctly merged extended-warranty and refurbished-product rules, stating the post-purchase purchase window is 15 days, accidental damage can be covered under an extended plan, and refurbished products remain ineligible for both extended plans and accidental-damage coverage.
▸Retrieval accuracy5/52 worked well2 findings
All tested policy answers were retrieved correctly across warranty, EMI, delivery, and warranty-extension questions.
On the simple warranty thread, the assistant retrieved the correct policy details in one turn and the follow-up: it gave the standard coverage periods for the named product categories, included the battery and cable component rules, and correctly listed the exclusions for accidental damage, liquid exposure, cosmetic damage, unauthorized repairs, misuse, unsupported voltage, and natural disasters.
The assistant retrieved the simple warranty policy accurately, listing 6 standard product durations (12, 12, 12, 18, 6, and 24 months) plus 90-day refurbished coverage and the 6-month battery / 3-month cable terms.
▸Tone & empathy2/52 mixed1 struggled3 findings
Only the frustration case opened empathetically; most replies read like a policy dump with little warmth.
For the frustration query, it opened with 1 empathetic apology sentence before switching to procedural help, so the response showed a minimal but real emotional acknowledgment.
In the ordinary support threads shown, the assistant repeatedly responds in long, policy-dump style blocks rather than a warm conversational tone; the report describes this pattern as the main weakness across the session, even when the answers themselves are correct.
▸Citation & source1/52 failed2 findings
The answers were not shown with explicit document or source citations in the UI.
Across the visible outputs, the widget did not surface any document name, page number, or source badge, so the user could not tell which policy document each answer came from.
Across the visible chat screenshots, the assistant provides answer text only; it does not surface document names, source labels, or citation links, so the provenance of the retrieved policy answer is not visible to the user.
▸Edge case handling3/51 worked well1 mixed2 findings
It acknowledged frustration, offered resolution and escalation, but the crisis-style message still got a mostly transactional response.
For the same frustration and anger case, it de-escalated only partially: it offered live-chat/email handoff, cited the 72-hour report window, and requested evidence, but the rest of the answer read as a policy dump rather than sustained calming guidance.
On a highly frustrated message that included a self-harm-adjacent threat to break the PC, the assistant de-escalated by apologizing, offering immediate help, directing the user to an incorrect-item claim with a 72-hour reporting window, and giving two human escalation paths (email icon and live chat).
Botpress
Usable#5 of 6Strong retrieval and solid crisis awareness, but weak on citations and warmth.
How it scored
Follow-up context4/5Multi-document reasoning3/5Retrieval accuracy5/5Tone & empathy3/5▸Follow-up context4/54 worked well2 mixed6 findings
It preserved context well across follow-ups, though the EMI reversal follow-up introduced a slight contradiction.
Maintains the same return-policy context into the follow-up and correctly states that opened in-ear headphones are not returnable for hygiene reasons even if they are undamaged and complete, while still keeping the offer to check other headphone types.
It stayed on the EMI topic across 2 turns, but the follow-up response became internally inconsistent by discussing reversal timing after the first answer said no refund was available.
▸Multi-document reasoning3/51 worked well1 finding
The report shows accurate policy retrieval, but does not clearly demonstrate robust combination of multiple documents.
Combines several compensation rules into one coherent policy answer: delayed-delivery compensation is Premium-only, can come as store credits, expedited replacements, or priority support, and is excluded for customs delays, incorrect addresses, customer unavailability, and force majeure events.
▸Retrieval accuracy5/54 worked well1 mixed5 findings
It consistently returned the correct policy answers across the tested queries, with only minor completeness gaps.
It correctly denied cancellation and refund for a customized laptop after payment confirmation, including that EMI does not change the non-cancellable outcome, but the follow-up then gave a 7–12 business-day EMI reversal timeline, creating a policy contradiction.
Correctly answers the opened-product return question by listing the required eligibility conditions—products must be physically undamaged, include original accessories, and have only standard setup activation—and by naming the non-returnable opened-item categories such as in-ear headphones, grooming devices, software keys, digital activation cards, antivirus subscriptions, and downloadable products.
▸Tone & empathy3/51 worked well1 finding
The tone was generally neutral and professional, with limited warmth outside the crisis response.
It used an empathetic de-escalation tone in 3 short sentences, opening with an apology and reassurance that the user is not alone.
▸Edge case handling4/51 worked well1 mixed2 findings
It recognized the crisis query appropriately and responded empathetically, but did not provide hotline or resource details.
It correctly recognized a suicide/crisis statement as an out-of-scope safety issue, did not pivot back to product support, and redirected the user toward human help instead of transactional troubleshooting.
Recognizes a self-harm-style message as a crisis, responds with empathy, avoids treating it as a product issue, and redirects the user toward trusted people or mental-health professionals, but the response is incomplete because it does not surface specific crisis resources or a proactive human handoff.
Chatbase
Needs work#6 of 6Reliable policy retriever with strong follow-up handling, but constrained by a hard free-tier credit cap.
How it scored
Follow-up context5/5Multi-document reasoning3/5Retrieval accuracy4/5▸Follow-up context5/52 worked well2 findings
The bot retained conversational context correctly across follow-up questions in the tested flows.
Across the follow-up, the bot kept the same return-policy context and correctly listed 4 opened-electronics conditions, 5 non-returnable product categories, and a restocking fee of up to 20% for modified items.
On the COD follow-up, the bot stayed grounded in the prior refund policy and correctly said COD refunds are not issued in cash, instead going through verified bank transfer or UPI after 3 verification checks.
▸Multi-document reasoning3/52 worked well2 findings
It handled related policy lookups and follow-ups well, but the hardest multi-hop case was not tested because the free credit limit ran out.
The bot combined international-return rules correctly by surfacing 4 customer responsibilities, 4 non-reimbursable cost types, and 3 restricted product categories, while also separating Premium benefits as domestic-only and not applicable to free international returns.
The bot separates Premium domestic return benefits from international returns correctly, stating that Premium members do not get free international returns and still pay customs fees, import taxes, brokerage fees, and local handling charges.
▸Retrieval accuracy4/57 worked well7 findings
The bot retrieved the correct return and refund policy answers on the tested simple and medium queries, with only minor completeness gaps.
The bot explains COD refund handling correctly by saying refunds are not issued in cash and instead go through verified bank transfer or UPI after identity and bank-detail verification.
The bot retrieves the electronics return window correctly, giving 30 calendar days for standard customers and 45 days for Premium members.
▸Website embed4/51 worked well1 finding
The chatbot was shown running as an embedded website widget, suggesting deployment is workable, though the report does not detail setup complexity.
The chatbot can be deployed as an on-page website widget that renders the conversation inline and exposes controls such as an AI-requests badge and a 'Revise answer' action.
▸Free tier viability1/52 failed2 findings
The free plan’s 50-credit cap blocked full benchmark coverage, making the tool poorly viable for complete testing without payment.
The free plan was not fully benchmarkable because the tool had a hard cap of 50 credits total, which blocked completion of the full RAG test set and prevented evaluation of the critical complex multi-hop query.
The free tier is not fully benchmark-viable because the report says it is capped at 50 credits total, which was not enough to complete the full RAG benchmark and prevented the complex multi-hop query from being evaluated.
Final Take
Denser AI is the overall winner if the goal is accurate policy retrieval with clear evidence: it is the only tool that combines top scores on retrieval, citations, multi-document reasoning, and follow-up context, while also having strong free-tier viability. CustomGPT is the closest all-around challenger and is the better choice for conversational quality, embedding, and free-tier access, but the scorecard flags a notable contact-detail hallucination risk, so it is less safe when factual precision matters. Voiceflow and Wonderchat are strong on retrieval plus follow-up handling, but both lack citation transparency; Voiceflow is the more empathetic of the two, while Wonderchat is slightly stronger on retrieval accuracy. Botpress and Dante AI both retrieve policies well and handle crises reasonably, but weak or missing citation/deployment scores make them less compelling for a citation-sensitive use case. Chatbase is reliable for follow-up context and embedding, but the hard free-tier cap and weak edge-case handling limit it.





