Recognising a regular without a secret list

Every restaurant has a manager who knows the regulars. She greets them by name, remembers their usual table and knows which one has a gluten allergy. Guests love her, and the restaurant depends on her. When she takes a fortnight's holiday, the regulars come in and are treated like everyone else. Some notice. A few do not come back as often.

In many venues, recognising a regular lives in a secret list: a manager's memory, a notebook behind the bar, a spreadsheet only one person updates. It works as long as that person is there. A venue that recognises its regulars well makes recognition a system the whole team can use, so every regular is known whoever is working.

This guide covers why recognition matters, why it should not depend on one person, how to build a system the team will use, what recognition should actually look like and how to handle VIP bookings and guests who prefer to stay anonymous. Every venue and figure in it is an example.

Regulars come back because they feel known, and recognition is one of the strongest parts of a guest's customer experience. Being greeted by name, seated at a favourite table and asked whether it will be "the usual" makes a guest feel that the venue is partly theirs. It is one of the most powerful reasons people choose one restaurant over another.

Recognition also builds the relationship. A regular who feels recognised forgives a slow evening, recommends the venue to friends and keeps coming as the menu changes. Our guide to regulars: how a venue makes them on purpose covers the wider picture.

A secret list fails because it depends on one person. When that person is off, busy or leaves, recognition stops. Regulars notice immediately, and they feel it as a change in how the venue values them.

It also fails because it cannot scale. One manager can remember perhaps fifty regulars well. A busy venue may have hundreds. And a secret list is rarely updated: the regular who has moved away stays on it, while the new regular who has come every week for three months is not yet on it.

Recognition as a system means recording who your regulars are, and what they like, in a place the whole team can see: the guest's profile, linked to their bookings. When a regular books, the host can see that they are a regular, how often they visit and what they prefer.

That record must be easy to read at the moment it is needed: on the booking, at the host stand, before the guest sits down. A profile nobody opens is no better than a secret list.

Decide what makes someone a regular, so the system can find them. It might be a number of visits in a period, such as six visits in six months, or a level of spend, or both. Many venues use a few levels: regulars, then the best regulars, then the guests who are part of the venue's story.

Whatever you choose, apply it consistently, and let the system keep it current as guests come and go, so a regular who stops coming is not treated as one forever.

Recognition depends on guest profiles the team trusts. If profiles are full of duplicates, out-of-date notes or missing information, the team stops looking at them. Keep them accurate: merge duplicates, update preferences and remove notes that are no longer true.

Our guide to guest profiles your floor team will trust covers what makes a profile reliable.

Record what helps the team recognise and look after each regular: their name, how they like to be addressed, their usual table or area, their usual drink or dish, any allergies or dietary needs, occasions they celebrate and anything that makes their visit better.

Keep it useful and respectful. Our guide to guest preferences worth writing down covers which preferences matter, and the simple test for any note: would the guest be comfortable reading it?

Remembering names is the heart of recognition, and it can be learned. Use the guest's name when they arrive, if you know it from the booking. Repeat it once naturally in conversation. Write down anything that helps you remember, such as where they usually sit or what they usually order.

Do not pretend. A server who guesses a name wrongly, or greets a stranger as a regular, does more harm than one who simply says "welcome back". When unsure, a warm welcome without a name is better than a wrong one.

The host stand is where recognition starts, because it is the first moment the guest meets the venue. A host who can see, as the guest arrives, that this is a regular with six visits this year, a favourite window table and a shellfish allergy can welcome them properly.

Before service, the host should look through the evening's bookings and note the regulars, the guests returning after a long gap and any occasions. Five minutes of preparation turns the evening's arrivals into a series of recognitions.

Share the evening's regulars at the pre-shift briefing: who is coming, what they like, any occasion and anything that went wrong on their last visit. Every server who might look after them should know.

Our guide to the pre-shift briefing, in five minutes covers what belongs in it. Naming the regulars takes a minute and lets the whole team recognise them.

Recognition should feel natural, warm and discreet. A greeting by name. "Your usual table is ready." "Would you like the Rioja you had last time?" A word from the chef about a dish they love. A small gesture on a birthday.

It should not feel like a script or a show. Guests notice when recognition is mechanical, and they notice when it is overdone. A sincere welcome, and remembering what they like, matters more than any gimmick.

Recognition must be discreet. Do not announce a regular's history in front of their companions: "Lovely to see you again, you were here with your sister last week" may be unwelcome. Do not mention how much they usually spend. Do not reveal their allergy to the table unless they have shared it.

Some regulars come with business contacts, first dates or family members who do not know how often they visit. Recognise them warmly, but let them decide how much of their history to share.

Some guests deserve particular attention: very regular guests, guests celebrating important occasions, local figures, critics, guests who have had a problem before. VIP bookings should be marked so the team knows, without a separate spreadsheet that only the manager can see.

Mark the booking or the guest's profile, note what makes the visit special and brief the team. A VIP booking handled with care is a guest who comes back and tells others; one handled like any other may not.

Not every guest wants to be recognised. Some prefer to come quietly, without fuss, and would find a greeting by name uncomfortable. Respect that: note it on their profile if they say so, and let them enjoy their visit as they wish.

Recognition is for the guest's benefit. If a guest would rather not be recognised, the respectful thing is to recognise that.

Regulars change. A guest who came weekly last year may come monthly now; a new guest may be becoming a regular. Let the system keep tiers and visit counts current, and look each month at who has joined the regulars and who has drifted away.

A regular who has drifted away is worth a personal note, if they have agreed to hear from you. Our guide to guest history: what the last four visits tell you covers reading the signs.

In a group, a regular at one venue may visit another for the first time. Recognising them there as a valued guest, rather than a stranger, extends the relationship across the group. A guest profile shared across venues makes that possible.

Agree across the group how recognition works, so a guest who is a regular at one venue is welcomed warmly at the others, without the new team pretending to know them better than they do.

Measure whether recognition is working: how many regulars return, how often, and whether regulars who are recognised come back more than those who are not. Look at feedback for comments like "they remembered me" or "it felt like coming home".

Look at the other side too: complaints from regulars who felt treated like strangers, or regulars who stopped coming after a change in staff. Those are signs that recognition still depends on a few people.

The bar is often where regulars feel most at home. A bartender who knows a regular's drink, starts making it as they walk in and remembers what they talked about last time creates a powerful sense of belonging.

Bring the bar into the system. A regular's usual drink, recorded on their profile, lets any bartender greet them as well as the one who knows them best.

Regulars often book by phone, and the call is a moment for recognition too. A host who recognises the number and says "Lovely to hear from you, the usual table on Friday?" makes the guest feel known before they arrive.

Looking the guest up by name while still on the call lets whoever answers greet them this way, not only the person who knows them best.

Not every regular books. Some walk in, especially in cafés and bars. Recognising them depends on the team knowing their faces and names, which is harder without a booking.

Take a name when a walk-in becomes familiar, with their agreement, so they can be recorded and recognised. A regular who walks in and is greeted by name feels as valued as one who booked.

On a busy night, recognition can slip: the host is rushed, the server has too many tables. That is exactly when regulars notice if they are treated like strangers.

Keep recognition simple enough to survive a busy night: a warm greeting by name, their usual table if it is free, their usual drink offered. Even a brief recognition on a busy night means a great deal.

A regular who had a problem on their last visit needs particular recognition on the next one: a word from the manager, an acknowledgement of what went wrong, a sign that it has been fixed.

Note problems on the guest's profile, so the team knows when the regular returns. Recognising a regular's bad experience, and putting it right, often deepens their loyalty.

New staff do not know the regulars, which is why the system matters most for them. Show new staff how to read a guest's profile before greeting them, and introduce them to regulars when it feels natural.

A new server who greets a regular by name on their first week, because they read the booking, makes a strong impression on both the guest and the team.

The kitchen can recognise regulars too: a regular's favourite dish prepared with extra care, a chef who comes out to say hello, a small taste of something new. These touches are remembered far longer than a free dessert.

Share the evening's regulars with the kitchen at the briefing, so the chef can decide where a personal touch would be welcome.

As a guest moves from new to regular to one of the venue's best guests, recognition can grow too: from a warm welcome, to their usual table, to invitations to events and a personal note on their birthday.

Let the system's tiers guide this, so recognition matches how much the guest means to the venue, and nobody is forgotten as they move up.

In the end, recognition is a habit, built by the whole team over time. A system helps, but it is the team's daily practice of greeting, remembering and noticing that makes regulars feel at home.

Make it part of training, the briefing and the standards, and recognise the staff who do it well.

Over the years, some regulars become friends of the people who serve them. That is one of the joys of hospitality, and part of why regulars stay. It also needs a little care.

Friendship should not turn into favouritism the rest of the room notices: a regular's table served first while others wait, free drinks that were never agreed, long conversations at the bar while other guests try to order. Other guests should see warmth, not a private club.

Keep generosity within the venue's policy, so a gesture to a regular is the venue's choice, recorded like any other. And make sure the regular is recognised by the whole team, not only their friend, so their welcome does not disappear on their friend's night off.

Many regulars are loyal to a person as much as to a place: the server who knows their order, the bartender who remembers their name. When that person leaves, the regular may drift away too, unless the venue carries the relationship on.

Before someone leaves, ask them to share what they know about the regulars they look after: names, usual orders, family members, preferences, the table they like. Record it on the guests' profiles, and introduce the regulars to whoever will look after them next.

Tell regulars, where it is natural, that their favourite server is moving on. A regular who hears it from the team, and is then welcomed by name by someone new, knows the venue still remembers them.

Recognition usually focuses on the welcome, but the goodbye matters as much. It is the last thing the guest experiences, and often what they remember most about the visit.

Thank regulars by name as they leave, help with coats, hold the door and, where it is true, say you look forward to seeing them next time. A host or manager who stops what they are doing to say goodbye to a regular sends a strong message to the guest and to the team.

A rushed goodbye, a bill that takes twenty minutes or a team too busy to notice the guest leaving can undo a good evening. Make the goodbye part of the standard, so it happens on busy nights too.

Many regulars are regular at one time of day: the evening crowd, the weekday lunch, the early coffee. When an evening regular comes in for breakfast, the morning team may not know them at all, and a guest who is greeted by name every week at dinner is treated as a stranger at breakfast.

Share recognition across shifts. Notes on the guest's profile, read by whoever is on, and a mention at each shift's briefing when a familiar name is booked, let the whole team know a regular when they see one.

A regular who is recognised whatever time they come in learns that the venue knows them, not just the one shift that happens to.

An invented brasserie relies on one long-serving manager to recognise its regulars. When she moves to another venue, regulars complain that the brasserie "isn't the same".

The brasserie starts recording regulars on their guest profiles: visit counts, favourite tables, usual drinks, allergies and occasions, kept current automatically as guests visit. The host reviews the evening's regulars before service and names them at the briefing. Servers are taught to greet regulars warmly, and by name where they are confident of it.

Within a few months, the complaints stop. A regular tells the new manager that the welcome feels as warm as it always did, and nobody on the team needs a secret list.

In servearound, guest profiles fill themselves from bookings, orders and checks, and guest tiers, new, regular, VIP and VVIP, are worked out from visits and spend over a window each venue sets, kept current as guests come and go, with a tier set by hand never overwritten. Taking a booking by phone number finds the returning guest, and the booking shows their visit count, last visit, notes, preferences and allergens, so whoever is on the host stand can welcome them back.

Tables can be marked VIP, and notes on the booking tell the team what makes the visit special. Guest analytics show the best guests at each venue, the tier mix and how many guests came back. See the guests module and the reservations module.

Regulars come back because they feel known, and recognition builds the relationship.

Because recognition stops when that person is off, busy or leaves, and memory cannot scale.

Name, how they like to be addressed, usual table, usual order, allergies, occasions and anything that makes their visit better.

Use the name from the booking, repeat it once naturally and never guess. A warm welcome is better than a wrong name.

At the host stand, with the evening's bookings reviewed before service.

Warm, natural and discreet: a greeting by name, their usual table, their usual drink.

Marked on the booking or profile, with the reason noted and the team briefed.

Respect it, note it on their profile and let them visit quietly.

Recognising a regular should not depend on a secret list in one manager's head. Make it a system: record who your regulars are and what they like on their guest profiles, keep it current automatically, and make it visible on the booking at the host stand.

Review the evening's regulars before service and name them at the briefing, greet them warmly and by name only when you are sure, keep recognition discreet, mark VIP bookings properly, respect guests who prefer anonymity and measure whether regulars keep coming back.