Key takeaways
- Use a business number on a venue device, not a manager's personal WhatsApp.
- Set an away message with your hours and booking link, and a small library of saved replies for the questions you get every day.
- A booking is not confirmed until it is in your booking system; send the confirmation from there.
- Keep only the chat data you need, delete it on a schedule, and get consent before any marketing broadcasts.
Is WhatsApp right for your venue?
WhatsApp suits venues whose guests already message them: younger crowds, tourists who prefer not to call, groups organising a night out and regulars who like a quick chat. It is less useful if your guests mostly book online or by phone, or if nobody can check messages during the day.
Messaging with automated replies is now familiar to many people. In a 2024 government survey, six in ten UK adults had used an AI chatbot in the past three months[1]. But familiarity is not the same as enthusiasm: the same research found public associations with AI were still dominated by negative concepts, though younger people were more positive[1]. Guests generally like quick answers; they do not like feeling fobbed off by a machine.
- Used an AI chatbot 60%
Source: Department for Science, Innovation and Technology, 2024[1]
Show the data
| Item | Value |
|---|---|
| Used an AI chatbot | 60% |
Decide before you start who will own the inbox and when it is checked. A WhatsApp channel that is answered on Monday and ignored on Saturday does more harm than not offering one.
Set it up properly
A clean set-up takes an hour and saves confusion later.
Use a venue phone and number
Install WhatsApp Business on a phone the venue owns, with a number that belongs to the business. Avoid using a manager's personal number.
Complete the business profile
Venue name, address, opening hours, website and booking link, and a short description in your own words.
Write a greeting message
A short welcome for first-time messages, with what you can help with and your booking link.
Write an away message
For closed hours and busy service, with your hours, the booking link and when you will reply.
Build saved replies
A small library for your most common questions (see below).
Use labels
For example "Booking request", "Event", "Complaint", "Done", so anyone can see what needs action.
Secure the account
Turn on two-step verification and lock the phone with a passcode.
Put the WhatsApp link or number on your website and Google listing only once the inbox has an owner and the away message is live.
Saved replies for everyday questions
Saved replies let staff answer common questions in seconds and give every guest the same correct answer. Write them in your venue's voice and keep them short.
| Shortcut | Reply |
|---|---|
| /hours | We're open Tue to Sat, 12 to 3 and 5.30 to 10, and Sunday 12 to 6. Kitchen closes 30 minutes before. |
| /book | You can book any time here: [booking link]. For groups of 8 or more, send us the date and numbers and we'll call you. |
| /dogs | Dogs are very welcome in the bar area. The dining room is dog-free. |
| /parking | The nearest car park is on Mill Lane, two minutes' walk. On-street parking is free after 6pm. |
| /allergens | Thanks for letting us know. A member of the team will reply with the allergen information for the dishes you're interested in. |
| /events | Thanks for your enquiry. Could you send the date, rough numbers and the occasion? Our events manager will reply within one working day. |
Review the library monthly, especially hours and parking, and whenever anything changes. An out-of-date saved reply spreads the mistake to every guest who asks.
Response times you can keep
Messaging creates an expectation of speed. Set a standard you can actually meet, and tell guests what it is.
- Same-day booking requests: reply as quickly as you can, ideally within the hour while open.
- Future bookings and general questions: reply the same day while open.
- Events and large parties: acknowledge the same day, with a full reply within one working day.
- Complaints: acknowledge the same day and move to a phone call with the manager.
- During service: let the away message do its job, then work through messages oldest first after the rush.
Give the inbox an owner on every shift, like the phone and the callback list. "Whoever has the phone" is not an owner.
Moving bookings into the diary
The biggest risk with WhatsApp bookings is that they never reach the booking system. A guest who was told "see you Saturday" in a chat, but who is not in the book, will arrive to no table.
- Read the request and check availability in your booking system.
- Enter the booking in the system, with the guest's name, number, party size and any notes.
- Send the system's confirmation, which contains the terms and a cancellation link.
- Reply in the chat: "All booked, you'll have a confirmation text now."
- Label the chat "Done".
If you take deposits, send the payment link from your booking or payment system. Never ask for card details in a chat.
Allergens and written answers
Guests often ask about allergens by message, and written answers are valuable: confidence in allergen information given verbally by staff fell to 60% in 2025, while written information remained far more trusted[2]. But a chat reply is only as good as its source.
- Answer allergen questions only from your current allergen information, never from memory.
- If the person on the inbox does not have it, use the /allergens reply and pass it to someone who does.
- Copy the allergy into the booking notes, so the kitchen and the server see it before the guest arrives.
Handing the inbox between shifts
A shared inbox needs a handover, just like the till. The person finishing a shift should leave the next person a clear picture of what is outstanding.
- Every chat that needs action has a label: booking request, event, complaint or waiting for reply.
- Anything promised to a guest ("I'll check with the chef and come back to you") is noted with a time.
- Chats that are finished are labelled "Done" so nobody replies twice.
- Anything unusual, such as an unhappy guest or a large group still deciding, is mentioned in the shift briefing.
If several people use the inbox, agree a simple signature, such as a first name at the end of each reply. Guests like knowing who they are talking to, and it helps the team trace what was said.
Keep automated replies honest
Greeting and away messages are automated, and guests know it. Write them so they are clearly from the venue's system, not pretending to be a person, and so they always give a useful next step: the booking link, your hours and when someone will reply.
If you add any further automation, such as replies that answer questions on their own, tell guests plainly and make it easy to reach a person. Check the answers it gives regularly. An automated reply that confidently gives last month's opening hours is worse than none.
Mistakes that cause problems
- Telling a guest "booked" in the chat without entering it in the system.
- Running the account on a manager's personal phone, so it leaves when they do.
- No away message, so evening messages sit unanswered until the next afternoon.
- Answering allergen questions from memory because the chat feels informal.
- Adding everyone to a broadcast list without asking.
Guest data and UK GDPR
WhatsApp chats contain personal data: names, numbers, dates, sometimes health information about allergies. UK GDPR requires personal data to be limited to what is necessary and kept in identifiable form for no longer than necessary[3].
- Mention WhatsApp in your privacy notice: what you use it for and how long you keep chats.
- Move what you need into your booking system, then archive or delete chats on a schedule, for example monthly.
- Do not forward guests' messages to personal phones or other groups.
- Keep the venue phone secure and remove access when staff leave.
Security matters because hospitality is not strong on it: only 25% of food or hospitality businesses had sought external cyber security information or guidance in 2025, against 42% of businesses overall[4]. Two-step verification and a passcode on the phone are the minimum.
Marketing and broadcasts
It is tempting to send offers to everyone who has ever messaged you. Under PECR, marketing emails and texts to individuals generally need their prior consent[5], and the safest approach is to treat WhatsApp marketing the same way. Ask before you add anyone to a broadcast list, record who agreed, and make it easy to stop.
Example: a fictional wine bar asks guests at the end of a booking chat, "Would you like a message when we have tasting nights? Just reply YES." Those who reply YES are added to a broadcast list with the date they agreed; everyone else only hears from the bar about their own bookings.
Frequently asked questions
Should we use WhatsApp or the WhatsApp Business app?
Use the WhatsApp Business app on a phone the venue owns, with the venue's own number. It adds a business profile, away messages, greetings and saved replies, and keeps the account with the business rather than a member of staff.
Can guests book a table by WhatsApp?
They can send a booking request. Treat it like a phone request: check availability, enter it in your booking system and send the system's confirmation. Do not reply "booked" in the chat until the booking is in the system.
How quickly should we reply to WhatsApp messages?
Set a standard you can meet and tell guests what it is, for example in your away message. Reply to booking requests within the same day, and faster for same-day bookings. During service, an automatic away message with your booking link is better than silence.
Can we send offers to everyone who has messaged us?
Not without care. Treat WhatsApp broadcasts like marketing texts: get the guest's agreement first, make it easy to opt out, and keep a record of who agreed.
References
Department for Science, Innovation and Technology (2024). Public attitudes to data and AI: Tracker survey (Wave 4) report (opens in a new tab) ↑
Food Standards Agency (2025). Food and You 2 Annual Report: Wave 11 (2025) (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 5: principles relating to processing of personal data (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑