WhatsApp automation for business: 9 workflows worth automating first, and what a good tool needs

Shalini Reddy runs a nine-person business in Visakhapatnam that sells and services inverter batteries. Her WhatsApp number gets about 60 chats a day, and when she read a week of them, more than half were one of five messages: what’s the price of a 150 Ah battery, is my service booked, when is the technician coming, my warranty card is lost, do you take the old battery back. Two office staff typed the same answers all day. Meanwhile the message that would have made money, a reminder that a customer’s annual service was due, never went out, because nobody had time.

That gap is what WhatsApp automation for business is for. It isn’t a robot that runs the shop. It sends the predictable messages on time, so people are free for the chats that need judgement.

What WhatsApp automation is

Every automated workflow has the same three parts.

A trigger starts it: a customer sends a message, taps a button, arrives from an ad, or something happens in another system, such as an order being placed or a service being booked.

Steps follow: send a message or an approved template, wait for a reply, check what happened, tag the contact, update a field, call another system.

And there’s a stopping rule. The customer bought, replied, asked for a person, or went quiet for two days. Workflows without a stopping rule are how a customer gets “you left something in your cart” an hour after paying.

Two platform rules shape everything else. Free-form WhatsApp message automation only works inside the 24-hour window that opens when a customer writes to you. Outside it, the workflow has to send a template Meta has approved, to someone who has opted in. Our glossary explains both terms, and the opt-in guide covers what counts as consent.

Nine workflows to automate first

They’re in the order we’d build them. The first four answer customers faster. The rest send messages that currently don’t get sent.

1. A first reply that sorts the chat

Trigger: a message arrives from someone with no open conversation. The workflow sends one message with up to three buttons (Meta’s limit for reply buttons), waits for the tap, tags the contact with the choice and passes the chat to the right team. For Shalini that’s “New battery”, “Service or warranty” and “Talk to us”.

Keep it to one question. If the customer types instead of tapping, send the chat to a person, don’t repeat the menu.

2. An instant answer to ad enquiries

A chat that starts from a Click-to-WhatsApp ad should get a reply in seconds, because the person has just messaged three other dealers too. Use the ad message as the trigger, reply with the price range and one qualifying question, and tag the contact with the ad it came from.

There’s a cost reason as well. When someone messages you from such an ad on their phone and you reply inside the window, Meta opens a free entry point window that can stay open for up to 7 days, and messages in it aren’t charged. A late first reply wastes it. How the ad window works has the detail.

3. Confirmations sent by your own system

When a booking is saved in your service software or an order is placed on your site, that system sends a webhook (a small HTTP request carrying the details) and the workflow sends a utility template: booking date, time slot, technician’s name. No one types anything.

This is usually the highest-volume workflow and the least risky, because the customer is expecting the message.

4. A reminder that checks whether it landed

Send the reminder template the evening before, then branch on what Meta reports back. Meta’s webhooks say whether each message was sent, delivered, read or failed.

• Delivered and read: do nothing more.
• Delivered but unread by 9 am: tag the contact for a phone call.
• Failed: tag it and tell the office, because the number is probably wrong.

Most tools send and hope. Branching on status is what turns a reminder into fewer missed appointments.

VR Venkat Rao talking to Reddy Power Systems

1. Reddy Power Systems:
   Template · Utility Hi Venkat, your inverter battery service is booked for tomorrow, 11 am to 1 pm. Our technician Suresh will call before he arrives. 6:00 pm
   • Confirm
   • Change the time
2. Delivered · read 6:42 pm · no tap by 9 pm
3. Tagged: confirm by phone
4. Venkat Rao:
   Change the time 7:15 am
5. Chat passed to the service desk

5. One follow-up when nobody replies

You sent a quotation and heard nothing. A workflow can wait for a reply and, if none comes in 24 hours, send a single follow-up template. If the customer replies at any point, the wait ends and the chat goes to sales.

Send one follow-up, not three. You’ll lose a few orders. You’ll keep people from blocking you, and you’ll run into Meta’s per-user marketing limit less often: WhatsApp caps how many marketing templates a person receives across all businesses, the cap isn’t a published number, and a blocked send comes back as error 131049.

6. Tags from taps

Each button a customer taps tells you something: which product, which branch, which budget. Have the workflow write it to the contact as a tag as it happens. In three months those tags are your campaign audiences (“asked about 200 Ah, didn’t buy”), and nobody had to fill in a spreadsheet.

7. Contact details updated as you learn them

Tags answer yes-or-no questions. Fields hold values: battery model, purchase date, next service due, preferred language. A workflow can update a contact field from a reply or from the data your system sent in the webhook. Shalini’s annual-service reminder only became possible once “purchase date” lived on the contact instead of in a paper warranty register.

8. A line written to your other software

The HTTP request step runs the other way from workflow 3: the automation calls another system. When a customer confirms a slot, the workflow posts it to the booking software. When a lead taps “Call me”, it adds a row to whatever the sales team already works from. If your software has an API, this step replaces retyping.

It’s also the one workflow where you’ll want someone technical for an afternoon, to set up the address, the credentials and what to do when the other system doesn’t answer.

9. Shopify cart recovery, and an AI agent for repeat questions

Two workflows that most tools ship ready-made, so you configure rather than build.

If you sell on Shopify, a cart reminder is the obvious one: a template goes out some time after a cart is left, and is cancelled if the shopper buys first. Meta treats cart reminders as marketing even when the shopper asked for them, so each costs the marketing rate. Our abandoned cart playbook covers timing and wording.

For free-typed questions that buttons can’t predict, an AI agent answers from your own pages and documents and hands the chat to a person when it can’t. The handoff matters more than the answers. Test what the agent does with a complaint before a customer does. We compared buttons and AI in WhatsApp chatbot for business.

What you shouldn’t automate

Complaints. Refund and payment disputes. Anything where the customer has already asked twice. A price negotiation with a dealer who buys forty batteries a year.

Automation is good at the first message and the reminder. It’s bad at the fourth message in an argument. Every workflow should have a way out to a person, and a rule that a human reply stops the automation for that chat.

Don’t automate cold outreach either. A workflow that sends templates to a bought list will be blocked and reported, and Meta’s limits tighten on accounts that send unwanted messages. Bulk WhatsApp without a ban explains how that plays out.

What automated messages cost

An automated message is billed exactly like one a person sends. Meta charges per delivered message, by category, and the India rates on the card effective 1 October 2026 are:

Message	Rate per delivered message, before GST
Marketing template (offers, cart reminders, follow-ups that sell)	₹0.8631
Utility template (confirmations, reminders about something the customer did)	₹0.115
Service message (free-form reply inside the 24-hour window)	₹0.115 after 1,000 per number per month

Meta, not you, decides a template’s category, and a “reminder” with an offer in it is marketing.

Take Shalini’s number as an illustrative month: 700 booking confirmations and 700 reminders as utility templates, 300 quotation follow-ups as marketing, and 2,500 automated first replies and button messages inside the window.

• Utility: 1,400 × ₹0.115 = ₹161
• Marketing: 300 × ₹0.8631 = about ₹259
• Service: 2,500 from automation plus 4,000 typed by staff is 6,500, less 1,000 free = 5,500 × ₹0.115 = about ₹633

That’s roughly ₹1,050 a month to Meta, before GST and before your provider’s fee. The number to watch is the last one. A workflow that sends four short messages where one would do quadruples it. What WhatsApp costs from October 2026 works through more examples.

What a good WhatsApp automation tool needs

Searches for the best WhatsApp automation tool mostly return lists. The demo matters more than the list. Ask to see these working, on your number if possible.

Ask the vendor to show you	Why it matters
A workflow started by a message, a button tap, an ad enquiry and a webhook	These four triggers cover nearly everything in this article
A wait step that branches on delivered, read, replied, failed and timed out	Without it you can’t build workflows 4 and 5
What happens when a person replies mid-workflow	The automation should step aside, not talk over your staff
A test run that doesn’t message real customers or change your reports	You’ll edit workflows often, and you need to try them safely
A list of runs showing where each one stopped, with a retry	”It didn’t send” has to be answerable in a minute
An HTTP request step with stored credentials	So passwords for your other systems aren’t pasted into a workflow
The 24-hour window handled for you	Outside the window the tool should send a template, not fail silently
Opt-out handling	A customer who says stop should drop out of every workflow
How many active workflows your plan allows, and what an extra one costs	Limits on this are common and rarely on the pricing page’s first screen
Who bills you for Meta’s charges, and at what rate	Compare against Meta’s own rate card

If the vendor can’t show the run list and the test mode, keep looking. You’ll spend more time fixing workflows than building them.

Is the free app enough?

Sometimes. The WhatsApp Business app has a greeting message, an away message and saved quick replies. For a shop where one or two people answer everything, that covers workflow 1 in a basic form and costs nothing.

It can’t start a message from your booking system, branch on whether a reminder was read, or send to someone outside a chat you opened by hand. Those need the WhatsApp Business Platform, which you reach through a provider. App vs Platform covers the trade-offs, including what you give up.

Start with one

Read last week’s chats and count the message your staff typed most often. Then list the message you meant to send and didn’t. Build the first as a button reply and the second as a template with one status branch. Run both for a fortnight and read every conversation they touch before you build a third.