Personalisation that is not a mail merge

An email arrives: "Dear Sarah, we have missed you! Here is what is new this month." Sarah knows exactly what it is. A list of names, a template and a button. Her first name is the only thing in it that was meant for her, and it fools nobody. That is what personalisation has come to mean for many businesses, and it is not what makes a restaurant feel personal.

Real personalisation in a restaurant happens mostly in the room. It is the host who greets a guest by name, the server who remembers that they take their coffee black, the manager who notices it is their anniversary without being told twice. It depends on what the venue knows about each guest, and on the team using that knowledge at the right moment, lightly.

This guide covers what personalisation really means in a restaurant, three personal touches that work in the dining room, how to use guest preferences and history without making guests feel watched, and how to make emails feel personal without relying on a first name. Every venue and figure in it is an example.

Personalisation means treating each guest as the person they are, rather than as a cover. It rests on knowing something about them, such as their name, their preferences or their history with the venue, and on acting on it in a way they notice and appreciate.

In a restaurant, most of that happens face to face. Software can store what the team knows and put it in front of the right person at the right time, but the personal moment itself is human. A preference remembered by a server feels personal. The same preference printed in an automated email often feels like data.

A mail merge fills a template with details from a list, so that each letter or email carries a name. It was a clever idea when letters were typed by hand. Today, guests receive dozens of merged emails a week, and a first name at the top of a generic message no longer reads as personal.

It can even backfire. "Dear Guest" when the name is missing, a misspelled name or a guest's name used too often in one message all signal that nobody actually wrote to them. The name is not the problem. The problem is when the name is the only personal thing in the email.

Guests decide whether a venue knows them by how they are treated when they arrive, while they eat and as they leave. An email can support that feeling, but it cannot create it. A guest who is greeted like a stranger at the door will not feel known because the newsletter used their name.

So start personalisation in the room, and let everything else follow. The three touches below cost almost nothing, need no new tools and are noticed by every guest who receives them.

The simplest personal touch is a guest's name, said warmly by the host as they arrive. "Good evening, Mr Patel, lovely to see you again" tells the guest they are expected and remembered. It is the same name as in the email, but it means far more coming from a person.

The host can know the name from the booking. Check pronunciation if a name is unfamiliar, and use it naturally, once or twice, not in every sentence. For regulars, greet them by name whether or not they booked. For first-time guests, a name from the booking makes the welcome feel prepared rather than generic.

The second touch is a preference remembered: the usual table by the window, the sparkling water without asking, the dish they always order, the wine they enjoyed last time. Few things make a guest feel more at home than being asked, "The usual?"

Preferences only help if they are recorded, so that anyone on the team can use them, not just the server who happens to remember. Write down the ones that make a difference at the table. Our guide to guest preferences worth writing down covers which ones matter and which are noise.

The third touch is noticing why a guest is there. An anniversary, a birthday, a promotion, a first dinner with new parents-in-law: each changes what the guest needs from the evening. Some want it marked with a candle and a word from the team. Others want discretion and a quiet table.

The occasion is often mentioned when the guest books, or by a companion who calls ahead. Make sure it reaches everyone who will serve the table. A guest who mentioned an anniversary when booking and is wished a happy anniversary by the server feels heard. One who mentioned it and was never asked feels forgotten.

Behind all three touches sits guest history: how often a guest has visited, when they last came, what they ordered, who they came with and anything that went wrong. It is the memory a team draws on to make a visit feel personal.

Read it before service, not during. A host who glances at the evening's bookings in the afternoon, and notices that one guest is returning for the first time in months and another had a long wait last time, can plan the personal touches before the first guest arrives. History used this way turns information into attention.

The quality of personalisation depends on the quality of the notes. Good notes are short, factual and useful at the table: "prefers a quiet table", "always orders the lamb", "coeliac, takes it very seriously", "partner's name is Anna". Bad notes are vague, judgemental or out of date.

Write notes as if the guest might one day read them. "Difficult guest" helps nobody and embarrasses everyone. "Likes to order slowly, do not rush" helps the next server do a better job. Review notes from time to time, and remove what is no longer true.

Recognising a regular is personalisation in its purest form. A regular who walks in and is greeted by name, shown to their usual table and asked whether they would like their usual drink has had a personal experience before they have sat down.

The difficulty is making it reliable, so it does not depend on one manager's memory. When recognition lives in a shared record that the whole team reads, any member of staff can recognise a regular. Our guide to recognising a regular without a secret list covers how to make it a system.

There is a line between feeling known and feeling watched. "Your usual table is ready" feels warm. "You have ordered the steak on each of your last eleven visits" feels like surveillance, even if it is true and well meant.

Use what you know lightly, and let guests lead. Offer the usual, rather than assuming it. Mention a preference only when it helps the guest, such as a dish they might enjoy or a table they like. Keep the detailed knowledge in the background, shaping the service rather than being recited.

Personalisation can go wrong: the wrong name, the preference of a different guest, a mention of last month's companion in front of this month's, a birthday wished on the wrong day. Each one undoes the good feeling it was meant to create.

When it happens, apologise simply and move on. "I am so sorry, I have muddled you with someone else" is honest and quickly forgotten. Then fix the record that caused it, such as a duplicate profile or an out-of-date note, so it does not happen again.

Loyalty emails feel personal when they are relevant, not when they carry a name. An email to regulars about a new dish, written in the owner's voice, feels more personal than a generic newsletter that opens with the guest's first name.

Relevance comes from who receives the email. A note about the new vegetarian menu sent only to guests who prefer vegetarian dishes, an invitation to a wine evening sent to guests who enjoy wine, a welcome back sent to regulars who have not visited for a while: each feels written for its reader, even when the words are the same for everyone in the group.

The practical tool for personal emails is the segment, not the merge field. A segment is a group of guests who share something: regulars, lapsed regulars, new guests, big spenders, guests with a dietary preference. Writing one short email for each segment makes every email more relevant than any amount of merging.

You do not need many. Four or five segments cover most of what a venue wants to say. Our guide to email segmentation with only four segments covers a simple set that works for most restaurants.

Emails feel personal when they sound like a person. Short sentences, specific details and a real name at the bottom: "We have just brought back the slow-roast lamb, and I thought of the regulars who kept asking. See you soon, Maria." That is personal, without a single merge field.

Make replies welcome, and answer them. A guest who replies to an email and receives a real answer from the owner has had a personal exchange. A guest whose reply bounces off an address nobody reads has learned that the email was not really from anyone.

The end of the meal is another moment for a personal touch. A goodbye by name, a word about the dish they enjoyed, a mention that their favourite is coming back next month. These leave the guest with the sense that the venue noticed them all evening.

Small gestures work best here. A handwritten line on the bill for a regular, a word from the chef as they leave, a coat brought without being asked. None of them costs much, and each is remembered far longer than the bill itself.

First-time guests have no history, so personalisation means attention. Ask what brought them in, listen to what they say about their preferences, notice whether they want to talk or be left alone, and adapt.

What you learn on a first visit becomes the history for the second. A note that a first-time guest loved the fish, or that they were celebrating a new job, lets the team make the next visit personal from the moment they arrive.

Allergies are the one area where personalisation is not optional. A guest's allergy must be recorded accurately, flagged on every booking and ticket, and never left to anyone's memory. It is personal in the most serious sense: a mistake can harm the guest.

Handled well, allergy information also makes guests feel looked after. A guest with a nut allergy who is greeted with "We have your nut allergy noted, and the kitchen knows" relaxes in a way no welcome drink could achieve.

Personal touches should not depend on which shift a guest visits. A regular known at dinner should be known at lunch, and a guest known at one venue in a group should be welcomed as a returning guest at another.

That only works if what the team knows is shared: notes on the guest's profile, read by whoever is on, and a mention at each shift's briefing of the guests worth noticing. A shared record is what turns individual memory into a venue's memory.

Personalisation can be overdone. A host, a server and a manager who each mention a guest's preferences in the first ten minutes make the evening feel scripted. A guest's name in every sentence sounds like a sales call.

Aim for one or two touches per visit that feel natural. Let the rest of what you know shape the service quietly: the table is right, the drink arrives without asking, the allergy is handled. Guests notice the result without seeing the effort.

Only use what guests would expect you to know. A guest's usual table, their favourite dish, their allergy and the name of the partner who often joins them are reasonable. Details overheard at the table, or found online, are not.

Be careful what you record and who can see it. A useful test is whether you would be comfortable if the guest read their own profile. If the answer is no, the note does not belong there.

Personalisation is a habit the team learns. Practise greeting guests by name, reading the bookings before service and using notes naturally. Share examples of personal touches that worked, and of the ones that went wrong, so the team learns where the line is.

Make it part of the pre-shift briefing: who is coming tonight that we know, what is special about their visit and what one thing would make it personal. Five minutes before service turns a team's knowledge into a plan for the evening.

Personalisation is hard to measure directly, but its effects show. Regulars return more often, feedback mentions the team by name, and guests comment that they feel at home. Over time, a venue that personalises well sees more repeat visits and warmer reviews.

Watch the repeat rate and read the comments guests leave. When a guest writes that the team remembered their anniversary, or knew their usual table, the personal touch has worked. Share those comments with the team, because they show exactly what to keep doing.

When a guest books for a group, most of the personal touches belong to the host: the person who chose the venue and will feel responsible for the evening. Greet them by name, check that the table is as they asked and let them know quietly that anything they need is in hand.

The rest of the group matters too. A guest at the table with an allergy, a birthday or a first visit deserves the same care as the host. Read the booking notes before the group arrives, so the team knows who is who, and never share details of the host's past visits in front of their guests.

Personal touches do not stop at the door. A regular who calls to book and is greeted with "Lovely to hear from you, shall I put you at your usual table?" feels known before they arrive. A guest who emails a question and receives a reply that answers it properly, signed by a real person, has had a personal exchange.

Make sure whoever answers the phone or the inbox can see what the team knows about the guest, and writes in the same warm voice as the room. A reply that sounds like a form letter undoes the effect of a personal welcome, while a short, specific answer adds to it.

An invented wine bar sends a monthly email to all its subscribers, opening with their first name, and few guests ever mention it. It decides to change its approach. The team starts reading the evening's bookings before service and agrees on one personal touch per regular: a greeting by name, the usual glass offered, an occasion noted.

The owner replaces the monthly newsletter with shorter emails to three segments: regulars, lapsed regulars and new guests, each written in her own voice about one thing that matters to that group. Within a few months, more guests reply to the emails, regulars mention that they feel looked after, and several lapsed regulars return.

In servearound, a guest's profile keeps their visits and spend, filled from bookings and paid checks, with the preferences, notes, allergies and dietary needs the team records. The booking shows the guest's visit count, last visit, notes, preferences and allergens, so whoever is on the host stand can greet a returning guest as one. Allergies and dietary needs entered on a booking are saved to the profile, and the guest's allergies sit at the head of every kitchen ticket.

Campaign emails can merge only a few facts: the guest's name, the venue's and the network's names, a booking link and a menu link. Nothing about a guest's preferences or past visits goes into a campaign, so the personal part of an email comes from who it goes to: audiences are chosen by tier, visits here, spent here, how recently the guest came and dietary needs, with allergens used only to leave guests out. Emails go only to guests who opted in. See the guests module and Campaigns.

Treating each guest as the person they are, using what the venue knows about them at the right moment.

Not on its own. A name at the top of a generic message convinces nobody.

A name said by a person, a preference remembered and an occasion noticed.

Short, factual notes that help at the table: preferences, allergies, occasions and anything that went wrong.

Yes, when it recites what you know. Use knowledge lightly and let guests lead.

Through attention: ask, listen and record what you learn for their next visit.

Send short, relevant emails to small groups of guests, written in a real person's voice.

The personal moment is human. A shared record helps the whole team know what one person knows.

Personalisation in a restaurant is not a mail merge. A first name in a generic email convinces nobody; what makes a venue feel personal happens in the room. Start with three touches: the guest's name said by a person, a preference remembered and an occasion noticed. Draw on guest history, write down what matters at the table and read the bookings before service.

Use what you know lightly, so guests feel known rather than watched, and fix mistakes simply when they happen. For emails, rely on relevance rather than names: a few short messages to small groups of guests, in the owner's voice, from an address someone reads. Treat allergies as a safety matter, share what the team knows across shifts and venues, and keep notes you would be happy for the guest to read.