Canonical public page: https://wavehello.ai/blog/website-chatbot-does-not-know Evidence record: https://wavehello.ai/read/blog/website-chatbot-does-not-know.evidence.json Site reading directory: https://wavehello.ai/read/index.txt This is a build-generated reading copy of the public main content. Navigation chrome, scripts, controls, form fields, and image pixels are omitted; authored image descriptions and diagram text are retained. Use the public page for interactive features. Links are source relationships, not endorsements or independent verification. [Home]() [Blog]() What Your Website Chatbot Should Do When It Does Not Know Custom AI systems # What Your Website Chatbot Should Do When It Does Not Know Design a useful response to uncertainty: clarify the question, avoid invented business claims, and help the visitor reach a person without starting over. By [WaveHello]() Published September 12, 2026 4 min read In this article 1. [Separate missing information from an unclear question]() 2. [Make uncertainty sound helpful, not evasive]() 3. [Let a person continue from the conversation]() 4. [Test the difficult questions deliberately]() 5. [Use unanswered questions to improve the service]() Related services [AI website assistants]() [Managed AI website sales agents]() In this article 5 sections 1. [Separate missing information from an unclear question]() 2. [Make uncertainty sound helpful, not evasive]() 3. [Let a person continue from the conversation]() 4. [Test the difficult questions deliberately]() 5. [Use unanswered questions to improve the service]() Related services [AI website assistants]() [Managed AI website sales agents]() Prefer the short answer? [What should a website chatbot do when it does not know the answer?]() A website chatbot should acknowledge when it cannot give a reliable answer, ask for clarification when that could help, and offer an appropriate way forward. It should not invent prices, policies, availability, or commitments just to keep the conversation moving. Knowing when to stop is part of providing useful help. ## Separate missing information from an unclear question A visitor may use a phrase the business does not recognize, ask about a situation missing from the approved information, or request a decision only a person can make. These are different cases. A clarifying question may solve the first; it cannot create a missing policy or authorize an exception. Define the important boundaries before launch. Identify which answers can come from business information, which require a connected tool, and which belong with a team member. This gives the assistant a useful role without expecting a conversational model to know everything about the company or the customer's circumstances. ## Make uncertainty sound helpful, not evasive A good fallback is brief and relevant. It explains the limit, preserves what is already understood, and offers a next step the visitor can choose. Avoid a long technical disclaimer or a confident guess followed by a warning. The customer needs to know whether the information can be relied on. Use language that matches the situation. If the assistant lacks current availability, it can say that it cannot confirm that time and offer the booking path. If the question needs judgment, it can offer to send the request to the team. Neither response needs to describe the model or its internal configuration. **Illustrative example** A visitor asks whether an unusual project can be completed by Friday. The assistant can explain that the team needs to confirm the deadline and offer to share the project details. It should not turn a general statement about fast service into a delivery promise. ## Let a person continue from the conversation If the visitor wants help from the team, carry forward the relevant question and context through an agreed contact path. Ask for the information needed to respond, rather than requiring the visitor to repeat the whole story. Do not imply that a person is already replying unless that service is actually available. Keep the confirmation truthful. Preparing a request, submitting it, and receiving a response are separate events. If the handoff fails, show a usable alternative. A pleasant conversation that silently loses the request is not a successful support experience. ## Test the difficult questions deliberately Before launch, test questions with incomplete details, outdated information, conflicting wording, and requests outside the business's scope. Include attempts to obtain private information or make the assistant ignore its rules. OpenAI's evaluation guidance supports using realistic tasks and difficult cases instead of relying on a few successful demonstrations. Write down what an acceptable response looks like for each case. You are testing behavior: whether the assistant clarifies, answers from the right information, stops, or offers a handoff. No test set proves an AI system will never make a mistake, so the ongoing review and customer fallback still matter. - Unknown or unpublished price. - Unconfirmed availability or deadline. - A request for a policy exception. - Contradictory business information. - A failed connection during a handoff. ## Use unanswered questions to improve the service Review unanswered questions for recurring information gaps. Some should lead to a better website answer or an updated business explanation. Others should remain a human decision. Do not treat every fallback as a failure to eliminate; sometimes it shows that the assistant respected an important boundary. Keep changes to approved information and assistant behavior traceable, and retest affected cases. The useful goal is not a chatbot that answers absolutely everything. It is a customer experience that gives dependable help where possible and makes the limits clear when a person or a different tool is needed. Sources ## Where the facts came from These links support the facts and definitions in this article. Recommendations are WaveHello's view unless we say otherwise. 1. [Evaluation best practices]() OpenAITesting AI behavior against realistic tasks and difficult cases. 2. [User notifications in forms]() W3C Web Accessibility InitiativeMaking errors and successful submissions understandable. What to do next ## Helpful answers. Clear limits. A sensible next step. Tell us what customers ask and where your team should take over. [Plan your assistant]() Continue reading ## More from the Blog. [View all Blog posts]() [Custom AI systems September 13, 2026 8 min read ### AI Customer Service Agents for Small Businesses Compare HubSpot, Intercom Fin, and Tidio Lyro by customer task, handoff, plan requirements, and usage costs. Includes a practical evaluation checklist. Read the guide]() [Custom AI systems September 12, 2026 4 min read ### From Answering Questions to Helping Customers Take Action Explore how a website assistant can support the next step through tailored questions, forms, booking, and connected tools—with clear customer control. Read the guide]() Related FAQs - [AI assistants]()