WhatsApp Business API Setup for Restaurants UK: The Complete 2026 Guide

6 min read • 2026-08-24

The Phone Rings During Service, and Nobody Answers

It is 7:15pm on a Friday in Manchester. The dining room is full, the pass is backed up, and the restaurant phone has been ringing on and off since six. Nobody can pick it up. Every one of those missed calls was somebody trying to give you money: a table for four, a birthday booking, a large collection order. Some callers ring back later. Many just book somewhere else.

This is the daily reality in most UK restaurants, pubs and cafés, and it is exactly the problem the WhatsApp Business API solves. Your guests are already on WhatsApp — it is the default way Britain communicates, with tens of millions of users in the UK checking it dozens of times a day. Yet most restaurants still run bookings through a phone line, a paper diary and a voicemail nobody checks.

This guide walks through exactly how a UK restaurant sets up the WhatsApp Business API properly: what it is, what you need before you apply, the step-by-step setup, what it costs in pounds, the compliance bits you cannot skip under UK GDPR, and the five automations we install first for restaurant clients because they pay for themselves fastest.

First, Clear Up the Confusion: App, API or Platform?

Nearly every restaurant owner who Googles this gets stuck here, so let us untangle it once and for all. There are three different things called "WhatsApp Business":

• WhatsApp Business App — the free download. One phone, one person, manual replies. Fine for a single-site café doing a handful of enquiries a day. It cannot do automated booking confirmations, reminders or follow-ups, and it lives on one handset that gets left in the office during a busy shift.
• WhatsApp Business API — also called the WhatsApp Business Platform. These are two names for the same thing: Meta's official interface that lets software send and receive WhatsApp messages on your behalf, automatically. This is what powers booking confirmations, no-show reminders and review requests that go out without anyone lifting a finger.
• Business Solution Providers (BSPs) — companies officially vetted by Meta (Twilio, 360dialog, Wati and others) through which most businesses access the API, because applying directly is fiddly and support is thin.

If you want automation — which is the entire point — you need the API. The good news: the API itself is free from Meta. You pay per conversation/message and, optionally, whatever your platform or agency charges to build the automations on top.

What You Need Before You Start (the Pre-Flight Checklist)

Gather these before touching any settings. Missing items here are the number-one cause of applications stalling for weeks:

1. A Meta Business Manager account at business.facebook.com, owned by the restaurant's real business entity. Use the email address tied to whoever manages your Facebook page.
2. Your Companies House details and matching website. Meta's business verification checks that your legal name, address and web presence line up. A restaurant trading as "Luigi's Kitchen Ltd" should verify against that exact name, not the sign above the door.
3. A dedicated phone number for the WhatsApp line. It needs to be able to receive a one-time verification code by SMS or voice call. Crucially, if the number is already registered on the WhatsApp or WhatsApp Business App, it must be migrated or deregistered first — a number cannot sit on both.
4. Admin access to your Facebook page (if you have one), because the WhatsApp account gets linked to it.
5. A display name that matches your brand. Meta reviews it, and names that do not match your trading name or website get rejected.
6. Someone with 30 minutes and a cup of tea to do the verification steps. Honestly, this is often the scarcest resource in a working kitchen.

The Step-by-Step Setup

Here is the actual sequence, in order. Skipping ahead is what causes rejections:

Step 1: Create and Verify Your Meta Business Portfolio

Sign up at business.facebook.com, add your restaurant as a business asset, and fill in legal name, address and phone exactly as they appear at Companies House. Then submit business verification: upload a utilities bill, bank statement or Companies House document, and make sure your website displays the same business name and contact details. Verification typically takes a few days. Do everything else while you wait.

Step 2: Add WhatsApp Through a Platform

You can request API access directly inside Meta Business Manager, but most restaurants go through a BSP because the direct route gives you raw infrastructure and almost no hand-holding. Pick a platform that fits a hospitality budget — 360dialog charges a flat monthly fee per number, Twilio bills per message plus usage, and tools like Wati bundle an inbox and simple flows. Whichever you choose, connect it to your verified Business Manager and authorise it.

Step 3: Register Your Number

Register the restaurant's dedicated number to the API. If it currently lives on the WhatsApp Business App, use the migration flow so your existing chat history moves across rather than starting cold. Once registered, the number can no longer be used in the normal apps — staff reply through the platform inbox instead, which is actually better during service because any manager can pick up any conversation from any device.

Step 4: Choose Your Display Name and Get the Green Tick Sorted Later

Submit your display name ("Luigi's Kitchen"). It gets reviewed within hours usually. The famous green verified tick comes separately once you are messaging at scale with a good quality rating — it is nice, not essential, and guests recognise your profile picture and name regardless.

Step 5: Create Message Templates and Get Them Approved

Business-initiated messages outside the 24-hour customer service window must use pre-approved templates, each falling into a category: utility (booking confirmations, order updates), authentication (verification codes) or marketing (offers, event nights). Write them clearly — "Hi {{1}}, your table for {{2}} on {{3}} at {{4}} is confirmed. Reply to this message if anything changes." — and avoid promotional language in utility templates, because miscategorised templates are rejected and repeat rejections hurt your account quality.

Step 6: Understand the 24-Hour Window and Messaging Limits

When a guest messages you first, you can exchange messages freely for 24 hours — perfect for live enquiries. After that window closes, only approved templates can re-open the conversation. New accounts start with a limit of 250 messages per rolling 24 hours to unique guests, rising automatically to 1,000, then 10,000 and beyond as your quality rating stays healthy. Quality drops if people block or report you, which is why opt-ins matter (more below).

Step 7: Connect It to Your Bookings System

This last step is where the magic happens. On its own, the API is just a pipe. Connected to your reservation diary (or a system like GoHighLevel acting as your bookings brain), it becomes automation: a booking made online triggers an instant confirmation; 24 hours before service, a reminder goes out asking guests to reply to cancel; a no-show triggers a polite re-engagement; the morning after their visit, a review request fires. None of it requires anyone on shift to remember anything.

The Five Automations Worth Installing First

We build these for restaurant clients in this exact order, because each maps to money already leaking out of the business:

1. Booking Confirmation + No-Shot-Killing Reminder

Instant confirmations stop the "can you just confirm our booking?" calls. The reminder is the real earner: sent 24 hours ahead, asking guests to reply if plans change. Empty tables from no-shows are the silent killer of restaurant margins — industry surveys have repeatedly put UK no-show rates in double digits on busy weekends, and every recovered table is pure cover revenue. Restaurants routinely report no-shows dropping sharply once a reminder with an easy reply-to-cancel goes out, because cancellations become effortless and same-day waitlists can backfill the gap.

2. Waitlist and Table-Ready Alerts

Saturday night, 45-minute wait. Instead of buzzing a coaster, take the guest's mobile, text them a WhatsApp when the table is ready, and let them have a drink at the bar while they wait. Guests wander less, walkaways drop, and the front-of-house stops shouting half-pronounced surnames across a packed room.

3. Collection and Delivery Updates

"Your order is being prepared" and "Your order is ready for collection" as automatic WhatsApp updates slash door congestion and those "how long is my food going to be?" calls that interrupt the card machine. If you take deposits for large orders, the payment-link-plus-confirmation flow slots neatly into this sequence too.

4. Post-Meal Review Requests

The morning after a visit, a short thank-you with a Google review link. Timing is everything: ask during the meal and it feels needy; ask three weeks later and the warmth has gone. Next-morning hits the sweet spot, and because WhatsApp gets read — open rates are commonly reported above 90% versus roughly 20% for email — response rates embarrass your old email campaign.

5. Win-Backs and Event Nights

Guests who visited in January but vanished by April get a tasteful template in the marketing category: a seasonal menu launch, a wine evening, Sunday roast availability. Used sparingly — once or twice a month maximum — this is the cheapest marketing channel a restaurant owns, because you are messaging people who already chose to hear from you rather than renting strangers' attention.

What It Actually Costs a UK Restaurant

Budget for three separate lines, because agencies quoting "from £99" tend to blur them:

To ground it: a mid-sized restaurant sending 800 booking-related utility messages and 500 marketing messages a month will typically land in the low tens of pounds on Meta fees, plus the platform subscription. Against even one saved Saturday-night four-top (£150–£250 of covers), the maths is not close.

The Compliance Bits You Cannot Skip (UK GDPR)

Get this wrong and Meta restricts your number, the ICO can investigate, and guests rightly get cross. Four rules cover most of it:

• Collect opt-ins honestly. Only message people who gave you their number and agreed to hear from you — booking forms with a pre-ticked box do not count. Say plainly what they are signing up for: booking updates and occasional offers.
• Honour STOP instantly. Every marketing message carries opt-out wording, and an opt-out must flow through to every connected system within a day. Log it centrally so a guest who opted out never hears from you again.
• Categorise templates truthfully. Sending offers dressed up as "order updates" is the fastest route to a quality-rating slide and account restriction.
• Keep data handling proportionate. Guest names, numbers and visit history are personal data: store them securely, delete on request, and include your privacy notice link in your opt-in wording.

Mistakes We See Restaurant Owners Make

• Using the owner's personal number. It cannot be migrated cleanly once it is someone's daily-driver WhatsApp, and it leaves the business hostage to one phone. Get a cheap SIM or VoIP number dedicated to the restaurant.
• Blasting marketing in week one. Fresh accounts that immediately mass-send offers get flagged. Start with transactional messages (confirmations, reminders), build a clean quality history for a few weeks, then introduce marketing gradually.
• No human fallback. Automation answers instantly; a named person still answers the tricky replies. Route "talking to a human" intents to a staffed inbox notification so complaints and allergy questions never hit a dead end.
• Treating it as separate from bookings. The API bolted onto nothing changes little. The compounding value comes from wiring it to your diary, deposits and review flow — ideally in one system like GoHighLevel so every touchpoint shares the same guest record.
• Ignoring the quality rating. Blocks and reports throttle how many people you can message. Relevant, expected, infrequent messages keep the pipes wide.

DIY or Done-For-You?

If you are comfortable in Meta Business Manager, enjoy admin, and have a quiet week, the DIY route above will get you live for the cost of platform fees alone. Realistically, though, most owners attempt it between services, stall at business verification, and come back to it "after Christmas" — while another season of missed calls and no-shows quietly costs more than the setup ever would.

That is the gap we fill at Systrify's WhatsApp Business automation service. We handle the Meta verification, number registration, template writing and approvals, then build the booking-confirmations, no-show reminders, review requests and win-back campaigns into a single dashboard alongside your other marketing — with fixed UK pricing from £299 rather than the four-figure quotes typical agencies lead with. Everything is built on official channels, GDPR-clean, and handed over with training so your team is never dependent on us.

Want the same setup for your restaurant, café or takeaway — including the exact no-show-killing reminder sequence described above? See how Systrify sets up WhatsApp automation for UK restaurants, or book a free 20-minute audit and we will map which of the five automations would earn its keep first in your venue.

Related reading: How WhatsApp automation booked a Birmingham plumber 40 extra jobs.

Building with AI? At Systrify, we help businesses implement AI automation that is reliable, verified, and built to scale. Get in touch to see what is possible.