WhatsApp for UK restaurants: the booking channel that Deliveroo and OpenTable don't touch

The customer relationship you don't own

The economics of UK independent restaurants right now are simple and grim. Cover margins are compressed, food costs are up, energy is up, staff is short. The lever that actually moves the P&L isn't a new marketing channel — it's second-visit conversion. A diner who came once and never returned is a full night's revenue that walked out.

And that diner belongs, in the current setup, to whoever brought them in. Book through OpenTable, and OpenTable owns the relationship — the email confirmation comes from them, the reminder comes from them, the review request comes from them, and the next time the diner opens the app they see three other restaurants ranked above yours. Book through Deliveroo, and Deliveroo owns the delivery relationship completely, including the takeaway rebook. The restaurant is the kitchen; the aggregator is the customer relationship.

WhatsApp is the one channel where the restaurant owns the diner. The number is captured at the point the booking is confirmed. The reminders come from the restaurant's name. The 'welcome back' message next month comes from a real person the diner met. This isn't a bigger revenue lever than the aggregator — it's a slower, deeper one, and it compounds while the aggregator relationship stays flat.

Where WhatsApp fits alongside the booking platform

Not as a replacement. The booking platform (Resy, OpenTable, SevenRooms, Tock, Collins) does the calendar, the deposit-holding, the walk-in avail — those are all real, and building them yourself is a distraction. What WhatsApp does is the conversational half that the booking platform is bad at.

Same-day changes. A booking for four at 20:00 becomes a booking for six at 20:15 with a message. The booking platform requires cancel-and-rebook and might lose the slot to a walk-in queue in the interim; the message to the restaurant keeps everyone whole.

Special requests that don't fit a form field. A birthday cake to bring out at pudding, a vegan guest who forgot to mention it at booking, a wheelchair user asking about accessibility — these need a human reply. The booking platform's 'notes to restaurant' field is where those go to die.

The month-after nudge. A first-time diner who had a good night is a diner who books again — if they're reminded. A message four weeks later ('we've got the truffle special back on this week if you fancy popping in') from the restaurant is different in kind from a re-engagement email from OpenTable listing three competitors.

Delivery-order rebook. Restaurants who do their own click-and-collect or delivery outside the aggregators can use WhatsApp for the second-order nudge: 'saw you enjoyed the tagine last month, we've got a new lamb dish on'. Aggregator commissions on repeat orders are pure margin left on the table.

What ICO / UK GDPR actually allows on a diner's phone number

The Information Commissioner's Office is precise about what you can and can't do with a number captured at booking. Two categories to keep straight.

Transactional messages — booking confirmation, reminder the day before, table-ready notification for walk-ins with a pager number, day-of change — run on legitimate interest. You don't need consent for these because they're the operational fulfilment of a service the diner asked for.

Marketing messages — the month-after nudge, event promotion, tasting-menu launch — need consent, and specifically opt-in consent, not pre-ticked-box consent. The booking form (or the WhatsApp initial exchange) needs an explicit question: 'may we message you about our menu and events?' with a real unchecked box. A restaurant that treats a captured phone number as blanket marketing consent is a PECR breach waiting to happen, and the ICO takes hospitality-sector complaints seriously.

The practical operating pattern: two lists in your CRM, tagged separately. Transactional list — everyone who ever booked. Marketing list — only those who explicitly ticked the box. Never merge them for a broadcast.

One more thing restaurants get wrong: sending a marketing message from a booking-confirmation thread. Once a diner has replied 'yes' to a booking, that thread has a specific purpose. Turning it into a promotional channel afterwards is exactly what PECR was written to prevent. A separate marketing thread, opened only for opted-in diners, is the clean pattern.

The three messages worth setting up first

Ordered by impact on cover economics.

Reminder the evening before at 18:00. A booking made ten days ago is a booking half-forgotten. A short message the evening before ('looking forward to seeing you tomorrow, 20:00 for four') reduces no-shows measurably in a business where a no-show is a full cover walked out. The booking platform sends its own reminder, but it comes from OpenTable, not from you — and diners parse them as branded promotion, not as your restaurant asking.

Table-ready message for walk-ins holding a spot. Any restaurant that runs a walk-in wait during service should be sending a WhatsApp when the table's ready, not shouting names or asking guests to stay at the bar. Guests appreciate it, the bar gets more relaxed, and it works better than a pager. This is a template that pays for itself in the first busy Friday.

Post-visit thank-you within 24 hours — from the restaurant, not from the platform. Short, human, no ask. A diner who receives this once is meaningfully more likely to return within the month than one who gets nothing (or gets an OpenTable review request). The purpose is not to extract a review; the purpose is to open the door for the next visit.

Where the WhatsApp workflow stops working

Three specific edges.

For a restaurant doing under thirty covers a night, the manual version of everything above works. The owner-operator can text guests personally, and the personal touch is the entire product. Automation here is over-tooling — the guests notice, and not in a good way.

For a delivery-heavy business where the aggregators are the customer relationship, WhatsApp gives you a channel that most of the customers won't come to. Delivery diners rarely convert into WhatsApp direct-bookers; the two audiences overlap less than restaurant owners assume. Investing here is investing in the segment you already have (dine-in guests), not the segment you wish you had (aggregator regulars).

For a restaurant whose entire marketing strategy is Instagram, WhatsApp is the missing back half of the story. The Instagram post gets the DM asking about vegan options; the DM needs to become a booking; and the booking needs to become a returning diner. Only WhatsApp handles the middle two hops well. Restaurants that stop at the Instagram DM without moving the conversation to a channel they own are giving Meta the second-visit that could have been theirs.