Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. How Do We Remember Our Restaurant Regulars' Favourite Table, Wine and Occasions When the Manager Who Knew Them Leaves?
Problems We Solve

How Do We Remember Our Restaurant Regulars' Favourite Table, Wine and Occasions When the Manager Who Knew Them Leaves?

Restaurant regulars' preferences live in one manager's memory. We build guest notes that surface favourite tables, wines and occasions when they book.

Updated 3 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Your best regulars expect you to remember them: the corner table, the Chablis they always order, the anniversary in May, the partner who does not eat shellfish. That knowledge lives in the head of one long-serving manager. We build guest notes that sit on each regular's booking record, are shown to the team when they book and arrive, and are added to by anyone who serves them.

A regular for ten years, and the new manager did not know

A couple who have eaten with you every few weeks for years book for Saturday. Your long-serving restaurant manager left last month. The new manager seats them at a table by the door, offers the wine list as if they were new, and does not mention their anniversary, which the old manager always marked with a glass of something at dessert.

They are polite about it. They notice. Regulars are loyal to places that know them, and the knowing is what went out of the door with the old manager.

Guest knowledge is personal, not recorded

Booking systems store bookings and, sometimes, basic guest notes. In practice, notes are sparse, inconsistent and rarely read, while the real knowledge sits in a few people's memories. It is shared by word of mouth at the pass or in the briefing, and it is lost when those people move on or are off for the night.

  • Guest notes in the booking system are blank or years out of date.
  • Preferences are learned at the table and never written down.
  • Regulars book under different names or phone numbers, so history is split.
  • The briefing mentions regulars only if the manager remembers.

A worked example: a regular books online using her work email, while her previous bookings were by phone under her husband's name. The booking system treats her as a new guest. Nobody links the two, so the note about her favourite table and the wine they always order is not shown for this booking.

What forgotten regulars cost

Regulars fill tables on quiet nights, recommend you to friends and forgive the odd off night. Treating them like strangers is one of the fastest ways to lose them, often quietly. When a key member of staff leaves, the restaurant can lose a part of its regular trade without anyone quite realising why.

It is also a missed chance on every visit: a favourite wine not offered, an occasion not marked, a dislike not remembered.

How we build guest notes the whole team can use

  1. Guest records from your reservations system are cleaned up and linked where the same person has booked under different names, emails or phone numbers, with a person confirming each match.
  2. Notes are structured into a few simple fields as well as free text: favourite table, usual drinks, occasions and dates, dislikes and dietary notes as told by the guest, and who they usually come with.
  3. When a regular books, their notes are attached to the booking and appear on the pre-service briefing and the table plan.
  4. Servers add what they learn on a tablet or phone during or after service, so knowledge builds up rather than living with one person.
  5. Upcoming occasions, such as an anniversary booking or a regular who has not visited for a while, are listed so you can decide whether to do something about it.
  6. Access to notes is limited to staff who need it, and guests' details are handled under your privacy policy.
What the team knowsBeforeWith guest notes
Favourite tableThe old manager knewOn the booking and table plan
Usual wineRemembered by one serverOn the guest record
AnniversaryMissed if nobody rememberedShown on the booking
Split guest historyDifferent recordsLinked, with a person confirming

What you record about guests, and how you tell them, follows your own privacy policy and advice. We build the notes to hold what you decide to keep.

Regulars recognised, whoever is on

The briefing tells the whole team which regulars are in tonight and what matters to them. New staff can look after a regular properly on their first week. When someone leaves, what they knew about your guests stays with the restaurant.

Over time you also see who your regulars actually are, how often they come, and who has not been in lately.

Signs your regulars are at risk

  • Knowledge of regulars sits with one or two staff.
  • Guest notes in your booking system are empty or out of date.
  • Regulars appear as new guests when they book a different way.
  • Occasions are marked only if someone remembers.
  • A key staff member leaving would take regulars' preferences with them.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Does our booking system already have guest notes?

Many do, such as SevenRooms, ResDiary and OpenTable. If yours does and the team will use it, we help clean and structure it rather than build something new.

How do you link a guest who books under different names?

By matching phone numbers, emails and names, with suggestions confirmed by a person. Nothing is merged automatically.

Is it appropriate to record guests' preferences?

Many restaurants do, and guests often appreciate being remembered. What you record and how you inform guests follows your privacy policy and advice.

What drives the cost?

Your booking system's integration, the state of your existing guest data and how notes are shown to staff.

What do you need from us?

Access to your booking system data, and time with the staff who know your regulars best.

Keep reading

More on Problems We Solve

Start here

Tell us what eats your restaurant's admin time

Describe how bookings, the rota, supplier invoices and the end of the night work in your restaurant now, and which booking, till and accounting systems you use. We will tell you what we would build and what we would leave alone, and if your booking system or till can already do it with a setting, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →