Key takeaways
- Booking data already holds visit counts, usual tables and party patterns. A short guest profile turns that into a warm welcome.
- Recognition works when it is light: a name, a usual drink, a preferred table. Reciting someone’s history feels like surveillance.
- Thank-you messages that promote anything are marketing and need consent or a valid soft opt-in under PECR[1].
- Guest data is a target: 30% of food and hospitality businesses identified a cyber breach or attack in a year[2].
What recognition looks like at the table
Regulars are the guests who keep a quiet Tuesday afloat and fill the diary when the weather turns. Most of them do not want a loyalty card. They want to be remembered: greeted by name, offered their usual table, asked whether it is the usual gin. Good hosts used to carry that in their heads. Staff turnover and multiple sites mean it now needs to live in the booking system.
Spending on eating out is still there to compete for. Restaurants and hotels were among the household spending categories with the largest increases in the financial year ending 2025, up £2.80 a week, or 6%[3]. Regulars are the most reliable share of that spend, and the cheapest to keep.
What booking data can tell you
| Data point | What it reveals | How staff use it |
|---|---|---|
| Visit count, last 12 months | Who is a regular and who is new | Different welcome for first and fifth visits |
| Usual day and time | Habits, such as every other Friday at 19.00 | Hold their usual slot when the diary fills |
| Usual table or area | Preferences they may never have stated | Offer it before they ask |
| Party size pattern | Couple, family, business lunches | Suggest the right table or room |
| Occasion history | Birthdays and anniversaries booked before | A card or a mention, if they welcome it |
| Notes from past visits | Drink order, name they prefer, past issues | A one-line briefing for the server |
Most booking systems build this automatically when guests book with the same phone number or email. The data is only useful if it is clean, so merge duplicate profiles when you spot them and make sure walk-ins who become regulars get a profile too.
Deciding who counts as a regular
A clear rule stops recognition from being random. Pick thresholds that suit your trade and apply them the same way across the team. Example tiers for a neighbourhood restaurant:
- New: first visit, or first in more than a year. Welcome them and ask how they heard of you.
- Returning: two or three visits in 12 months. Thank them for coming back.
- Regular: four or more visits in 12 months. Greet by name, offer the usual table, brief the server.
- Friend of the house: monthly or more, or a long history. The manager says hello in person.
Review the thresholds after a quarter. If half the diary qualifies as “regular”, the bar is too low to mean anything; if nobody does, raise the profile of returning guests instead.
Using it without being intrusive
The line between warm and creepy is about what you say out loud. Guests like being known; they do not like being reminded that a database knows them. Use the data to shape what you do, and say less than you know.
| Say | Avoid | Why |
|---|---|---|
| “Lovely to see you again.” | “This is your 14th visit this year.” | Recognition, not a statement of record |
| “Your usual table is ready.” | “You always sit here and order the lamb.” | Offer, do not predict |
| “Happy birthday, we hope it’s a good one.” | Mentioning a birthday they booked last year but not this year | Only use what this booking tells you |
| “Same again?” when they look at the drinks list | Bringing the usual drink unasked to a business guest | Let them choose in front of others |
Be careful with notes about who a guest dines with. A profile that shows someone books for two most Fridays should not lead a server to ask after “your wife” when they arrive with someone else. Use names only when the guest has given them on this booking.
Data protection in plain terms
Guest profiles are personal data, so UK data protection law applies. Keep the profile to what helps you serve the guest, tell guests in your privacy notice that you keep visit history and preferences, and delete profiles that have not been used for a long period you set in advance. Allergy and access notes are health information and need extra care; keep them only with the guest’s agreement and never use them for marketing.
Marketing has its own rules. Direct marketing means the communication of advertising or marketing material directed to particular individuals[4], and marketing emails and texts need prior consent under PECR[1]. The soft opt-in lets you market your own similar products to people whose details you obtained during a sale or negotiation[1], as long as they had a simple chance to refuse when you collected the details and in every message since. A booking where the guest paid a deposit or dined with you can meet that test; a guest who only browsed your menu has not.
Security matters as much as consent. In the government’s 2025 cyber survey, 30% of food or hospitality businesses identified a breach or attack in the previous 12 months, against 43% of businesses overall[2], and only 12% had a board member responsible for cyber security[2].
Source: Department for Science, Innovation and Technology, 2025[2]
Show the data
| Item | Value |
|---|---|
| Food or hospitality | 30% |
| All businesses | 43% |
- Give each staff member their own login and remove leavers on their last day.
- Turn on two-step sign-in for the booking system and email.
- Limit who can export guest lists, and log exports.
- Never keep guest data in personal phones or spreadsheets on shared laptops.
Thank-you messages that stay on the right side of PECR
A message that only thanks a guest for visiting, with no offer and no promotion, is closer to service than marketing. The moment it includes a discount, a new menu launch or an invitation to book again, it is marketing. Send those only to guests who opted in or who fall under the soft opt-in and have not said no. Keep the opt-out link in every one.
Recognition rarely needs a message at all. The most effective loyalty tool most venues have is a host who remembers a name.
Spotting regulars who have drifted away
Visit history also shows you who has stopped coming. A guest who booked every month for a year and has not been back for three is worth a look, because something may have gone wrong on the last visit, or a new competitor may have opened. Run a simple report each month: guests with four or more visits in the previous year and none in the last 90 days.
- Check the notes from their last visit for an issue, a complaint or a long wait.
- If there was a problem, the manager can call or write personally, without an offer attached, to ask how it went.
- If they are opted in to marketing, include them in the next newsletter as normal; do not single them out with a “we miss you” discount that trains guests to drift.
- If nothing stands out, leave it. People move house, change jobs and have babies.
The point is to learn, not to chase. A pattern of drifting regulars after a menu change or a new rota tells you more than any survey.
What to record after service
Profiles go stale unless someone updates them. Make it part of the close-down routine for the shift lead, taking five minutes at most.
- Any new preference the guest mentioned, such as a favourite table, a drink or how they like to be addressed.
- Any issue and how it was resolved, tagged so the next host knows.
- Occasions the guest shared, only if they would welcome it being remembered.
- Corrections: wrong names, merged profiles, out-of-date numbers.
Groups with several sites should agree whether profiles are shared across venues, and say so in the privacy notice. A guest who is a regular in one branch may enjoy being recognised in another, but it should not come as a surprise.
Example: a neighbourhood bistro sets it up
Example. A fictional 45-cover bistro realises its regulars are being treated like strangers on the nights the owner is off. It sets four visit tiers, adds a one-line “usual” field to guest profiles (preferred table, drink, name they use) and prints a short list of regulars booked for the evening at the 4pm briefing. Servers are asked to use only what is on the list.
Within a few weeks, the evening team greets regulars by name even when the owner is away. The bistro also notices that several regulars book the same Friday slot every fortnight, so it holds that table until 48 hours before. It deletes profiles with no visit for two years, as its privacy notice says it will.
Setting it up in a month
Week 1: clean the data
Merge duplicate profiles, fix misspelt names and make sure phone numbers are stored in one format.
Week 2: agree the tiers
Set your visit thresholds and decide what each tier gets, from a warm hello to a manager’s visit.
Week 3: add the usual field
Create a short, factual field for preferences and train staff to update it after service.
Week 4: brief and review
Add regulars to the pre-shift briefing, then ask the team which notes helped and which they ignored.
Frequently asked questions
How can a restaurant recognise regular customers?
Use the visit history in your booking system to build short guest profiles with visit count, usual table and preferences. Set clear tiers for who counts as a regular and brief the team on regulars booked for each service.
Is it legal to keep guest preferences in a booking system?
Yes, if you tell guests in your privacy notice, keep only what helps you serve them, protect the data and delete it after a set period. Allergy and access notes need extra care and the guest’s agreement.
Can we email regulars with offers?
Only with prior consent or a valid soft opt-in for your own similar products, with an easy opt-out in every message[1].
How do we avoid being creepy with guest data?
Use the data to shape what you do, not what you say. Greet by name and offer the usual table, but do not recite visit counts or past orders.
References
legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Office for National Statistics (2025). Family spending in the UK: financial year ending 2025 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2018). Data Protection Act 2018, section 122: direct marketing (definition) (opens in a new tab) ↑