When customers already message you on WhatsApp, the slow part is rarely the conversation itself. It is the gap before anyone replies, the booking someone forgets to confirm, and the order question that arrives while you are with another customer. I set up WhatsApp Business automation for UK businesses so that new enquiries get an instant, useful reply, reminders and order updates go out on time, and every conversation that needs a person reaches one with the history attached.
The aim is not to remove people from WhatsApp. It is to stop routine messages eating the day, and to make sure no enquiry sits unanswered because the phone was in someone’s pocket.
Who this suits, and who it does not
It suits businesses where WhatsApp is already a real sales or service channel: clinics and salons confirming appointments, trades quoting from photos customers send, online shops answering delivery questions, driving schools, tutors, restaurants taking group bookings, and anyone running click-to-WhatsApp ads on Facebook and Instagram that bring in more chats than staff can answer quickly.
It is not worth it if you receive a few WhatsApp messages a week. The free Business app, set up properly, will do the job. It is also the wrong channel for sending promotions to a list of numbers that never agreed to hear from you on WhatsApp. That breaks UK law and Meta’s own policy, and Meta restricts numbers that collect too many blocks and reports.
The WhatsApp Business app or the WhatsApp Business Platform
There are two different products, and choosing between them is the first decision.
The WhatsApp Business app
The free app on a phone. It gives you a business profile, a product catalogue, labels for sorting chats, quick replies, a greeting message for first contact and an away message outside opening hours. For a small team handling messages by hand, configuring these well is often all the automation needed, and I will tell you so if that is the case.
The WhatsApp Business Platform (API)
The WhatsApp Business API is the version that other software can drive. It is how a WhatsApp number connects to a booking system, a shop or a CRM, sends messages triggered by events, and lets several staff answer from one shared inbox. You access it through Meta directly or through a provider that sits on top of Meta, and Meta charges for certain message types. It needs a verified Meta Business account, an approved display name and a phone number set up for the platform.
Moving a number that already runs on the Business app needs care. Depending on the provider and the route chosen, you may be able to keep using the app alongside the platform, or the number may have to leave the app. I check which applies before anything is switched, so you do not lose access to chats customers rely on.
The rules that shape every WhatsApp build
Three sets of rules decide what a WhatsApp build is allowed to do, so I design around them from the first conversation rather than discovering them at template approval.
The 24-hour customer service window
When a customer messages you, a 24-hour window opens in which you can reply freely, with any wording. Once it closes, you can only start a conversation with a message template that Meta has approved in advance. A reminder for next Tuesday’s appointment, sent on Monday, is a template. So is an order dispatch notice.
Templates and their categories
Templates are grouped as utility (updates about something the customer has already started, such as an order or booking), authentication (one-time codes) and marketing (anything promotional). The category affects both the cost and the rules. Meta reviews each template and will recategorise a utility message as marketing if it contains a discount or a sales pitch, so I write utility templates that stay strictly about the transaction.
Opt-in, PECR and UK GDPR
Meta requires an opt-in before you send someone business-initiated messages, and the opt-in has to make clear that the messages will come from your business on WhatsApp. UK law adds its own layer. Under PECR, marketing sent by electronic message, which in my reading of the ICO guidance includes WhatsApp, needs the person’s specific consent, or the soft opt-in for existing customers who bought something similar and were given a simple way to refuse. Service messages about an existing order or booking are not marketing, but adding a promotion to one turns it into marketing.
The phone numbers and message content are personal data under UK GDPR, so your privacy notice should mention WhatsApp, your provider needs a data processing agreement, and someone should decide how long chat histories are kept. This is not legal advice, and for anything unusual I would ask you to check with a solicitor.
What I build
Each workflow below is something I scope with you and test with real messages before it goes live.
Instant replies to new enquiries
A first reply that arrives in seconds, answers the likely question or asks the two or three things your team always needs to know (service, postcode, preferred date), and tells the customer honestly when a person will pick it up. For enquiries arriving from ads, this is where most of the value sits.
Enquiries into your CRM
New WhatsApp contacts and their answers are created or updated in your CRM or a shared sheet, tagged with the source, and assigned to the right person using lead routing rules. Your pipeline then shows WhatsApp leads next to web forms and calls, instead of in one person’s phone.
Booking confirmations and reminders
Confirmation when a booking is made, a reminder before the appointment with options to confirm or rearrange, and a follow-up afterwards if you ask for reviews. The booking system stays the source of truth; WhatsApp is the messenger.
Order and delivery updates
For online shops: order confirmed, dispatched with tracking, delivery issues, and a reply path for “where is my order” questions that pulls the status rather than waiting for staff.
Hand-off to a person
Every flow has a clear route to a human: a keyword, a button, or automatic hand-off when the customer is unhappy or the question falls outside the script. Staff answer from a shared inbox and see the whole conversation. If you want an AI assistant answering free-text questions too, I add it with a human in the loop for anything uncertain.
Consent capture and opt-out handling
Opt-in recorded with date, wording and source; an opt-out word that works instantly; and a suppression list that every future send checks. This is dull work, and it is what keeps the number healthy.
How I run the project
- Map the conversations. I read a sample of your recent WhatsApp chats (with personal details removed where possible) to see what customers ask, when, and where replies stall.
- Choose the setup. Business app or platform, which provider, which number, and what connects to what. I write this down with the running costs you should expect from Meta and the provider.
- Write the messages and templates. Plain, short, British English, in your tone. Templates are submitted to Meta for approval before any build depends on them.
- Build and connect. The flows, the links to your booking system, shop or CRM through webhooks or an automation platform, and the shared inbox.
- Test with real devices. Every path, including opt-out, hand-off, out-of-hours and a failed connection, on Android and iPhone.
- Launch and watch. After go-live I check for failed sends, rejected templates and quality warnings, and adjust the flows that cause them.
If your WhatsApp chats come from paid ads, I can also make sure a conversation counts in your reporting. My guide to checking your conversion tracking works covers the first checks.
What goes wrong most often
- Promotions sent as utility templates. Meta reclassifies them or rejects them, and the build that relied on them stops.
- No opt-in record. The business believes customers agreed, but cannot show when or to what.
- A bot with no way out. Customers get stuck in a menu loop, block the number, and the quality rating drops, which lowers how many people you can message.
- The number lives on one phone. When that member of staff leaves or the phone breaks, the business loses its chat history.
- Reminders that drift from the diary. A reminder goes out for an appointment that was moved, because WhatsApp reads a copy of the booking rather than the system itself.
What you receive
- A written plan: setup choice, provider, flows, templates and expected running costs.
- Working flows, connected to your systems and tested.
- Approved templates and an opt-in and opt-out process with records.
- A short guide for staff on the shared inbox and hand-off.
- Access to every account in your name, not mine.
Pricing
Each project is quoted after a free first call, in GBP, and agreed in writing before work starts. Separately from my fee, Meta charges for some messages, with rates set by message category and the recipient’s country, and most providers add their own monthly fee. You pay those directly, so the costs stay visible and the accounts stay yours.
Next step
Send me a description of how customers use WhatsApp with you now, roughly how many chats you get a week, and the systems you use for bookings, orders or leads. I will tell you whether the Business app is enough or the platform is worth it, and what I would build first. You can book a free 30-minute call to talk it through.