How AI Web Agents Stay Honest When They Don't Know the Answer

TL;DR
An honest AI web agent does not turn missing evidence into a confident answer.
A strong AI chatbot strict mode grounded answers setup has four possible outcomes: answer, clarify, decline, or hand off.
Matram's Strict Mode confines answers to approved content and refuses when it cannot find support.
Retrieval can reduce a RAG hallucination, but stale or conflicting sources can still create a chatbot hallucination.
Matram can cite supported answers, refuse unsupported ones, and offer a person.
What does an honest AI web agent do when the answer is missing?
An honest web agent does not always answer and does not always refuse. It chooses the safest useful response based on the evidence available.
| Situation | Honest response | Example |
|---|---|---|
| The approved content clearly supports the answer | Answer and cite the source | A published plan includes a stated feature |
| The question is too vague to retrieve the right content | Ask one focused question | “Do you mean the Basic or Standard plan?” |
| The content does not contain the answer | Say the answer is unavailable | “I couldn't find that in the approved information.” |
| The question needs private data, judgement, or authority | Hand off to a person | An account issue, exception, or negotiated term |
The goal is to stop unsupported wording before a visitor mistakes it for a company commitment.
How does Matram handle a question it cannot support?
Matram publicly describes a grounded response path that starts with approved content and ends with either a cited answer or a clear boundary.
- Retrieve: Matram searches the website pages, documents, files, and connected knowledge sources approved for the agent.
- Answer with proof: When the material supports a response, Matram drafts the answer and links the source page used.
- Stop at the boundary: When the material does not support an answer, Strict Mode refuses. This is the core of an AI chatbot strict mode grounded answers setup.
- Offer a person: Matram can pass the conversation with its transcript attached, so the visitor keeps the context.
- Expose the gap: The dashboard shows conversations and unanswered questions the team can review.
This flow reduces the chance of a chatbot hallucination, but it does not prove every accepted answer is correct. The source still needs to be current, relevant, and consistent.
Strict Mode or Flexible Mode: which should Matram use?
Matram's features page documents both Strict Mode and Flexible Mode. Strict Mode confines responses to approved material. Flexible Mode allows broader reasoning.
Choose the mode according to the cost of being wrong.
| Question type | Better starting mode | Why |
|---|---|---|
| Pricing, plan limits, policies, eligibility, security claims | Strict Mode | The answer should match an approved source exactly |
| Product explanations already covered in documentation | Strict Mode | A citation should support the complete reply |
| General guidance where wider reasoning is acceptable | Flexible Mode, after testing | A broader answer may help, but it can move beyond company content |
| Account-specific, contractual, legal, medical, or sensitive requests | Human handoff | Grounding does not replace access, authority, or professional judgement |
For AI chatbot strict mode grounded answers, start strict when a wrong detail could change a purchase, policy decision, or customer action. Use broader reasoning only when the business has decided that the extra flexibility is worth the added uncertainty.
Matram does not publicly state the exact retrieval threshold, the default refusal message, or every rule used for ambiguous questions. Test those behaviours with your own content before launch.
Why can a grounded AI web agent still get an answer wrong?
Grounding reduces risk, not errors to zero. NIST defines confabulation as confidently presented false or erroneous content and notes that generated citations can also mislead.
Five failure modes matter:
| Failure | What goes wrong |
|---|---|
| No relevant source | Flexible answering may fill the gap with a chatbot hallucination instead of declining |
| Wrong passage | Related text is retrieved, but it does not answer the question |
| Stale source | The agent accurately repeats an old price, policy, or feature |
| Conflicting sources | Two approved pages give different answers and either may be retrieved |
| Unsupported wording | The reply adds a detail or conclusion that the passage does not support |
The last four can still create a RAG hallucination. An AI chatbot strict mode grounded answers configuration cannot decide which company policy is authoritative unless the source set makes that clear.
OWASP's RAG guidance says risk remains across ingestion, retrieval, generation, and output. Refusal rules, source control, citations, and human review must work together.
What should a useful “I don't know” answer say?
A useful refusal has three parts:
- Name the gap. Say the approved information does not contain a confirmed answer.
- Protect the boundary. Do not add a likely answer, estimate, or invented exception.
- Offer the next step. Ask a clarifying question, link a relevant source, capture the request, or offer a person.
For example:
I couldn't find a confirmed answer to that in the information available to me. I can help with the published plan features, or pass your question to a person with this conversation attached.
This is an example, not Matram's published default. Adapt it to your scope and response process.
A vague error may prevent a chatbot hallucination but still leave the visitor stranded. Design the decline as carefully as the successful answer.
How should you test Matram's no-answer behaviour?
Do not test only the questions you know Matram can answer. The edge of the knowledge base is where an AI chatbot strict mode grounded answers system proves whether it is trustworthy.
Use real customer wording, including typos, incomplete questions, and mixed requests.
| Test | Prompt design | Pass condition |
|---|---|---|
| Known answer | Ask a question covered by one current page | The answer matches the source and links it |
| Missing answer | Ask about a fact absent from every approved source | Strict Mode declines without inventing a detail |
| Ambiguous question | Remove the detail needed to choose the right answer | The agent asks a focused clarifying question or declines safely |
| Conflicting sources | Create two approved pages with different answers | The conflict is detected during review and resolved before launch |
| Stale source | Leave an old policy in the source set | The test exposes the outdated answer so the source can be removed |
| Unsupported follow-up | Start with a supported question, then ask for an unstated exception | The agent does not extend the first source beyond what it says |
| Sensitive request | Ask for private, contractual, or high-stakes advice | The agent hands off instead of attempting a final decision |
| Human request | Ask for a person midway through the conversation | The team receives the transcript and the visitor keeps the context |
Record each result as supported, unsupported, unclear, or handoff. Do not use “sounds good” as a QA grade.
That is the practical standard for AI chatbot strict mode grounded answers.
Run specific RAG hallucination tests by checking whether the cited passage supports every important sentence. Run chatbot hallucination tests by asking plausible questions that your business has never documented.
How can unanswered questions improve the website?
A declined question shows what a visitor expected to find but could not. Use a simple improvement loop:
- Review Matram conversations that ended in a decline or handoff.
- Group repeated questions by topic and customer intent.
- Decide whether the business should publish an answer.
- Add or correct one authoritative source.
- Re-sync the content and repeat the original test.
Prioritise gaps that recur, block a valuable next step, or create avoidable work. The decline list reveals weak documentation. Fixing the source can prevent the next RAG hallucination and also help visitors who never open the chat.
Related read: 15 Chatbot Best Practices That Actually Change Outcomes
When should Matram not be the final answer?
Matram should not make the final decision when the response needs private account data, commercial authority, professional judgement, emotional care, or a resolution to conflicting internal information. It can identify the need, preserve the context, and route the conversation without disguising a handoff-worthy request as a complete answer.
Frequently asked questions
What does AI chatbot strict mode grounded answers mean?
AI chatbot strict mode grounded answers means the chatbot uses approved sources and should decline unsupported requests. Test the behaviour rather than trusting the label.
Does Strict Mode eliminate chatbot hallucination?
No. It can reduce chatbot hallucination by blocking unsupported responses, but wrong retrieval, stale sources, and overextended wording can still create errors.
Can RAG eliminate hallucinations?
No. Retrieval gives the model relevant material, but a RAG hallucination can still occur when the wrong passage is retrieved or the answer goes beyond it. Citations and refusal rules make those failures easier to detect and contain.
What does Matram do when it cannot find a source?
Matram says that Strict Mode tells the visitor it does not have the answer and offers a person instead of guessing. Teams should test the exact wording and handoff route in their own setup.
Should every unsupported question go straight to a person?
Not always. Ask a clarifying question when one missing detail could locate the right approved answer. Hand off when the content is genuinely missing or the request requires private information, authority, or judgement.
Make “I don't know” part of the product
An honest AI web agent knows the edge of its evidence. It answers when the source supports the reply, asks when the question is unclear, declines when the answer is missing, and hands off when a person should decide.
That is the real value of AI chatbot strict mode grounded answers: not the promise that a chatbot will never be wrong, but a controlled response when certainty is not justified.
Explore the Matram AI web agent or start a 30-day trial. No card is required. Test it with known, missing, ambiguous, conflicting, and sensitive questions before putting it in front of customers.
See Matram in action
Watch it answer from real content, with the exact source page cited, on the live demo.
Book a demo