How to Set Up Automated Customer Follow-Up with WhatsApp Business API

Automated follow-up on the WhatsApp Business Platform works by sending a pre-approved template message to a customer who has opted in, which opens a 24-hour window in which you can reply freely. Outside that window only approved templates may be sent, and every message should be written back to the customer record.

Most businesses trying this discover the same thing a fortnight in: the WhatsApp Business app and the WhatsApp Business Platform are different products. The app is a phone in someone's hand. The Platform is an API with template approval, opt-in requirements and a messaging window — and only the second one can be automated.

Understanding that window is most of the design work. Everything below follows from it.

What you need before you start

• A number that is not already on the consumer app. Migrating an existing number is possible but it is a one-way move; decide deliberately.
• A verified business account with the provider you choose, which takes days rather than minutes.
• Opt-in you can evidence. Under UK GDPR you need a lawful basis for messaging, and for marketing-style messages that will normally be consent you can show — where and when it was given.
• Somewhere for the messages to land. If replies arrive in an inbox nobody owns, automation makes the problem faster rather than smaller.

Setting it up

1. 1Choose the number and the providerA dedicated business number avoids the migration question entirely. Your provider handles verification and template submission; you keep the number.
2. 2Collect and record opt-inAsk at the point the customer gives you the number — on the booking form, on the call, at the desk — and store where and when they agreed. Opt-in that cannot be evidenced is not opt-in.
3. 3Write and submit your templatesStart with three: appointment confirmation, appointment reminder, and a missed-call follow-up. Keep variables to name, date, time and service. Approval usually takes hours, and vague marketing language is what gets templates rejected.
4. 4Define the triggersEach template fires from an event in your systems, not from a person deciding to send it: booking created, appointment two days away, inbound call unanswered.
5. 5Plan for the replyA reply opens the 24-hour window and is the whole point. Decide in advance what is answered automatically, what goes to a person, and how quickly.
6. 6Write everything back to the recordEvery message sent and received belongs on the customer's timeline. Without that you cannot see whether a customer was already chased, and two people will chase them again.

The three templates worth having first

The reminder timing is a business decision disguised as a technical one. A reminder the day before reduces no-shows; a reminder two days before reduces no-shows and gives you time to offer the freed slot to somebody else.

Where WhatsApp fits against the call

WhatsApp is the second touch, not the first. The pattern that works is call first — because a call gets answered or it does not, immediately — then message if there was no answer. Reversing that order produces a lot of unread messages.

That sequence, with its timings and exit conditions, is the subject of automating lead follow-up; the wider chain from the inbound call through to the CRM record is in end-to-end business automation. WhatsApp is one channel inside both.

Staying on the right side of the rules

Two regimes apply at once and businesses tend to think about only one. WhatsApp's own policy governs templates, opt-in and what counts as marketing. UK law governs the personal data: a lawful basis for the messaging, a retention period for the message history, and a processor agreement with whoever runs the API on your behalf. The ICO's guidance on direct marketing is the reference point for the second.

In practice the distinction that saves trouble is between service messages and marketing. A booking confirmation to someone who just booked is a service message. "We have 20% off this month" to the same person is marketing, and it needs consent you can evidence — not merely a phone number you happen to hold.

What usually goes wrong

• No exit condition. The customer books, and the sequence keeps chasing. This does more damage than never having sent anything.
• Templates written like adverts. They get rejected, and the rewrite loop costs a week.
• Replies with no owner. The window opens, the customer answers, and nobody sees it for two days.
• Messages that never reach the record. The history lives in a separate app and the CRM shows a customer who was apparently never contacted.

Measuring it

Delivery and read rates are the numbers the platform gives you, and they are the least useful. Track reply rate on each template, the share of sequences that exited cleanly, and — for the reminder — the change in no-shows against a baseline you set before switching it on.

If you want the templates and triggers mapped against your own booking flow, book a demo call.

← All articles