WhatsApp is now the default inbound channel for most UK service businesses. It’s faster than email, more personal than web chat, and your customers are already there. But the tooling most teams use for business WhatsApp is either a phone someone keeps on their desk, or a group inbox that turns into chaos within a week.
Here’s a grounded guide to what real WhatsApp automation looks like in 2026 — no hype, just the decisions that actually matter.
First: which API are you using?
There are three ways to run business WhatsApp, and the choice shapes everything else.
1. WhatsApp Business app (free)
Fine for a solo operator with low volume. No automation, no multi-user access, no integrations beyond basic auto-replies. Outgrown by most teams within six months.
2. WhatsApp Business Cloud API (official Meta API)
The real option for any serious business. Lets you connect CRMs, AI agents, web hooks, and multi-user inboxes. Meta handles hosting. Messaging pricing is per-conversation (currently around £0.03–0.06 per business-initiated conversation in the UK, free for user-initiated within the 24-hour window).
3. On-premise / self-hosted gateways (e.g. Evolution API)
Useful for high-volume or cost-sensitive cases, but you’re now responsible for compliance, uptime, and Meta relationship management. Not recommended unless you have dedicated engineering.
What to automate (and what not to)
The biggest mistake we see is automating the wrong things. Good candidates: FAQ responses (hours, location, pricing ranges, services offered); appointment booking linked to a live calendar — this is the single biggest win; qualification (a few routing questions before the conversation reaches a human); follow-ups and reminders (day-before reminders, post-visit check-ins, rebooking nudges).
Bad candidates: emotional conversations — complaints, grief, clinical concerns (route these to a human fast); anything requiring judgement about a specific customer’s situation; high-value sales where relationship building matters more than response speed.
Template messages vs session messages
Meta distinguishes between session messages (replies within 24 hours of a user message — free, flexible) and template messages (business-initiated, pre-approved by Meta, paid). Every automation you build needs to respect this distinction or it won’t scale.
Practical rule: replies within 24 hours can be anything. Outside 24 hours, you need a pre-approved template. Plan your flows around this.
Opt-out is non-negotiable
If your automation ignores STOP / UNSUBSCRIBE / opt-out, Meta will suspend your number. Every serious WhatsApp platform handles this. Verify it does before you go live.
What “good” looks like
A well-built WhatsApp automation, for a typical clinic or service business, answers the first message in under a second, qualifies the enquiry in three or four exchanges, books the appointment into a real calendar, confirms with the customer, and hands off to a human only when needed — logging everything to your CRM in the process.
