When does a business actually need an AI chatbot?

Ask most software vendors and the answer is always yes. Ask us, and the honest answer is: sometimes, and only once a few other things are in place. A chatbot bolted onto a business that is not ready for one tends to frustrate customers rather than help them, and a poor chatbot experience is often worse than no chatbot at all.

Good use-cases

Chatbots earn their place when they are handling questions that are frequent, repetitive, and answerable from information you already have: opening hours, pricing tiers, order status, appointment availability, product specifications, or "how do I" questions your team currently answers the same way, several times a day. In these situations, a chatbot gives customers an instant answer at eleven at night that would otherwise wait until Monday morning, and it frees your team from repeating themselves.

They also work well as a first-line filter: gathering the details a human will need anyway, name, contact details, what the enquiry is about, before handing over to a person, so the human conversation starts from context instead of from scratch.

Poor use-cases

A chatbot is the wrong tool when the questions are genuinely varied, emotionally sensitive, or high-stakes: a complaint, a medical or legal question, a negotiation, anything where getting it slightly wrong damages trust. It is also the wrong tool when your own knowledge is not organised well enough to ground it. A chatbot that guesses, or worse, invents an answer with total confidence, causes more damage than the time it saves.

If your business does not yet have clear, written answers to your most common customer questions, that is the actual first project, not the chatbot.

Ground it in your own knowledge

The chatbots worth having are grounded in your specific information: your service pages, your pricing logic, your policies, your FAQ, your product catalogue, not a generic model improvising an answer from general knowledge about your industry. This is usually the difference between a chatbot customers trust and one they quickly learn to work around.

Grounding also means keeping that knowledge current. A chatbot answering from a price list that changed three months ago is a liability, not a convenience.

Always leave a door to a human

Every chatbot conversation needs a visible, easy way to reach a person, not hidden behind three menus, and offered proactively once the bot detects it is struggling or the visitor is getting frustrated. The goal is to handle the repetitive questions so your team's time goes to the conversations that actually need a person, not to keep people away from your team altogether.

Measuring whether it is working

A chatbot is working if it is reducing repetitive load on your team, resolving a meaningful share of conversations without escalation, and customers are not visibly frustrated by it. Track deflection rate, escalation rate, and, most tellingly, whether the same questions keep escalating despite being "covered." That last signal usually means the grounding needs work, not the bot itself.

WhatsApp or website?

For South African businesses, this is often the more useful question than "chatbot or not." WhatsApp is where a large share of customers already are, particularly for anything transactional, and it carries none of the friction of finding and loading a website first. A website-based assistant suits businesses with a wider range of information to surface, where a chat window is one part of a bigger page rather than the whole interaction.

Many businesses are best served by both, doing different jobs. Few need to start with both at once: start with whichever channel your customers already prefer, prove it works, then expand.

The real question

Not "should we get a chatbot," but "do we have repetitive, well-defined questions, answerable from information we actually have, in high enough volume to justify it, with a clear escalation path when it cannot help." If that is yes, a chatbot is a genuinely good investment. If it is no, the more useful project is usually organising the knowledge itself, which pays off with or without a chatbot on top of it.