WhatsApp automation for customer follow-up

WhatsApp Business app or the WhatsApp Business Platform?

Two products, one brand. The free WhatsApp Business app runs on a phone and suits a small team answering messages by hand. The WhatsApp Business Platform, which most people still call the API, has no app at all: it connects WhatsApp to your own systems, and it is what real automation runs on.

When is the WhatsApp Business app enough?

More often than vendors admit. It gives you a business profile, greeting and away messages, quick replies, labels and a catalogue at no cost. What it cannot do is write to your CRM, follow up on a schedule, or hand a conversation between agents with the history intact.

When do you need the Business Platform?

When messages must reach your other systems, when several people share the load, or when follow-up has to run on a schedule rather than on memory. You reach it through Meta's Cloud API or a Business Solution Provider who bundles an inbox, flow builder and billing. Budget for the provider's monthly fee, Meta's per-message charges (quoted in US dollars, so your rand cost moves with the exchange rate) and the build. Our note on what automation actually costs in South Africa covers sizing that.

One local offer to refuse: tools that drive the ordinary WhatsApp app through an unofficial connection to blast messages. They breach WhatsApp's terms, and the penalty is losing the number your business runs on.

How do opt-in and template messages actually work?

Meta splits business messaging into two states and every rule follows from that. When a customer messages you, a 24-hour window opens in which you can reply freely, in your own words. Outside it you may only send a template Meta approved in advance.

Templates have fixed wording with variable slots for a name, order number or date. Meta reviews and categorises each one, broadly as utility (order updates, reminders, anything tied to a transaction), marketing (promotions, re-engagement, anything selling) or authentication (one-time codes). Marketing templates are priced differently and judged more strictly.

Opt-in is the gate in front of all of it. People must have agreed to hear from you on WhatsApp, captured somewhere you can point to: a tick box on your web form, a line on the quote acceptance, a consent request that meets the POPIA requirements set out below. Blocks and reports feed the quality rating on your number, and a rating that drops far enough cuts how many people you may message in a day.

What does POPIA require when you message customers?

POPIA has been fully in force since mid-2021 and applies to WhatsApp exactly as it applies to email and SMS.

Section 69 covers direct marketing by unsolicited electronic communication. In practice you may not market to someone who has not consented, with one carve-out: where the person is an existing customer whose details you obtained during a sale, you may market your own similar products or services, provided they had a reasonable chance to object then and in every message since. An order update or appointment reminder is not direct marketing, because it flows from the arrangement you already have.

How you ask matters as much as whether you ask. Section 69(2) lets you approach a person whose consent you need once only, and that request must follow Form 4 of the POPIA Regulations. An unsolicited “reply YES” message to someone who is not yet your customer is exactly that single regulated approach, and spending it badly costs you the person permanently. Collecting the tick box on your own form, before you ever message, avoids the problem. The Information Regulator's guidance note on direct marketing sets out how it reads all of this — guidance rather than law, but it is what the Regulator will apply.

The rest is housekeeping. Collect only what the process needs, keep a record of consent you could produce if the Information Regulator asked, and put a written operator agreement in place with your messaging provider and CRM vendor, since they process personal information on your behalf. None of this is legal advice; an hour with your attorney before you switch on outbound messaging is money well spent.

Where does WhatsApp automation go wrong?

• It sounds like a robot. Exclamation-marked corporate copy in a channel where people write like people. Write flows the way your best salesperson types, then read them aloud.
• There is no way out. Every flow needs an obvious escape to a human, and the handover must work: same conversation, nothing repeated, somebody actually watching in business hours.
• It sends too much. Three follow-ups on an unanswered quote is persistence. Seven is a report. Cap the sequence, stop on any reply, honour a “stop” instantly.
• It knows nothing about the customer. A payment reminder to someone who paid yesterday costs more trust than the automation saves, which is why this work usually starts with connecting WhatsApp to your CRM and website forms.
• It sits on a broken process. If your quote turnaround is the real problem, faster follow-up just tells more people, sooner, that you are slow. Messaging is the visible end of a process; the workflow automation behind it makes the message worth sending.

What does setting this up actually involve?

Less than the sales pitches imply, more than a weekend. In rough order:

1. Pick two or three flows worth building

   Quote follow-up and appointment reminders usually repay the effort first: high volume, rule-based, currently running on somebody's memory.

2. Sort out the number, the account and the templates

   Meta business verification, a migrated or dedicated number, a provider account, then templates submitted for approval. Approval is usually quick, but rejections cost a day.

3. Connect the systems

   CRM, calendar, order or job system, website forms. Most of the real work sits here, and it decides whether the project is useful or a glorified auto-reply.

4. Build the exceptions in, not around

   What happens on a reply, on silence, on “stop”, on a question nobody anticipated. Then test with your own staff on real phones.

A focused first build, one or two flows with one system connected, takes weeks rather than months. What stretches a timeline is rarely WhatsApp: it is systems never designed to talk to each other, and internal decisions about who owns a reply. That is the same pattern we work through when we automate approvals, reporting and customer follow-up.

Common questions

Can we automate WhatsApp using the business number we already advertise?

Usually yes, and there are two routes. Coexistence keeps the WhatsApp Business app on the phone and connects the Cloud API to the same number, carrying across roughly six months of one-to-one history; group chats do not come across. Full migration hands the number to the Platform and the app goes away. Ask your provider which of the two they support, because not all support both.

Do we need consent before sending WhatsApp appointment reminders?

A reminder about a booking the customer made is a service message, not direct marketing, so POPIA's section 69 rules do not apply to it. You still need their agreement to be contacted on WhatsApp and a working way to stop. Add a promotion to that reminder and it becomes marketing, with the consent rules in full.

What does WhatsApp automation cost to run each month?

Three separate costs: a monthly platform fee from your provider, Meta's per-message charges billed in US dollars, and the once-off build. Meta revises its pricing periodically, so check current South African rates with your provider before you budget.