When a website chatbot does not know, it should say so plainly, avoid filling the gap with a guess, and offer a clear next step. Ask for the visitor's contact details so a person can answer the question.
The message does not need to sound clever. It needs to protect the customer from a wrong answer and keep the question moving toward someone who can help.
What should the chatbot say first?
Start with the limit. Do not hide it behind a long apology or a vague error message.
I couldn't find that answer in the information on this website.
That sentence tells the visitor what happened without blaming them. It also avoids pretending that the question was answered. Chatterbox answers from material the business has already published. When it is not confident, it declines instead of inventing a reply.
For a warmer version, keep the meaning just as direct:
I don't want to guess and give you the wrong information. I couldn't find a clear answer to that here.
The useful part is not the exact wording. It is the decision to make uncertainty visible.
How do you offer a human next step?
Follow the limit with one action the visitor can take now. For many small businesses, that action is leaving contact details for a callback.
Please leave your name and phone number. A member of the team can answer this for you.
Chatterbox asks for contact details when the business's material does not contain the answer. It captures the inquiry for a person to handle; it does not turn a missing answer into a plausible one.
Do not promise a callback time unless the business can keep that promise. “Today,” “within an hour,” and “before we close” sound helpful, but they become commitments. A safe template states what will happen without inventing when it will happen.
Which fallback message fits the question?
A useful fallback can reflect the kind of answer that is missing. Keep the same structure: state the gap, do not guess, and ask for contact details.
For a price that is not published:
I couldn't find a price for that request, and I don't want to quote the wrong amount. Leave your contact details so the team can prepare the right answer.
For a service-area question:
I couldn't confirm whether this location is covered. Please leave your contact details so the team can check.
For a policy question:
I couldn't find a clear policy for that situation. Leave your contact details and the team can confirm it with you.
These versions are specific enough to feel relevant without stretching the website's material beyond what it actually says.
What should the message avoid promising?
Do not say “probably,” “usually,” or “in most cases” when the source material gives no answer. Those phrases turn a missing fact into a soft guess. The customer may still read it as the business's position.
Do not send the visitor into a loop by suggesting they rephrase the same question again and again. If the answer is absent, a clearer question cannot create it. Move to contact capture.
Do not imply that a person is already reading the conversation. The honest next step is that the visitor leaves details and a person answers later.
How do you test an “I don't know” response?
Before the widget goes live, ask it questions your website cannot answer: an unpublished discount, an address outside your stated service area, or an exception to a policy you have not written down.
The response passes when it admits the information is missing, avoids a number or promise, and asks for contact details. If it supplies a confident answer anyway, the failure is not cosmetic. A wrong price, area, or policy can become an expectation the business has to unwind.
An honest fallback is short because it has only two jobs: say what the website does not establish, then make room for a person to answer.