Where the chat bubble came from
Somewhere in the last couple of years a chatbot turned up in the bottom corner of most business websites. It came in as a free trial, or a plugin someone installed on a quiet Friday, or a line in an agency proposal promising 24/7 AI customer support. It worked in a two-minute demo. Nobody has looked at it since.
We see a lot of these, because clients ask us to look at websites that get traffic but not enquiries. The chatbot is rarely the only problem, but it's often one of the bigger ones. It sits at the exact moment a visitor has a question and is deciding whether to trust you, and it answers badly.
How a bad bot loses a customer
The failures are so consistent that we can usually describe them before we've seen the site.
The bot makes things up. A general-purpose language model with no connection to your content will answer confidently about your prices, your opening hours, your delivery areas and your refund policy. Some of those answers will be wrong. And a visitor who's been quoted a price by your own website, then told something different by a human, doesn't blame the bot. They blame you.
It sits on top of the phone number. On mobile, the widget often covers the one thing the person came for: the call button, the address, the contact details in the footer.
It dodges the question that matters. Ask a typical bot the thing your customers most want to know, the question that decides whether they enquire, and you get "I'm not sure about that, but I can help with other questions." So the visitor leaves.
It loops. Menu buttons that lead back to the same menu. "Would you like to speak to someone?" followed by a form nobody replies to. People don't persist through that. They close the tab.
And it talks like nobody in your business talks. Over-cheerful, over-long, exclamation marks everywhere. If you're a plumber or a law firm, a bot that sounds like a theme park mascot undoes the trust the rest of the site built.
None of this shows up in the vendor dashboard, because the dashboard counts conversations started. That's a count of people who had a question and were routed to software instead of to you.
The ten-minute audit
You don't need us to tell you whether your bot is bad. You can find out before lunch. Open your site in a private browser window on your phone rather than your desktop, because that's how most visitors arrive, and work through these.
- Ask it your five most common customer questions. You know what they are. They're the ones your front desk or inbox answers every day. Ask them the way a customer would, with typos and no context. Does the bot answer correctly, in a sentence or two, with a link to the right page? Or does it guess, hedge or deflect?
- Ask it something it should refuse. Ask for a firm price on a job that needs a quote. Ask whether you do something you don't do. Ask about a competitor. A good bot says "that needs a proper conversation, here's how to start one." A bad bot invents an answer, and now your business appears to have made a promise.
- Try to reach a human. Type "I want to talk to a person" and count the steps. See whether you're offered a phone number, an email, a form with a response time, or just another article. More than one step and the bot is a gatekeeper.
- Check what it covers up. Scroll to the footer on your phone. Open a service page. Is the bubble sitting on a button, a form field, a price or a phone number? Close it and see whether it reopens on the next page.
- Read the transcripts. Most platforms keep them. Read the last twenty conversations in full, not the summary. This is usually the point where the mood in the room changes, because you're watching real prospective customers ask reasonable questions and get nonsense back.
If it passed all five, it's in a small minority and you can stop reading. If it failed two or more, it's costing you enquiries and you have a decision to make.
What a good one looks like
We build conversational tools for clients, so we're not against the idea. We're against the version that gets installed by default.
A bot that earns its place is grounded in your content. Its answers come from your pages, price lists, policies and documents, and when those don't contain an answer it says so instead of improvising. We wrote about when that's the right tool in our piece on a custom knowledge base versus a chatbot. If the answers aren't anchored to your content, you haven't built a support tool. You've built a rumour generator.
It's honest about its limits. "I can't give you a fixed price for that, but here's what usually affects it and here's how to get a quote in two minutes" is a good answer. It's more useful than a wrong number and it moves the visitor toward the form. Good bots decline often, and gracefully.
A person is one tap away, always. The phone number, an email and a short form should be visible inside the chat window from the first message, not behind a menu. During business hours someone real should be reachable from the widget. Outside them, the bot should say when you'll reply and mean it.
It stays out of the way. It doesn't open itself. It doesn't cover the footer or the call button. It doesn't follow the visitor from page to page bouncing for attention.
And it's measured by outcomes: questions resolved, enquiries submitted, calls placed, quotes requested from inside the conversation. If the bot can't be connected to your lead form and your analytics, you can't know whether it's working.
Sometimes the right answer isn't a chatbot at all. If most of your visitors are trying to find a specific product, service or page, a well-built AI site search does more with far less risk, because search returns your real pages rather than paraphrasing them.
When to switch it off
There's no shame in removing a bot. Keeping a bad one costs you.
Switch it off if it failed the audit and you're not going to invest in fixing it. A half-configured bot is worse than none, because none doesn't invent your prices. Switch it off if your customers overwhelmingly want to call or email, which is true for many trades, professional services and local businesses. Switch it off if nobody in your business owns it, reads the transcripts, or updates it when your prices and services change.
In its place, put the boring things that work. A clear FAQ on the pages where the questions come up. A phone number and email in the header on mobile. A short contact form with an honest response time next to it. We've seen these out-perform an untuned bot on the same site, and they never tell a customer something that isn't true.
Then, if the questions your team keeps answering are repetitive and answerable from your own content, come back to the idea with a proper brief. That's when a grounded assistant, built as part of a considered AI and automation integration rather than bolted on as a plugin, starts to pay for itself. The ones that work were built backwards from the business: someone listed the real questions, gathered the real answers, decided what the bot must never say, and wired it to the enquiry form so it could be measured.
If you suspect the chat bubble on your site is turning people away, we can run the audit with you, tell you plainly whether to fix it or remove it, and build the version that earns its place if there is one. Get in touch.
