A chatbot is often the first AI project a business considers, and it is also one of the easiest to get wrong. Before building one, it is worth being honest about what problem it is actually solving.
When a chatbot genuinely helps
Chatbots work well for answering repetitive, predictable questions: opening hours, pricing tiers, delivery timelines, and basic troubleshooting. If your team answers the same handful of questions dozens of times a week, a chatbot can take that load off immediately.
When a chatbot makes things worse
If your customers usually have varied, specific, or emotionally sensitive questions, a chatbot that cannot handle nuance becomes a wall between the customer and the help they actually need. A frustrating chatbot is often worse than no chatbot at all.
Questions to ask before building one
What are the top ten questions we get asked?
If they are repetitive and factual, a chatbot is a good fit. If they vary widely, it is not.
What happens when it cannot answer?
A good chatbot hands off to a human cleanly. A bad one leaves the customer stuck in a loop.
Who is going to keep it updated?
A chatbot with outdated information is worse than a simple FAQ page, because it gives confident wrong answers instead of nothing.
Simple versus AI-powered
Not every chatbot needs to be built on a large language model. A simple decision-tree chatbot is often more reliable and cheaper for narrow, predictable use cases. AI-powered chatbots make sense when the range of questions is wider and a scripted flow could not realistically cover it.
Our recommendation
Start narrow. Build a chatbot for one clear use case, such as pre-sales questions or booking enquiries, and measure whether it actually reduces load on your team before expanding its scope. A chatbot that does one thing well beats one that tries to do everything and does none of it convincingly.
