Before You Buy A Chatbot: 4 Questions To Ask First

Free checklistFrom the video

Before you buy a chatbot: 4 questions to ask first.

Imagine hiring a contractor to build you a kitchen. He does a great job. Six months later you want to add a dishwasher, and he says: we didn't run the plumbing for that, so we have to tear it out and rebuild the kitchen from scratch.

That is what happens when you build a chatbot without thinking about what comes next. And it happens every single day.

There are four questions every business owner should ask before committing to any chatbot system. Almost nobody asks them. Not the business owner, and often not even the agency selling the solution. Here they are, with the reason behind each one, so you can tell a foundation from a trap before you hand over a single dollar.

The wallHow a working bot turns into a rebuild

It usually goes like this. A business owner decides to automate their WhatsApp. They find a platform, maybe from a YouTube tutorial, maybe because an agency recommended it. The demo looks clean, the bot responds fast, the price seems reasonable. They sign up, they build, and for a while everything works.

Then the business grows. Or changes. They need the bot on a second channel, or connected to their booking system, their customer records or their loyalty program. And that is when they find out the platform does not support it.

Not because it is technically impossible. Because some platforms are designed to keep you INSIDE them. They lock the door that lets outside software connect, and no developer and no budget can open it. The door is locked from the inside, and the platform owner holds the key.

So the owner who built on a closed platform is not upgrading. They are REBUILDING. Different platform, different logic, different cost, and all the time and money that went into version one is gone. Every time I have seen this happen, it was completely preventable.

The 4 questionsAsk them before you build, sign or pay

• 1Can this system grow with my business?

  Don't ask what the bot needs to do today. Ask what your business will need it to do in 12 months, and in two years. A good system is modular: a basic level today, the next level when you are ready, without tearing anything out.

  WhyIf the one thing it does is already its ceiling, you are not buying a kitchen. You are buying a microwave and calling it a kitchen. The businesses that skip this question are the ones that rebuild the same thing over and over, and then tell everyone chatbots don't work.

• 2What happens when I need to connect it to something else?

  Your bot does not live on its own. It needs to talk to your booking system, your customer records, your loyalty program, maybe your point of sale or your email tool. Ask the person selling it: which connections are possible, which are NOT, and is anything locked so that no outside software can ever connect?

  WhyAn honest answer to this question is worth more than any demo. If they cannot answer it clearly, or worse, they promise you everything is possible, that is information too.

• 3What happens when something breaks?

  Something will. Not because the system is badly built, but because your business changes: a new product, a campaign, new staff, new opening hours. Each one opens a gap between what the bot knows and what your customer needs. So ask who closes that gap.

  WhyWhoever builds your system has to stay involved. Not just for the setup, ongoing. Version one is never the finished product, and anyone who promises you a finished, set-and-forget chatbot is either inexperienced or not being honest with you.

• 4Does it think in specialists or generalists?

  Is it one bot trying to know everything, or a team? What works is a boss that manages the conversation and routes it, with specialists underneath: one for bookings, one for orders, one for coupons, one for customer history. On the front it still feels like one friendly, competent person.

  WhyYou would not hire one person to run your marketing, your customer service, your bookings and your technical questions at the same time. A bot built to know everything starts pulling the wrong answer at the wrong moment. Specialists beat generalists.

A real exampleThe campaign nobody told the bots about

Here is what question three looks like when it bites. A client of ours had a system that was running beautifully. The team was happy, customers were happy.

Then they sent a WhatsApp marketing campaign to their customer list, and the replies started flooding in. Except nobody had told the bots about the campaign. So when customers asked about the promotion, the bots answered confidently, helpfully, and completely incorrectly. They had never been briefed. They had no idea the campaign existed.

That was not a bot failure. It was a human one, and a simple one. Five minutes of conversation before the send and we would have briefed the system, and every one of those conversations would have gone right.

It happened to us, an experienced team. We caught it, fixed it and learned from it. A first-time builder won't see it coming, and won't even know what went wrong.

Two more habitsFrom the same video

• Brief your bot before every change. A campaign, a launch, new opening hours: tell whoever runs your bot first. Five minutes stops it answering confidently and wrongly.
• On a tight budget, a basic FAQ bot is better than nothing. Something that answers your most common questions, captures a contact and points people in the right direction has real value. Just go in knowing what it is: a starting point, not a system.

The honest money partStart where your budget is, and know what you bought

Don't let the perfect be the enemy of the good. But when you add up the real cost of doing it yourself, including your own time, the learning curve, the rebuilds and the ongoing maintenance, the numbers often look very different from what people expect.

If you are still deciding which kind of bot you need, the video Why Your Business Chatbot Is Stuck at Level 1 walks through the four levels. If you are deciding whether to build it yourself, watch Should You Build Your Own Chatbot?