The most common issues and how to fix them in minutes.
Is your chatbot not behaving the way you expected? Don't worry: most issues have a specific cause and take just a couple of minutes to fix from your dashboard. Here are the most common situations, what causes them, and how to solve them step by step.
Most common problems
The chatbot doesn't respond or always gives the fallback message
Cause: the knowledge base is empty, or the questions it's getting aren't covered by your content.
Solutions:
Go to Knowledge and confirm you have at least one source in "Ready" status. If it shows "Processing" or an error, that content isn't available for answering yet.
Re-sync the URL manually using the button on the source itself to force a fresh read.
Test with questions that are in your content. If those work, it's a coverage gap, not a configuration problem.
Check Conversations to see what visitors are actually asking, and compare it against what you've documented. It usually reveals easy gaps to fill.
Cause: the chatbot automatically detects the visitor's language and replies in it.
Solutions:
To force a fixed language, go to Behavior & Tone → Instructions and add something like: "Always reply in English, regardless of the visitor's language."
If your knowledge base is in a single language but you serve customers in others, add documents in those languages so it has material to draw from.
Cause: the chatbot ID is permanent and can't be changed, since it links the widget to your configuration.
Solutions: if you need a new identifier, contact us and we'll sort it out with you.
Still stuck?
If the problem persists, open the ChatME Assistant inside your dashboard and paste the browser console error there (or describe what you're seeing): it'll give you an instant diagnosis. And if you'd rather we look at it together, book a demo and we'll review it with you live.
Was this article helpful?
NEED MORE HELP?
Ask the ChatME Assistant
It's in your dashboard and knows every step. Or book a demo and we'll set it up with you.