Guest history: what the last four visits tell you

A guest's profile shows four visits in the past year. In March, a table for two on a Friday, with a bottle of wine. In May, a table for six on a Saturday, a birthday. In August, a table for two, no wine, a short visit. In October, a table for two on a Friday again, a dessert left untouched, a feedback rating of "okay". A server glancing at it sees four dinners. A manager reading it sees a regular whose visits are getting shorter and whose last one did not go well.

Guest history is one of the most useful things a venue knows, and one of the most often ignored. Most profiles hold far more than anyone reads: dates, party sizes, tables, orders, spend, feedback. Read for patterns rather than trivia, the last few visits tell you who a guest is, how they feel about you and what might bring them back.

This guide covers how to read a guest's history, what visit frequency and spend reveal, the warning signs worth noticing and the three facts from a history that are worth mentioning to the guest. Every venue and figure in it is an example.

A guest history is the record of every visit a guest has made: when they came, how many were in the party, where they sat, what they ordered, what they spent, how they paid and anything the team or the guest said about it. Together with their preferences and notes, it forms the guest's profile.

Most venues with a booking system and a till already collect this, often without realising how much it says. The question is not whether the history exists, but whether anyone reads it.

The trick is to read a history for patterns rather than details. A single visit tells you little. Four visits, read together, show how often the guest comes, whether that is rising or falling, who they come with, what they like and whether their experience is getting better or worse.

Ask three questions of any history: how often do they come, and is it changing? What do they usually do? And how did the last visit go? Those three answers tell you most of what matters.

Visit frequency is how often a guest comes. A guest who visits every fortnight is a regular; one who visits twice a year is an occasional guest; one who came once three years ago is a former guest.

The pattern matters more than the number. A regular whose visits have stretched from every fortnight to every two months is drifting away. A guest who used to come twice a year and now comes monthly is becoming a regular. Both deserve attention, for opposite reasons.

The gap since a guest's last visit, compared with their usual gap, is one of the clearest signals in a history. A guest who usually comes every month and has not been for three is a guest who may be lost.

That is the moment to reach out, if the guest has agreed to hear from you: a short, personal message, perhaps mentioning something they enjoyed. Our guide to lapsed guests: the message that brings them back covers how.

The size and shape of the party tells you how a guest uses the venue. A guest who comes as a couple on Fridays is using it for date nights; one who books for six on Saturdays is using it for celebrations; one who comes alone at lunch is using it as a regular refuge.

That changes how to look after them. The couple might like a quiet table; the celebrators a bigger one and a candle on the dessert; the solo lunch guest a seat at the bar and a newspaper.

Order history shows what a guest likes: their usual dish, their usual wine, whether they have dessert, whether they share. It lets a server offer "the usual?" and lets the kitchen know when a regular's favourite dish is coming off the menu.

It can also show change. A guest who always ordered wine and has stopped may have a reason worth knowing, gently, or may simply be driving. A guest who always had dessert and has stopped may have been disappointed by the last one.

Spend per visit, and guest lifetime spend across all visits, show how much a guest is worth to the venue. A regular who visits monthly and spends a moderate amount each time may be worth far more over a year than a guest who spent heavily once.

The idea behind customer lifetime value is simple: a guest's value is not one bill but all the bills they will bring over the years. Treat the regulars who bring the most over time as the guests they are.

The last visit matters most, because it shapes whether the guest comes back. Look at what the team noted, whether there was a complaint or a remake, and any feedback the guest gave.

A regular whose last visit went badly is at risk. A short, sincere message, or a word from the manager on their next visit, can repair it. Ignoring it can lose a guest who has been coming for years.

The days and times a guest visits tell you how they use the venue. A guest who always comes on Friday evenings is a weekend guest; one who comes on Tuesday lunchtimes may work nearby. A guest whose visits cluster around certain months may be a seasonal visitor or someone who celebrates there each year.

That helps with planning as well as service. A regular who always comes on the first Friday of the month can be expected, and their usual table kept free. A guest who visits every summer can be welcomed back warmly when the season starts.

It also helps with messages. A weekday lunch guest is unlikely to be tempted by a Saturday tasting evening, but might welcome news of a new lunch menu.

A few patterns are warning signs. Visits that are getting further apart. Spend that is falling. A complaint or a low feedback rating on a recent visit. A regular who used to bring friends and now comes alone, or not at all. Bookings that are made and then cancelled.

None of these proves anything on its own. Together, they suggest a guest whose relationship with the venue is weakening, and who might be won back with a little attention.

Good signs deserve notice too. A guest whose visits are getting closer together, whose parties are growing because they bring friends, whose feedback is warm and whose spend is steady or rising is becoming a regular.

Notice them and thank them. A regular in the making who is recognised and welcomed is far more likely to become a regular for years.

Feedback a guest has given sits alongside their visits, and it is worth reading together with them. A guest who rated their last visit poorly and has not been back since is a guest at risk. One who rated every visit highly is a guest who might be happy to leave a public review, or to bring friends.

Read the comments as well as the ratings. A guest who praised a particular dish can be told when it returns to the menu; one who complained about noise can be offered a quieter table next time.

Feedback in the history turns a guest's past opinions into a guide for their next visit.

Not everything in a history should be mentioned to the guest. Three kinds of fact usually are: that you remember them ("lovely to see you again"), what they like ("your usual table by the window?") and anything you have changed because of them ("we took your advice and changed the dessert").

Each makes the guest feel known and valued. Each uses only what the guest would expect you to know.

Other facts should stay in the history. Mentioning how much a guest spent, who they came with last time, how often they cancel or anything they might not want their companions to hear can feel intrusive, even when it is meant kindly.

The test is whether the guest would be comfortable hearing it in front of the people they are with. "Your usual Rioja?" passes; "Last time you were here with someone else" does not.

The host benefits from guest history as much as anyone. Before service, the host can look at the evening's bookings and note the regulars, the guests returning after a long gap, the guests whose last visit went badly and the guests celebrating something.

That short look lets the host greet each one appropriately: a warm welcome back for the regular, a word of reassurance for the guest whose last visit was disappointing, a congratulation for the birthday. It also lets the host plan the seating so each guest gets the table that suits them.

Five minutes with the evening's histories before the doors open can change how a dozen guests feel about their visit.

Guest history is the foundation of personalisation that feels natural. A server who knows from the history that a guest always orders the lamb can mention that it is on the specials tonight. A host who knows a guest celebrates their anniversary every October can offer their favourite table when they book.

Done well, it feels like being remembered by a friend. Done badly, using details the guest never shared or mentioning them too often, it feels like being watched.

Histories are only useful if the team reads them. Make it part of the routine: the host looks at the evening's bookings and notes regulars, recent complaints and occasions; the server glances at a table's history before greeting it.

Keep the profile easy to read, with the most useful facts at the top: allergies, preferences, the number of visits, the last visit and any recent note. Our guide to guest profiles your floor team will trust covers how.

In a group, a guest may visit more than one venue. A history that shows all their visits, across every venue, gives a fuller picture: a guest who is a regular at one site and new at another can be welcomed as a valued guest at both.

Agree with each venue how cross-venue history is used, and make sure it respects the guest's privacy and any consent they gave.

A guest who books for large groups has a history that tells a different story: the size of their parties, the occasions they celebrate, the set menus they choose and how much each group spends. These guests can be among a venue's most valuable, even if they rarely visit on their own.

Recognise them as the organisers they are. Remember what their last group chose, offer them the space that suited the group and make the booking easy. An organiser who finds booking with you effortless will come back with the next group.

Their history also helps plan for the group: the dietary needs that came up last time, the timing that worked and anything that went wrong.

Histories are often incomplete: walk-ins whose names were never taken, bookings made under a partner's name, duplicate profiles for the same guest. Each gap makes the history less reliable.

Fill the gaps where you can: take names for walk-ins who are happy to give them, merge duplicate profiles and link bookings to the right guest. Our guide to duplicate guest records and how to merge them covers the duplicates.

Guest history also shapes campaigns. Guests who have not visited for a while, regulars who visit often, guests who always come for celebrations: each group can receive a message that fits them, if they have agreed to hear from you.

Segmenting by history, rather than sending the same email to everyone, makes each message more relevant and more likely to be welcome. Our guide to regulars: how a venue makes them on purpose covers building regulars deliberately.

Histories become more useful the longer they run, but only if they stay accurate. Duplicate profiles split them, bookings under the wrong name hide visits and old notes that are no longer true mislead. A little care each month keeps them reliable.

Make sure every booking and every order is linked to the right guest, merge duplicates as you find them and update notes when something changes. A history that the team trusts is one they will read.

Over years, a well kept history becomes a record of each guest's relationship with the venue, one of the most valuable things a restaurant owns.

The kitchen can learn from guest history too. A regular who always orders the same dish might be offered a taste of something new by the chef. A guest whose history shows a dish sent back last time can have that dish checked with special care. A guest who always has dessert might be told about a new one before they order.

Share the useful parts with the kitchen through the booking notes or the briefing, not by asking cooks to read profiles during service. A short line at the briefing, "the Taylors are in tonight, they always have the lamb", is enough.

Small touches from the kitchen, guided by history, are often what guests remember most.

Guest history is personal information, and guests trust the venue to use it well. Use it to serve them better, not to pry. Keep it to the team members who need it, protect the accounts that can see it and follow the data protection rules where you trade.

If a guest asks what you hold about them, or asks you to delete it, answer promptly and honestly. A venue that handles history with care earns the trust that makes guests happy to be remembered.

The best test is simple: would the guest be pleased to know you used their history this way? If yes, carry on.

An invented brasserie's manager starts reading the histories of guests booked each evening. One regular stands out: visits every three weeks for two years, then a gap of three months, and the last visit's feedback mentions a cold main. The guest has booked again for Friday.

The manager makes a note for the team, seats the guest at their usual table and visits during the meal to say they are glad to see them back and that the kitchen has changed how mains are held at the pass since their last visit. The guest is visibly pleased.

The guest returns two weeks later, and the three-week pattern resumes. The manager starts doing the same for every regular with a recent complaint or a lengthening gap.

In servearound, a guest's profile shows each visit with its date and time, the party, the table, the orders and what was spent and paid, alongside notes from the team and any feedback the guest gave, and the profile keeps their visits, spend and last visit in view. When the guest books again, staff see their number of visits, their last visit, their notes, their preferences and their allergens on the booking.

Possible duplicate profiles are flagged with how confident the match is and why, and merging moves the reservations, orders and feedback onto the profile you keep. With Campaigns, guests who opted in can be emailed by how often they visit, how much they spend or how long it has been since they last came. See Guest CRM and Campaigns.

The record of every visit a guest has made: when, with whom, where they sat, what they ordered, what they spent and how it went.

For patterns: how often they come and whether that is changing, what they usually do and how the last visit went.

Whether a guest is a regular, occasional or former guest, and whether they are drifting away or becoming closer.

The total a guest spends across all their visits, which shows their value over time rather than on one bill.

Longer gaps, falling spend, a recent complaint or a low rating, and cancelled bookings.

That you remember them, what they like and anything you changed because of them.

Spend, who they came with before or anything they might not want their companions to hear.

Make reading the evening's bookings and each table's history part of the routine before service.

A guest history holds far more than most venues read. Read it for patterns: visit frequency and whether it is changing, who the guest comes with, what they order, their spend over time and how the last visit went. Notice the warning signs of a regular drifting away and the good signs of a regular in the making.

Mention three kinds of fact to guests: that you remember them, what they like and what you changed because of them, and keep the rest in the history. Make reading histories part of the routine, fill the gaps by merging duplicates and linking bookings, and use history to send each guest a message that fits.