Chatbot Live but Not Behaving? Troubleshoot a Bot That’s Switched On but Silent, Wrong or Handing Everything Over (Free Symptom Checker)

Chatbot live on your website, bubble showing, and still something is off: visitors get no reply, the answers got basic overnight, every question gets the same reply, or people ask for a person and wait. This guide works from the symptom you can see back to the setting that causes it. Tick your symptoms in the free checker and it ranks the likely causes, with what to check and how to fix each.

👤 What the visitor seesVisitor
cod available for pune?
No reply for 4 minutes
hello??
Visitor left the chat

Illustrative: the widget works, the bot doesn’t answer. Where do you start?

⚡ In short

  • If the bubble doesn’t appear at all, it’s an install problem. Fix the script first.
  • If the bubble appears but the chat misbehaves, start from the symptom, not from the settings menu.
  • Most problems trace back to five things: AI allowance, saved replies, knowledge, visitor limit and alerts.
  • Test as a real visitor would: private window, phone on mobile data, the customer’s exact words.
  • Change one thing at a time and re-ask the same question after each change.
Chatbot live in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them
How it looks in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them.

Before you start

Is it the install or the bot?

There are two very different kinds of “it isn’t working”, and they have different fixes. Sort out which one you have before you touch a single setting.

The bubble doesn’t appear anywhere. Not on your phone, not on your laptop, not in a private window. That’s an install problem: the chat script is missing, blocked by a speed plugin or a security policy, or pasted in the wrong place. Bot settings can’t fix it. Our script troubleshooting guide walks through the ten usual causes in order.

The bubble appears, but the chat misbehaves. The widget opens, visitors can type, and then something goes wrong: no reply, the wrong reply, a reply that used to be better, a handover that goes nowhere. That’s what this guide covers.

There’s a third case worth naming: the chat appears for some people but not others. That usually isn’t a broken install. It’s a rule doing its job a little too well, such as a device, country or page setting, or a block you set while testing. It’s covered below.

A quick way to tell them apart: open your site in a private window on your phone, using mobile data rather than your office Wi-Fi. If the bubble shows there, your install is fine and the problem is in how the chat is set up.

How to test

Test like a visitor, not like the owner

Most false alarms about a chatbot live on your site come from testing the wrong way. As the owner you’re logged in, on the office network, on a browser that has visited the site a hundred times. Real visitors are none of those things.

Use this routine every time you test:

  1. Open a private window, or better, use your phone on mobile data. This avoids old cached pages and any rule tied to your office IP.
  2. Use the customer’s exact words. If the complaint was “cod available for pune?”, type that, not “Is cash on delivery available in Pune?”. Bots answer the words they see.
  3. Test the page the visitor was on. Rules about pages and Flows mean the product page can behave differently from the home page.
  4. Write down what happened, including the time. If the problem is about opening hours or alerts, the time matters.
  5. Change one thing, then repeat the same test. If you change three settings at once and it starts working, you won’t know which one fixed it, or which one you’ve broken.

Keep a short list of five or six test questions you re-use: one about price, one about delivery, one that needs a person, one in Hinglish, one you know the bot can’t answer. Our regression testing guide shows how to build a fuller set of golden questions to re-check after every change.

Free tool

Find the likely cause from what you see

Tick every symptom you have noticed, say when it started and who sees it. The checker ranks the causes and gives a check and a fix for each.

Tick what you are seeing, then answer the two questions below. The checker ranks the likely causes and tells you what to check first.

When did it start?

Who sees it?

Runs only in your browser; nothing is sent or saved.

Symptom 1

Your chatbot live, but visitors get no reply

This is the one that hurts most, because visitors give up fast. Work through these causes in order.

The AI allowance is used up and nothing else matches

In LiveChatBot the AI Agent answers from the knowledge you give it, within a small free monthly allowance per website. When that allowance is used up, the free keyword bot takes over and answers from your saved replies. If no saved reply matches the question, there’s nothing for the bot to send, and the question waits for your team. The fix is either an AI pack, or saved replies that cover your top questions so the keyword bot has something to say. Our saved replies guide shows how to write them.

The visitor limit is reached

On the free plan each website gets 100 visitors a month, counted once per visitor. Over the limit, tracking and new-visitor alerts carry on, but chat pauses for new over-limit visitors until you add a visitor pack or the month resets. Nothing is charged automatically. If replies stopped late in the month after a busy spell, check the count first. Packs are 100 for ₹99, 500 for ₹299 and 1,000 for ₹499 per website, and they never expire. See pricing.

You blocked yourself

During testing it’s easy to block a “spam” chat that was really you. If only you see the silence, check the blocked list for your own IP or test visitor.

The question needs a person, and none is around

Some questions are meant to go to your team. If nobody is online and there’s no away form, the visitor sees silence. That’s covered under Symptom 4.

Symptom 2

Answers got worse, or every question gets the same one

“It was great last week, now the answers are basic”

A sudden drop in quality, where replies become shorter, more generic or look like canned text, usually means the AI allowance for the month has run out and the keyword bot is now answering from saved replies. That’s by design: it keeps something answering instead of nothing. Check the AI usage for that website. If you’d rather keep AI replies all month, add an AI pack. If you’re happy with the keyword bot as a fallback, make the saved replies better, because for the rest of the month they’re the main voice of your business.

“Every question gets the same reply”

This is almost always a saved reply with keywords that are too broad. A reply triggered by “order” fires on “where is my order”, “can I order in bulk”, “order cancel” and “minimum order value”. A reply triggered by “price” fires on every product question.

Fix it in three moves:

  • Find the reply that keeps coming back and read its keywords.
  • Replace single common words with two-word phrases: “order status” instead of “order”, “delivery charges” instead of “charges”.
  • Split catch-all replies. One reply for delivery time and one for delivery charges beats one long reply about both.

Our guide to rule-based bots has a free tester that shows which of your rules fire for a pasted question, which is handy here.

Symptom 3

Wrong, invented or out-of-date answers

A confident wrong answer does more damage than no answer, so treat this one as urgent.

Out-of-date facts

If the bot quotes last month’s price or an old delivery time, the old fact is still in its knowledge or in a saved reply. It’s often in two places: you updated the knowledge text but not the saved reply, or the other way round. Search both for the old number and change every copy. Then re-ask the question in a private window.

Gaps the AI fills on its own

If the knowledge doesn’t mention something, an AI can produce an answer that sounds right but isn’t yours. The fix is to add the missing fact in short, plain sentences, one topic per paragraph, and to state clearly what you don’t offer: “We don’t ship outside India.” “We don’t offer EMI.” Negative facts stop a lot of guessing. Our training guide covers how to write knowledge an AI can use.

Two sources that disagree

If the answer changes from one chat to the next, look for two versions of the same fact: a “₹60 delivery” line in one paragraph and “free delivery over ₹999” in another, with no rule joining them. Merge them into one clear sentence.

Whatever the cause, run your whole test list again after the fix. Changing one answer can shift another.

Symptom 4

Visitors ask for a person and nobody comes

The bot did the right thing and handed over, but the handover went nowhere. Visitors in this spot often leave and don’t come back, so it’s worth fixing properly.

Nobody was alerted. Check that every teammate who should answer has the Android app signed in, with notifications allowed in the phone’s settings. Battery savers on some phones stop alerts from arriving, so test with the phone locked and on the desk. Our Android app guide covers the setup.

Opening hours don’t match reality. If the hours say you’re open and nobody is, visitors wait for a reply that never comes. If the hours say you’re closed while you’re at the counter, the away form appears instead of your team. Compare the days, times and time zone with your actual hours. See setting opening hours.

There’s no safety net. Even with alerts and hours right, sometimes nobody can reply in time. Two free features catch those visitors: the away form, which collects an email or phone number outside hours, and the chat rescuer in Flows, which steps in when a visitor has waited too long. Offline messages can also become tickets, so they’re tracked until someone replies.

If the bot and your team sometimes talk over each other once a person does join, our guide on who speaks when sets simple rules for that.

Quick reference

Symptom, first check, likely fix

What you seeCheck firstUsual fix
No reply at allAI usage, saved replies, visitor countAI pack or saved replies; visitor pack
Answers suddenly basicAI usage this monthAI pack, or better saved replies
Same answer to everythingKeywords on the repeating saved replyTwo-word phrases; split the reply
Wrong or old factsKnowledge and saved replies for the old factUpdate every copy; add negative facts
Handover goes nowhereApp alerts, opening hoursAlerts on; away form; chat rescuer
Away form at the wrong timeDays, times and time zoneCorrect the hours
Missing for some visitorsDevice, country, hide-on pages, blocksLoosen the rule; unblock
Proactive message misfiresEach Flow condition against a real visitRemove conditions one by one
Wrong languageAuto language, welcome translationsTurn on; add answers in that language

Symptom 5

It works for you but not for some visitors

When a customer says “your chat isn’t working” and it works fine for you, a rule is usually hiding it from them.

Where it shows. You can choose which devices and countries see the chat, and hide it on chosen pages. These are useful, but easy to forget. A chat hidden on phones disappears for most Indian visitors. A chat limited to India vanishes for a customer travelling abroad. A hide-on rule written for “/checkout” can also catch “/checkout-help”. Read each rule against the visitor who complained. Our guide to showing chat on specific pages explains the options.

Blocks. If someone on your team blocked an IP, everyone sharing that connection, such as an office or a college network, can be affected. Check the blocked list. Our blocking guide explains how blocks work.

Proactive messages that never show. Flows can use up to six conditions, chosen from page, source, country, device, browser language, number of visits, lead score and whether the visitor has given contact details. Each condition narrows who sees the message. Read every condition against one real visit, then remove conditions one at a time until the message fires where you expect. Add back only what you need.

The wrong language. If visitors get English when they wrote in Hindi, check that automatic language and welcome translations are on, and that your knowledge includes key answers in the languages your customers use.

Keep it working

A ten-minute weekly check for your chatbot live on the site

Most of the problems above are easier to prevent than to fix. Put ten minutes in the diary once a week.

  1. Open the site on your phone, on mobile data, and check the bubble appears on the home page and a product page.
  2. Ask your five test questions in the customer’s words. Note any answer that changed.
  3. Ask for a person. Check that someone’s phone alerts within a minute, or that the away form appears outside hours.
  4. Look at the month’s usage: visitors for each website and AI replies. If either is close to the limit and you’re mid-month, decide now whether to add a pack.
  5. Read three chats where the bot didn’t help, and add a saved reply or a knowledge line for each.

Write down anything you changed. When something breaks later, the list of recent changes is usually where the answer is.

For a fuller routine, our weekly review guide shows how to tag a week of chats by outcome, and our features dependency map shows which settings rely on each other, so switching one on doesn’t quietly break another.

When to ask for help

What to send so it’s fixed in one reply

If you’ve worked through the checker and the problem is still there, ask our team. You’ll get a faster answer with these details:

  • The website it’s happening on, and the page address.
  • What you expected and what happened, in one sentence each.
  • The exact words the visitor typed, with personal details removed.
  • When it happened, with the time, and whether it was inside opening hours.
  • The device and browser, and whether you tested in a private window on mobile data.
  • What you’ve already changed, so nobody suggests it again.

A screenshot of the chat helps more than a long description.

LiveChatBot’s free plan includes the AI Agent with a small free monthly allowance, the free keyword bot, saved replies, the team inbox, the Android app, Flows with the chat rescuer, opening hours with an away form, and tickets, for two websites with 100 visitors per website each month. Start at livechatbot.in.

Frequently asked questions

Why is my chatbot live on the site but not replying?

The usual causes are an AI allowance that’s used up with no saved reply matching the question, the monthly visitor limit being reached, or a block you set while testing. Tick your symptoms in the checker above to rank them.

Why did my bot’s answers suddenly get more basic?

Most often the AI allowance for that website ran out for the month, so the free keyword bot is answering from saved replies. Add an AI pack, or improve the saved replies until the allowance resets.

Why does the chat work for me but not for a customer?

A rule is usually hiding it from them: device, country or hide-on-page settings, a blocked IP, or Flow conditions. Test from a private window on mobile data, then read each rule against that visitor.

Am I charged automatically when I go over the visitor limit?

No. Tracking and alerts continue, and chat pauses for new over-limit visitors until you add a visitor pack or the month resets. There are no automatic charges.

Does the symptom checker send my answers anywhere?

No. It runs entirely in your browser and nothing is sent or saved.

Keep reading

Related guides

📘

Chatbot Introduction Message Clinic: 10 Common Mistakes, Before-and-After Rewrites and a Free Line-by-Line Checker

Read the guide →

🧭

Chatbot Interface Design by Answer Type: When to Use Buttons, a List, a Text Box or a Card for Each Question (Free Control Picker)

Read the guide →

🛠️

Chatbot Maker Red Flags: 10 Things That Look Great in a Demo but Cost You Later

Read the guide →

Fix it once, then keep it working

Saved replies, Flows, opening hours, the away form and the chat rescuer are all on the free plan. Start free on livechatbot.in.