WhatsApp Chatbot for Business: Guide

A chatbot on WhatsApp does not have free rein over the channel. What it may send depends entirely on whether a customer service window is currently open with that person.

Three practical consequences follow.

Your bot is at its best when the customer is talking. Service messages are free and free-form, so the entire conversational part of a bot — answering questions, collecting details, confirming a booking — costs nothing while the window is open. Design flows to complete inside it.

Once the window closes, the bot is nearly mute. It cannot improvise. It can send an approved template, and if that template is categorised as marketing it is charged every single time, whether or not the customer engages.

You do not decide the category. Meta's documentation is clear that businesses accept the charges associated with the category applied to the template at the time of use. A message you consider a utility nudge, written with a promotional line in it, can be categorised as marketing and billed as marketing.

One cheap starting route worth knowing: conversations opened from Click-to-WhatsApp ads are a free entry point, giving 72 hours in which all messages are free. A bot handling those conversations is operating at no message cost for that period.

Every bot eventually meets a question it cannot answer. A handoff that works has four properties:

1. It triggers early. The signals are visible — a repeated question, an explicit request for a person, frustration in the wording. Trigger on the first one, not the third.
2. It carries the transcript. The agent picking up should see what has already been said, so the customer is not asked to repeat themselves.
3. It names an owner. "A team member will get back to you" is not a handoff; it is a queue with no accountability.
4. It respects the clock. Free-form conversation only works while the window is open. If the handoff sits unclaimed until the window closes, your agent's first message is now a charged template — and a colder one.

That fourth point is why handoff is an operational design question, not a chatbot-configuration question. The bot can flag a conversation instantly. Whether anyone picks it up in time depends on whether the flag lands somewhere a human is actually working.

A common pattern: a team installs a chatbot, deflection looks good in the first month, and the workload does not actually fall. The bot handled the easy questions and pushed everything else into a shared inbox, where it accumulated. Deflection is not resolution. If a bot cannot escalate into a system that holds the outcome, it has moved the work rather than removed it.

Two failure modes in particular:

The unresolved conversation with nowhere to go. The bot could not answer, the handoff went to a general inbox, nobody claimed it, the window closed. The customer is gone and there is no record that anything was owed to them.

The qualified lead with no next step. The bot captured a name, a requirement, a budget — and then the customer went quiet. Inside WhatsApp there is nothing more it can do: no free-form route back, and a marketing template costs money each time it pokes someone who has already stopped responding.

Both failures share a cause: the bot is the end of the process rather than the start of one.

This is where our approach differs from a WhatsApp-only chatbot tool. Those tools automate inside WhatsApp. HelloGrowthCRM continues the conversation off it.

When our bot escalates, the conversation becomes a record on a sales pipeline. It has a stage, an owner and a next action with a date. The WhatsApp transcript stays attached, so whoever picks it up can read what was already said. And when the customer goes quiet — which most will — the sequence carries on through channels that have no messaging window: SMS, email, an outbound dialer call, and a task on a named person's list.

The bot is then doing what a bot is genuinely good at: handling the live conversation cheaply while the window is open, and putting everything it cannot finish somewhere a human will see it. One thing stated plainly so nothing surprises you later — WhatsApp broadcast Campaigns sit on tier 2 and above, not on every plan.

If you are evaluating WhatsApp chatbots, put one question to each vendor: what happens to a conversation the bot cannot finish? A tool that only automates inside WhatsApp will show you a handoff into an inbox. That is a queue, not an outcome.

We would rather show you the escalation path — a pipeline stage, an owner, a dated task, and follow-up that continues on SMS, email and dialer when WhatsApp goes quiet. Book a walkthrough and bring the questions your bot keeps failing.