Every assistant reaches the limit of what it knows. A visitor asks about a service you have never described, a policy you have not written down or something unrelated to your business altogether. What the assistant does next says more about your business than its correct answers do. A confident guess can mislead a customer, create a dispute or promise something you cannot deliver. A cold 'I do not understand' leaves them stuck. A good fallback does three things: it is honest about not knowing, it points the visitor to a useful next step and it keeps the conversation moving toward something the customer needs, whether that is a booking, a callback or an answer from a person. This guide explains why fallbacks matter, describes the main kinds of 'I do not know' situations, gives wording examples, shows how to design next steps, explains why the assistant should never guess and how to test edge cases. It describes how Crescelo behaves: when nothing in your content answers a question, the assistant says so and offers a booking form or a person, and the gap is logged so you can fill it.
Why fallbacks matter
- A wrong answer given confidently costs more than an honest gap.
- Visitors forgive 'I do not know' if it comes with a way forward.
- The fallback is the moment a chatbot either loses or saves a customer.
- Each fallback is data: it shows what to add to your content.
The kinds of not knowing
| Situation | Example | Best response |
|---|---|---|
| Missing information | 'Do you do wedding hair trials?' (not in the documents) | Say you do not have that information; offer a callback or a person |
| Outside your services | 'Can you fix my laptop?' to a hairdresser | Say it is not something you offer, kindly, and stop |
| Needs a person's judgement | 'Can I get a discount for my group?' | Explain that a team member decides, and capture details |
| Sensitive or personal advice | 'Is this treatment safe with my condition?' | Explain that only a qualified person can advise; offer a call |
| Ambiguous | 'How much is it?' without saying what | Ask a clarifying question |
| Off-topic | 'Tell me a joke' | Politely steer back to what you can help with |
| Account-specific | 'Where is my booking?' | Say the assistant cannot see personal bookings; point to the confirmation link or a person |
The four parts of a good fallback
- Be honest: 'I do not have that information.'
- Do not guess: avoid phrases like 'probably' when the answer matters.
- Offer a next step: book, leave details, call, or ask a person.
- Stay helpful: offer related information that you do have.
| Weak | Good |
|---|---|
| I do not understand. | I do not have information about wedding trials. Would you like to leave your details so the team can reply, or shall I show you our booking times for a consultation? |
| I am sorry, I cannot help with that. | That is not something we offer, but I can help with haircuts, colour and treatments. What would you like to know? |
| Probably yes, but I am not sure. | I do not want to give you the wrong information. Let me pass your question to the team; can I take your email? |
Choose next steps that fit
| Next step | When to use it | In Crescelo |
|---|---|---|
| Book an appointment | The visitor wants to proceed and the question can be answered in person | Offer available times in the chat |
| Leave details for a callback | The answer needs a person | Lead form fields you choose; alerts by email, Slack, Sheets or webhook |
| Speak to a person now | Urgent or sensitive | Handover to your team with the conversation attached |
| Read a page | You have the information elsewhere | Link to it |
| Try a different question | Ambiguous request | Ask a clarifying question |
Match the step to the situation. Offering a booking for every unknown question feels pushy; offering a person for every trivial one wastes time.
Never guess in the areas that matter
- Prices, availability and policies must come from your documents, never from the model's general knowledge.
- Health, legal and financial questions should be handed to a qualified person.
- Promises about results, guarantees and timelines must come from your own content.
- Instruct the assistant explicitly: 'If the answer is not in the documents, say you do not know and offer a next step. Do not invent prices, hours, policies or guarantees.'
This is the purpose of a grounded assistant; see how to stop a chatbot from making things up. Even so, always test with questions you know the documents cannot answer.
Tone: honest without being robotic
- Keep the apology short: one 'sorry' is enough.
- Use natural language and avoid corporate wording.
- Show you have understood the question, so they do not feel ignored.
- Avoid repeating the same fallback sentence over and over; if the visitor keeps asking things you cannot answer, escalate.
- Keep the brand voice; see making the assistant sound like your business.
Loop protection
A visitor who receives 'I do not know' twice in a row is losing patience. Set a rule that after two failed answers, the assistant offers a person or takes details. Otherwise conversations turn into a maze of polite refusals. Crescelo's handover options let you choose when to offer a person; see handover design.
Use the gaps
Each fallback is a log entry. Review them weekly and fill the ones that recur; see your assistant's unanswered questions are a to-do list. A good assistant gets better because its gaps are systematically closed.
Test your fallbacks
| Test | What good looks like |
|---|---|
| A question the documents cannot answer | Honest, no invention, offers a next step |
| An off-topic question | Polite decline and redirect |
| A sensitive question | Hands over to a person, no advice |
| An ambiguous question | Asks a short clarifying question |
| Three unknowns in a row | Offers a person or takes details |
| A question in another language | Handles it gracefully or explains language support |
Keep these as a standing checklist and repeat after any change to instructions or documents.
Common mistakes
- Letting the assistant guess to avoid saying no.
- Offering no next step.
- Repeating the same canned apology.
- Sending every unknown question to a person.
- Never reading the fallback log.
- Failing to test out-of-scope requests.
Frequently asked questions
What should a chatbot say when it does not know?
Say honestly that it does not have that information and offer a useful next step, such as a booking, leaving details or speaking to a person.
Why should the assistant not guess?
A confident wrong answer about prices, policies or advice can mislead customers and cause disputes.
What does Crescelo do when it does not know?
It says so and offers a booking form or a person, and logs the question so you can fill the gap.
How do I avoid a frustrating loop?
After two unanswered questions, offer a person or take contact details.
Should the assistant answer off-topic questions?
It should politely decline and steer back to what it can help with.
How do I test fallbacks?
Ask questions you know the documents cannot answer, sensitive questions and off-topic ones, and check the response.
See the AI assistant feature, the human handover feature and try edge cases in the playground.
Further reading
- Google Search Central: creating helpful, people-first content: What Google looks for in useful pages.
RISPONDI A OGNI VISITATORE. PRENOTA CHI È PRONTO.
Installa Crescelo sul tuo sito in 15 minuti
Addestra il tuo assistente sui tuoi listini, documenti e condizioni di servizio. Attiva risposte fondate sulle tue fonti 24 ore su 24 e prenotazioni in chat senza sovrapposizioni.