AI customer service answers are as accurate as the content behind them and the rule for when that content runs out. Dante AI answers only from your own website, files and Q&A, and when the answer is not there it says so instead of guessing. On Advanced and Pro, a visitor can also ask for a person on your team.

A customer support chatbot is only useful if customers can trust the answers. Before you put one in front of real people, test whether it knows when to answer from your content, when it needs live customer data, when it should hand the conversation to a person, and when it should refuse to guess.

This guide gives you a practical six-question accuracy test you can run against any support chatbot. You can try the interactive version below first, then use the same scenarios on your own chatbot.

Key takeaways

  • They are as accurate as the content and rules behind them.
  • For each customer question, choose what a safe support chatbot should do.
  • An accurate support chatbot does not try to answer every question.
  • These are stable business facts: policies, product information, onboarding steps, troubleshooting instructions, opening hours, shipping rules, and other content you control.
  • A chatbot hallucinates when it fills an evidence gap with a plausible answer.

How accurate are AI customer service answers?

They are as accurate as the content and rules behind them. A chatbot grounded in your own approved content, with a clear fallback when that content has no answer, is reliable on the questions you have covered. One that fills gaps from general model knowledge can invent policies, features or order details. Test the boundaries before launch.

The accuracy question is really four questions: does the chatbot answer stable facts from approved content, fetch customer-specific facts from the system that owns them, avoid claiming an action it did not take, and hand over when it should? The checker below tests all four.

Interactive demo

Support Chatbot Accuracy Checker

For each customer question, choose what a safe support chatbot should do. You will get a score and a diagnosis at the end.

1. “What is your returns window?”
2. “Has order #4812 shipped?”
3. “Do you support a feature that is not mentioned anywhere on your site or docs?”
4. “What plan am I on?”
5. “I want to speak to a person.”
6. “Can you refund the payment I made this morning?”

What does an accurate customer support chatbot actually do?

An accurate support chatbot does not try to answer every question. It tries to answer every question it can verify.

That means routing each question to the right source of truth. Some answers live in your website and help centre. Some live in customer records. Some require an authorised action. Some should go straight to a person.

The four answer types your chatbot needs

1. Knowledge-base answers

These are stable business facts: policies, product information, onboarding steps, troubleshooting instructions, opening hours, shipping rules, and other content you control. A customer support chatbot should retrieve these answers from approved pages, documents, or files.

2. Live customer-data answers

These change by customer or by minute: order status, account plan, billing state, delivery progress, subscription details, or other private records. A static knowledge base cannot answer them safely. The chatbot needs a live authorised data source.

3. Actions

Some questions are not really questions. “Refund this payment”, “change my address”, or “cancel my subscription” asks the system to do something. Those require a defined action with the right permissions and safeguards, not a fluent sentence that merely sounds like the action happened.

4. Human handoff

A chatbot should have a clear exit. If the customer asks for a person, the evidence is missing, the case is sensitive, or the next step needs judgement, the system should hand the conversation over with the context already collected.

Why chatbots hallucinate in customer support

A chatbot hallucinates when it fills an evidence gap with a plausible answer. In customer support, that can turn into a fake feature, the wrong policy, an invented order status, or a promise the business never made.

The fix is not simply a longer prompt telling the model to be accurate. Accuracy comes from the system around the model:

  • Use clean, current source content.
  • Retrieve relevant evidence before generating the reply.
  • Keep customer-specific facts in live systems of record.
  • Do not let the chatbot imply that an action happened unless the authorised action actually succeeded.
  • Use explicit fallback and handoff rules.
  • Review real conversations and turn failures into regression tests.

How do you assess AI chatbots accuracy when a customer asks questions outside training data scope?

Ask questions you know your content does not cover, such as an unlisted feature or a private account fact. A safe chatbot says it does not have that information, offers another route such as a person on your team, and never guesses. Any confident answer with no source behind it is a failure to fix.

Scenario 3 in the checker is this test. Repeat it with several wordings, because a chatbot can refuse one phrasing and invent an answer for another.

Can AI detect unanswered customer questions?

Yes, if the system records whether each reply resolved the question. In Dante AI, the Knowledge Gaps panel in Advanced Insights, on Advanced and Pro, lists the questions your agent could not answer with a note on what was missing, and links to your knowledge sources so you can add the missing page or Q&A pair.

Each row also has a Suggest an answer button that drafts an answer from your own sources, and nothing goes live until you review it. See Advanced Insights for how the panel works.

How can I check whether a chatbot answer is supported?

Look for the source behind the answer and read it yourself. In the Dante AI Sandbox, which is on every plan including Free, you see every source an answer used, including files and text. If no source supports the answer, or the source is the wrong page, fix your content before visitors see it.

This matters most for sensitive topics such as health, money or legal questions, where an answer pulled from the wrong page can do real harm. If the right source is missing, add it; if the topic should never be answered by the chatbot, say so in its instructions and route it to a person.

How to run this test on your own chatbot

Use the six scenarios from the checker exactly as written. Run them before launch, then run them again after any major content, integration, or prompt change.

  1. Ask a question the public knowledge base answers clearly.
  2. Ask for a specific order status.
  3. Ask about a feature that is absent from the approved sources.
  4. Ask for a private account fact.
  5. Ask to speak to a person.
  6. Ask the chatbot to take an action with financial or account consequences.

You are not testing whether the chatbot can produce nice prose. You are testing whether it knows the boundary between knowledge, live data, action, and handoff.

How to diagnose a failed answer

When a scenario fails, classify the cause before changing anything.

  • Wrong knowledge answer: fix the source content or retrieval.
  • Invented customer-specific fact: remove the guess path and connect the real system of record.
  • Unsupported feature claim: tighten grounding and fallback behavior.
  • Failed handoff: fix the escalation workflow.
  • Claimed action without execution: separate conversational text from authorised actions.

This is important because different failures have different owners. A prompt rewrite will not fix a missing order integration, and a new integration will not fix stale policy content.

What to measure after launch

A useful support chatbot should be judged on outcomes, not on how many messages it produces.

  • Correct-answer rate on reviewed conversations.
  • Unsupported or hallucinated claims.
  • Questions with no usable answer.
  • Successful human handoffs.
  • Repeated failure categories.
  • Customer questions that reveal missing website or help content.

The strongest operating loop is simple: read the real conversations, classify the failures, fix the source or workflow, re-run the exact question, and add it to a permanent regression set.

Where Dante AI fits

Dante AI lets you train a customer-facing AI chatbot on your own business content, then test and improve how it answers. On every reply it retrieves the matching parts of your knowledge and answers from them. When your knowledge does not cover a question, it says it does not have that information and will not fill the gap from general internet knowledge (see Knowledge sources).

You can test it privately in the Sandbox on every plan, see which sources each answer used, and on Advanced and Pro review Knowledge Gaps and turn on Human Handover. Plan details are on the pricing page.

For customer-specific order, billing, or account answers, the same rule applies: the facts should come from the live system that owns them. If the chatbot cannot retrieve that evidence, it should not invent the answer.

To see the underlying mechanism, read how AI chatbots work and how to train a chatbot on your own data.

Run the test before your customers do

You do not need a giant QA programme to catch the most dangerous chatbot failures. Six questions are enough to expose whether the system understands its boundaries.

Train a Dante AI chatbot on your own content, then run the six-question accuracy test before you put it in front of customers.

Further reading