Personalisation is the part of this subject with the worst reputation, and it earned it. Done badly it produces the email that starts "Hi FIRSTNAME," the offer for a steak sent to a vegetarian, and the faintly unsettling message that proves a company has been watching. Done well it is not technology at all — it is the oldest thing in hospitality, which is a host who remembers you. This topic is about the difference, and about which of it is actually worth your time.
🤝 Hospitality remembered, not surveillance performed
The same fact can land in completely opposite ways depending on how you use it. A manager who greets a couple with "your usual table?" is delivering the finest moment in hospitality. A restaurant that emails those same people "we noticed you always sit by the window" has taken the identical information and made it creepy. The fact did not change; the feeling did.
What separates them is whose benefit it is for, and whether the customer would have expected you to know. A good host remembering your name is expected — that is what a good host does, and it flatters you. A system telling you it has been tracking your seating preference is not expected, and it makes you calculate what else is being recorded. So the useful frame is not "how much data do we have" but "would this person be pleased or startled to learn we knew this?"
That gives you a test you can apply in three seconds, without a policy document.
- Would they be pleased or startled? If you cannot say confidently, it is startled.
- Is it for them or for you? Remembering an allergy serves them. Reminding them they have not been in for a while serves you — both can be fine, but be honest about which.
- Could a good host have known it? Anything a warm regular-facing manager would naturally remember is safe territory.
- Would you say it out loud, face to face? If saying it at the table would be strange, sending it is worse, not better.
🍽️ The four things actually worth personalising
Most personalisation projects fail because they try to tailor everything and end up maintaining a machine for no gain. In a restaurant, only a handful of things repay the effort — and they are all simple.
| Worth doing | Why it works |
| Recognising someone as a returning customer | Costs nothing, works in person, and is the one people actually value |
| Sending a different message to a different group | The whole point of topic 3; four groups, four messages, not one blast |
| Remembering an allergy or a hard dietary need | Serves them, prevents harm, and is obviously in their interest |
| Timing a message to their own rhythm | Reaching a monthly customer monthly beats reaching everyone weekly |
And the mirror image — things that consume effort and return very little. Inserting a first name into an email does almost nothing and backfires visibly when the field is empty or wrong. Recommending dishes from an algorithm is a solved problem for a shop with ten thousand products and a waste of time for a menu with thirty, where a server's suggestion is better. Elaborate birthday and anniversary machinery is usually a lot of collection for one predictable message a year. The rule of thumb: personalise the group and the timing, not the individual sentence.
🎛️ Segments, not individuals
The practical version of all this is that a restaurant should personalise at the level of the four or five groups from the last topic, and stop there. That is a workload you can sustain forever, it is where nearly all of the benefit is, and it never produces anything unsettling — because a message written for "people who used to come often and have not been in for a while" reads as a general invitation to whoever gets it.
Each group has an obvious different thing to say, and you already know what it is.
- Regulars: something first, or something extra. Not a discount — they were coming anyway, and discounting them is paying for visits you had already earned.
- Occasionals: a reason to come one more time this quarter. This is where an offer actually pays for itself.
- Big-ticket, rare: reach them near their occasion, and talk about groups and celebrations rather than Tuesday specials.
- One-timers: one good invitation back, and then let them go. Chasing them repeatedly costs more than they are worth.
- Drifting: the win-back from the email course, which is the highest-value message you will send all year.
Notice how little technology any of that requires. Five lists and five messages, sent from the same tool you already use, is the entire implementation — and it will outperform an expensive personalisation system running on a list nobody cleaned.
🧑🍳 The version that runs on paper
There is one more form of personalisation that beats everything above and never appears in software brochures: telling your floor staff who is in the room. A manager who checks the book before service and knows that the eight o'clock is a couple who have been in six times, and that the party of ten is a first visit from a company nearby, will produce more warmth in one evening than a year of segmented emails.
That is where your data pays the best return, because it turns numbers back into hospitality delivered by a human being. Keep it to what genuinely helps — they have been here before, they usually order the fish, it is their anniversary if they told you so — and keep it out of sight of the customer, in a briefing, never on a screen at the table. Get this right and you also get an unexpected bonus: staff who see the data being used to treat people well start feeding it, which is the same loop the previous course found with the notebook by the pass.