Almost every WhatsApp automation project starts in the wrong place. Somebody builds a chatbot, spends six weeks on conversation trees, launches it, and discovers customers ask three questions the tree does not have and then ask for a human.
Meanwhile the thing that was actually costing money, nobody following up on Tuesday's leads, is still unfixed.
What should you automate on WhatsApp?
The flows worth building are the ones where timing is the whole value, not the ones where you are trying to replace a conversation.
1. The first reply, in seconds. A lead fills in your ad form. Somebody should be in their WhatsApp before they have closed the tab. Not because the message is clever, but because you are first. This one flow outperforms every chatbot ever built, and it is the simplest to make.
2. The follow-up when they go quiet. Most leads do not say no. They say nothing. A rule that brings a silent lead back onto somebody's list tomorrow morning recovers more revenue than any amount of copywriting on the first message.
3. Reminders before an appointment or visit. A visit booked and forgotten is worse than a visit never booked, because you paid for the lead and blocked the time. Reminders are also the one place utility templates genuinely apply, so they are cheap.
4. The reply to their reply. When someone answers, a 24-hour window opens where everything you send is free and needs no template. Automating the immediate acknowledgement inside that window costs nothing and buys you the time to get a human on it.
5. Re-engagement of old leads, carefully. A list from four months ago is not dead, it is cold. Re-engaging it deliberately, in small batches, with something that gives them a reason to reply, is legitimate. Blasting all of it in one afternoon is how the next section happens.
What should you never automate?
Three things, and each one costs you the account rather than the campaign.
Volume to people who never asked. Automation makes it trivial to send to ten thousand people you have no relationship with. Meta's per-recipient marketing cap (131049) will start blocking, your quality rating will fall, and the messaging tier you climbed to gets taken away. The error code reference covers which failures are survivable and which are not.
Retries of permanent failures. A number that returns 131026 is not on WhatsApp and never will be. An automation that retries it nightly is a machine for damaging your own sender reputation.
Answers to questions the customer did not ask. A bot that responds to "is it still available?" with a five-option menu is worse than a slow human. If your flow cannot handle the answer, hand over rather than deflect.
Why do most WhatsApp chatbots fail?
Because they solve a problem the business did not have.
The bottleneck in almost every Indian SMB pipeline is not that customers cannot get answers. It is that nobody replied for six hours, and by then the customer had spoken to somebody else. A chatbot addresses the wrong half of that: it answers instantly and then cannot close, so you still need the human, just later and with a worse-tempered customer.
Automating the follow-up instead solves the actual failure, needs no conversation design, and works on the first day.
If you want a bot eventually, build it after the timing problems are fixed. It will also be better, because by then you will have a log of what people genuinely ask.
What does WhatsApp actually let you automate?
Two rules shape every flow you will ever build, and knowing them saves redesigning later:
- Outside a conversation, you can only send approved templates. Free-form text is not allowed until the customer messages you first. So any automated first touch is a template, submitted in advance and reviewed by Meta.
- Inside the 24-hour window, anything goes. Once they reply, that window opens and free-form messages send with no template and no template pricing.
Every efficient WhatsApp automation is therefore shaped the same way: one template designed to earn a reply, then everything else inside the free window. That is not a cost trick, it is the whole architecture.
How do you know it is working?
Not by messages sent. Three numbers, in order:
| Metric | Why it matters |
|---|---|
| Time to first contact | The only one that beats competitors. Measure in seconds. |
| Reply rate on the first message | Decides your cost per conversation, and nothing else moves it as much. |
| Delivered, not sent | A 200 from the API is not delivery. Why "sent" means nothing. |
If your dashboard reports messages sent and campaigns completed, it is measuring your effort rather than your outcome.
Where to start on Monday
- Automate the first reply. One template, one question, sent within seconds of the lead arriving. Nothing else.
- Add the silent-lead follow-up. Anyone who has not replied comes back tomorrow.
- Add reminders for anything you book.
- Then look at the reply rate, and rewrite the first message until it moves.
- Only then consider a bot, and only for the questions your logs show people actually ask.
That order is deliberate. Each step pays for the next, and none of them require you to design a conversation tree.
At Kredoo this is what the product is: leads captured from Meta and Google Ads, one message engineered to earn a reply, then automated follow-up when it goes quiet, all inside your own WhatsApp account. See how it works.
Questions people ask
What should I automate on WhatsApp for my business?
Five flows, all about timing rather than conversation: the first reply within seconds of a lead arriving, a follow-up when someone goes quiet, reminders before appointments or visits, an immediate acknowledgement when they reply so you stay inside the free 24-hour window, and careful re-engagement of older leads in small batches.
Is WhatsApp automation allowed by Meta?
Yes, within two rules. Outside an open conversation you may only send templates that Meta has approved in advance. Inside the 24-hour window that opens when a customer messages you, free-form messages are allowed with no template. Automation that sends unapproved content, or high volumes to people who never opted in, triggers per-recipient blocks and quality-rating damage.
Why do WhatsApp chatbots usually fail?
Because they solve a problem most businesses do not have. The bottleneck is rarely that customers cannot get answers, it is that nobody replied for hours. A chatbot answers instantly and then still needs a human to close, so the delay returns. Automating the follow-up fixes the actual failure and needs no conversation design.
How many messages can I automate on WhatsApp?
It is limited by your messaging tier, not by your software. A new number can start conversations with 250 unique customers per rolling 24 hours, rising through 2,000, 10,000, 100,000 and unlimited as your volume and quality rating allow. Sending more than your tier permits produces errors rather than messages.
What is the difference between WhatsApp automation and bulk messaging?
Automation reacts to something a specific person did, such as submitting a form, replying, or booking a visit. Bulk messaging pushes the same content to a list regardless of behaviour. The first improves your quality rating because recipients engage; the second damages it, because most recipients did not ask.
Do I need the WhatsApp Business API to automate messages?
Yes for anything triggered by your own systems. The free WhatsApp Business app offers only [basic greeting and away messages](/whatsapp-business-greeting-message-examples/), with no way to react to a CRM event or a form submission. Automation driven by lead data requires the WhatsApp Business Platform.
Stop losing leads to the follow-up gap
Kredoo captures leads from Meta and Google Ads, then follows up on WhatsApp automatically. Live in 5 minutes.
Get Started