A contrary view

When not to use an AI chatbot

We ship an AI chatbot and we think it's good. We also think a lot of teams switch one on in places it actively makes support worse - and then conclude the technology is useless, when really it was pointed at the wrong problem. Here's where we'd tell you not to bother.

The customer is already angry

Somebody whose order is late, whose payment failed twice, or whose service is down does not want to be triaged. They want a person to acknowledge the problem. A bot in that moment reads as a company avoiding them - and it is remembered long after the issue is fixed. If your widget sits on a page people reach when something has gone wrong, route it straight to a human.

The answer has consequences

Medical, legal, financial and safety questions are the wrong place for a model that can be confidently wrong. The cost of a plausible incorrect answer is not a bad review - it's harm, and sometimes liability. Keep AI away from advice a regulator would care about, no matter how good the documentation is.

The question is genuinely new

Grounded AI answers well from what you've written down. During an outage, a recall, or the week after a confusing release, the questions arriving are precisely the ones nobody has documented yet. That's when a bot is least useful and most likely to improvise - and exactly when your customers are least forgiving.

Your volume doesn't justify it

A chatbot is not a set-and-forget appliance. It needs documentation written, answers reviewed, handoff tuned. At a handful of chats a day a person can simply answer all of them, better, with less effort than maintaining the bot. Canned responses and a proactive greeting will get you most of the speed for none of the upkeep.

You'd be using it to hide

If the honest goal is to make reaching a human hard, a chatbot will achieve that - and customers recognise it immediately. Deflection that comes from genuinely answering the question is good for everyone; deflection that comes from friction just moves the anger to a public review.

Where it genuinely earns its place

The mirror image of the list above.

Situation Why AI fits
The same question, endlessly Documented, unambiguous, and answering it is nobody's idea of a career.
2am, and nobody is on An imperfect answer now beats a perfect one in nine hours - and if it can't help, it takes a message.
Routing and qualifying Gathering the order number before a human arrives is genuinely useful to both sides.
Helping the agent, not replacing them Drafts, summaries and tags speed your team up while every customer still hears from a person.
If you do switch it on

Make giving up easy

The single biggest difference between a chatbot people tolerate and one they resent is how quickly it steps aside. Set generous handoff triggers, let "talk to a human" work at any point, and pass the full transcript across so nobody repeats themselves. A bot that admits defeat early is judged far more kindly than one that keeps guessing.

Read next

How handoff works - and how to set the triggers.

The quieter option

Reply suggestions give your team the speed without putting a bot in front of customers.

Isn't it strange for a chat vendor to argue against chatbots?
We sell software, not a promise that AI fixes support. A chatbot deployed in the wrong place makes customers angrier and your team's job harder, and you would rightly blame the product. We would rather you switch it on where it helps and leave it off where it doesn't.
When is a chatbot clearly the wrong choice?
When the customer is already upset, when the answer carries legal, medical or financial consequences, when the question is genuinely novel, and when your volume is low enough that a person can simply answer everything. In those cases a bot adds a delay before the real answer.
What if we only get a few chats a day?
Then a chatbot is probably not worth operating. At low volume the maintenance - writing documentation, reviewing answers, tuning handoff - costs more than the time it saves. Use canned responses and proactive greetings instead; they need no upkeep.
Can we use AI without letting it talk to customers?
Yes, and for many teams that is the better trade. Reply suggestions draft answers for your agents to edit and send, so customers always hear from a person while your team still gets the speed. Summaries and tagging are similarly invisible to customers.
If we do run a chatbot, what matters most?
That it hands over quickly and gracefully. A bot that admits it cannot help and fetches a human is far better received than one that keeps confidently guessing. Set generous handoff triggers and make reaching a person easy at any point.
Owned customer support software

Deploy live chat on your own terms, not on someone else's pricing model.

ZChat gives you the installable server, web dashboard, website widget, and desktop agent tools in one self-hosted product you buy once and keep. Run it on infrastructure you trust and connect AI only if and how you want it.

Deployment

Install on Windows or Linux, behind IIS or Nginx, in a VM, or in Docker if that fits your stack.

Commercial model

One-time purchase, perpetual license, and no monthly per-agent bill attached to growth.

AI Flexibility

Use Ollama locally or connect OpenAI and Anthropic with your own provider accounts.