Guest profiles your floor team will trust

Guest profiles are the records a venue keeps about each guest: who they are, how often they visit, what they like, what they cannot eat and what the team has noticed. In theory, they let any host greet a regular by name, any server remember a preference, and any manager spot a guest who has stopped coming. In practice, many profiles are ignored, because the floor team has learned that they cannot be trusted.

Trust is everything. A host has a few seconds at the door to glance at a profile before greeting a guest. If the profile is cluttered, out of date or wrong, the host stops looking. Once the team stops looking, the profile becomes a record nobody reads, however much data it holds. Recognising a regular depends less on how much a venue knows than on whether the team believes what it reads.

This guide sets out how to build guest profiles your floor team will trust: what to show at the door in four seconds, what to keep in the full record, how guest history and guest tags should work, and the two kinds of field that most often make staff stop believing a profile. It also covers who should update profiles, how to keep them current and how to use them during service.

A guest profile has one main job during service: to help the team treat each guest as an individual. That means greeting them by name, seating them where they like, knowing their allergies, remembering what they enjoyed, and avoiding what went wrong last time. Every part of a profile should help with that job, or with understanding guests more broadly afterwards.

Profiles also support the rest of the venue. Managers use them to see who the regulars are, who is lapsing and how guests responded to changes. Marketing uses them, with consent, to write to the right guests. But the floor team is the audience that matters most, because they use profiles in real time, with real guests in front of them.

Design profiles for the floor first. If a host can use a profile in four seconds at the door, the rest of the venue will find it useful too. The broader discipline of customer relationship management covers much more than profiles, but in a restaurant it starts here: one accurate record per guest, used at the moment it matters.

At the door, a host needs to know a few things at a glance: who this guest is, whether they are a regular, any allergy or dietary need, and anything important about this visit or the last one. That is the four-second view, and it should fit on one small panel.

A good four-second view shows the guest's name, a simple indication of how often they visit, any allergy in a way that cannot be missed, and one or two short, current notes, such as "prefers a booth" or "celebrating an anniversary tonight". It might show when they last visited.

Everything else, such as full visit history, spend, feedback and older notes, belongs in the full profile, a tap away. Mixing the two makes the four-second view unreadable.

The full profile holds the rest of the guest data: contact details, visit history, spend, preferences, feedback, notes over time and marketing consent. It is where a manager looks before a special booking, where a host checks the details of a large party, and where the team learns more about a guest they are about to meet.

Organise it so the most useful information is at the top. Allergies and dietary needs first, then current preferences, recent visits, recent notes and feedback. Older history and administrative details can sit lower down.

Keep the full profile honest. It should reflect what the guest has shared and what the venue has observed, factually and kindly. Our guide to guest data covers what to collect and what to leave.

Guest history is the record of each visit: the date, the party size, the table, what was ordered, what was spent and, where available, how the guest felt about it. It is the most reliable part of a profile, because it is recorded by the service itself rather than written by hand.

History lets the team see patterns: the guest who always books for two on a Friday, who always orders the same starter, who celebrates in June. It shows who the regulars are without anyone having to remember. And it shows when a guest has stopped coming.

For history to be trustworthy, bookings, orders and bills must be connected to the same profile. A history that misses visits, because they were booked under a different name or paid separately, gives a false picture.

Recognising a regular is one of the most valued things a venue can do. A guest who is greeted by name, offered their usual table and asked whether they would like their usual drink feels at home. Regulars notice when this happens, and they notice when it does not.

Profiles make recognition possible even when the person who knows the guest is not working. A new host can greet a regular of ten years by name, because the profile tells them who is arriving. That consistency is what turns personal relationships into the venue's relationship.

Use recognition naturally. A warm "welcome back" and a remembered preference feel generous. Reciting a guest's entire history at the door feels like surveillance.

Guest tags are short labels attached to a profile: a tier such as regular or VIP, a dietary need, a preference, an occasion. Used well, they make the four-second view quicker to read. A host seeing "regular, vegetarian, prefers window" knows a lot in a moment.

Keep tags few, consistent and meaningful. A venue with fifty tags, many of them overlapping or out of date, has replaced one kind of clutter with another. Agree a small set, define what each means, and apply them the same way every time.

Make sure tags are current. A tag that says "VIP" for a guest who has not visited in three years, or "pregnant" from a visit long ago, damages trust in every other tag.

Two kinds of field, more than any others, make staff stop believing guest profiles.

The first is the stale note. "Always sits at table 12" when table 12 was removed in the refit. "Prefers the old house red" when it left the list a year ago. "Celebrating engagement" from three years ago, read out as if it were tonight. A host who acts on a stale note and gets it wrong in front of the guest will not trust the next note they read.

The second is the inflated flag. When every second guest is marked VIP, the flag means nothing. When a guest is marked as a regular after two visits, the team learns to ignore the label. Flags that are applied too generously, or never removed, stop carrying information.

Both have the same fix: date every note, review notes regularly, base tiers on clear rules rather than enthusiasm, and remove what is no longer true.

An allergy on a guest profile is the most important field of all, and the one that must never be wrong. Record it once, clearly, and make sure it appears wherever the guest is served: on the booking, on the table during service and on the kitchen ticket.

Always confirm allergies at the table. A profile is a prompt for the conversation, not a replacement for it. A guest's needs may have changed, and a profile cannot know that. Our guide to allergy notes covers where an allergy must appear between booking and the pass.

If an allergy on a profile turns out to be wrong, correct it immediately and tell the team. An allergy field that cannot be trusted is dangerous.

Notes written by the team are what make profiles personal. "Prefers a quiet table, away from the door." "Always orders the lamb; ask about the special." "Uses a wheelchair; seat at the accessible table." Notes like these turn a record into hospitality.

Keep notes short, factual and kind. Write them as though the guest might read them, because under privacy rules they may have the right to. Avoid comments about appearance, character or behaviour that would embarrass the guest or the venue.

Date and sign every note. A note with a date tells the reader how current it is; a note with an author tells them whom to ask.

Profiles drift out of date unless someone keeps them current. Build small habits into the service. After a visit, the server adds any new preference they noticed. When a guest mentions a change, such as a new allergy or a move away, the host updates the profile. Once a month, a manager reviews notes on the most frequent guests and removes anything stale.

Duplicate profiles undermine everything. When the same guest has three profiles, each with part of their history and a different note, nobody knows which to believe. Merge duplicates regularly, keeping the most accurate details.

The goal is not a perfect database; it is a set of profiles the team can rely on during service.

Decide who can change what. Hosts and servers usually add notes and preferences. Managers review and correct notes, adjust tiers and merge duplicates. Allergy records may need a confirmation step, because they matter so much.

Make updating easy. If adding a note takes six taps and a separate screen, nobody will do it during service. A quick note added at the host stand or from a handheld, in a few seconds, is far more likely to happen.

Train the team on what makes a good note and what does not. A few examples, good and bad, are more useful than a long policy.

During service, profiles should appear where the team already looks: on the booking list at the host stand, on the table when a guest is seated, and on the order when it is taken. A profile that lives in a separate system, opened only if someone remembers, is rarely used.

Brief the team on notable guests before service. A short mention at the pre-service briefing, such as "two regulars in tonight, one with a shellfish allergy, one celebrating a birthday", prepares everyone.

After service, capture what was learned. A preference noticed, an occasion mentioned, a problem resolved: each one improves the next visit.

The booking is the first moment a profile can help. When a guest calls, the person answering can find their profile from their phone number, greet them as a returning guest, check that their allergy is still current and note anything new about this visit. When a guest books online, the booking can attach to their existing profile rather than creating a new one.

That conversation is also where profiles are kept accurate. A quick "is it still just the shellfish allergy?" confirms the record. A mention of a birthday or a new baby can be noted. A guest who has moved and has a new number can be updated, so the next booking finds them.

Train whoever takes bookings to use the profile naturally, without reading it back to the guest. The aim is to make the guest feel known, not watched.

Every regular started as a first-time guest with an empty profile. Treat first visits as the start of a record, not a gap. Capture what the guest shares at booking, note anything the team learns during the visit, such as a preferred table or a favourite dish, and make sure the visit and its spend are attached to the profile.

Do not try to fill a profile in one go. A first-time guest asked many questions at the door feels interrogated. A few details gathered naturally, and added to over later visits, build a profile the guest never notices being built.

The second visit is where profiles prove their worth. A guest who returns and finds that the team remembers something from their first visit is far more likely to come a third time.

Some venues add a photograph to the profiles of frequent guests, so hosts can recognise them as they arrive. It can be genuinely useful in a busy venue with a changing team, but it needs care. Only add a photograph with the guest's knowledge and agreement, store it securely, and show it only to the people who need it.

Many guests are happy to be recognised; some are not. If a guest prefers not to have a photograph on file, respect that without question. A warm welcome by name works just as well.

Profiles hold personal information, and guests trust the venue to use it carefully. Only collect what you will use, store it securely, show each part only to the people who need it, and keep it only as long as it is useful. Spend and full history, for example, may be for managers rather than every server.

Be transparent. Explain in your privacy notice what you keep and why. If a guest asks what you hold about them, you should be able to show them, and the profile should contain nothing you would be uncomfortable showing.

Never use sensitive information, such as allergies, for anything other than keeping the guest safe.

In a group, a guest may visit several venues. One profile across the group means a regular at one venue can be recognised at another, and their allergies are known everywhere. That is a real advantage for service.

Make sure notes are relevant across venues, or clearly labelled with the venue they apply to. "Prefers table 12" means something at one venue and nothing at another. Agree who in the group can see what, and be clear with guests that their profile is shared across the group.

Here is an illustrative venue that rebuilt trust in its guest profiles. The details are examples.

In servearound, guest profiles fill themselves from bookings, orders and checks: visits, spend, the last visit and every visit with its date, party, table, orders and what was spent and paid. Allergies, dietary needs, drinks and dining preferences such as a preferred zone and time are saved to the guest, and allergies show as a flag on the booking list, on the table and on the kitchen ticket. Notes carry their author and date, and the profile keeps a photo and a birthday.

Tiers, new, regular, VIP and VVIP, are worked out from visits and spend over a window you set and kept current as guests come and go, and a tier set by hand stays where you put it. Possible duplicates are flagged with how confident the match is, such as the same phone number, and merging moves the history across. See the guests module.

The guest's name, how often they visit, any allergy and one or two current notes. Everything else a tap away.

Monthly for frequent guests, and whenever a note turns out to be wrong.

Clear rules based on visits and spend, with a manager able to make exceptions. Not individual enthusiasm.

Usually not. Spend is useful to managers; servers need preferences, allergies and notes.

Match returning guests by phone or email when they book, and merge the duplicates that slip through regularly.

Accuracy. A profile that is right every time is read every time.

Yes. Explain it in your privacy notice, and be ready to show guests what you hold if they ask. A profile you would be happy for the guest to read is a good profile.

Guest profiles only help if the floor team trusts them. Give hosts a four-second view at the door: name, how often the guest visits, allergies and current notes. Keep guest history, spend and older notes in the full profile, built from the service itself so it is accurate.

Use a small, consistent set of guest tags, date and sign every note, review notes regularly, and avoid the two kinds of field that destroy trust: stale notes and inflated flags. Show allergies wherever the guest is served, merge duplicates, respect guest privacy, and recognising a regular becomes something every member of the team can do.