There’s a paradox we see in restaurant after restaurant. Operators want to deliver memorable hospitality. They’ve read Unreasonable Hospitality, watched the Forks episode of The Bear, want to make those gestures that turn a guest into a fan. Then Saturday night arrives, the manager pulls the team together for the pre-shift, and says: “Tonight we have the Davises at table 7 — I think they’re regulars, but I’m not sure.”
“I think.” “Not sure.” That’s the moment hospitality dies. Not from lack of intent. But because the necessary information isn’t available at the moment it’s needed.
Between the desire for unreasonable hospitality and its execution sits an operational tool: the guest CRM connected to your reservation system, and the pre-shift meeting that pulls from it. Without the first, the second is blind. Without the second, the first is wasted.
What CRM means in a restaurant
CRM — Customer Relationship Management — is a term that often conjures up enterprise software. In a restaurant, it’s much simpler: a profile for every guest, where the information you need to recognize, remember, and welcome them lives.
What’s in a well-kept guest profile?
- Basic info. First name, last name, phone, email.
- Visit history. Last visit date, number of visits, who they came with.
- Preferences. Favorite table, dishes ordered, regular wine, preferred meal.
- Restrictions. Allergies, intolerances, dietary choices, religious preferences.
- Special dates. Birthday, anniversary, meaningful personal dates.
- Free-form notes. “Came in for a first date — went well.” “Loved the sommelier’s Sangiovese pick.” “Works as a food blogger, writing a book.”
We’ve covered this in detail in our piece on restaurant CRM and guest loyalty — the core idea is that without a structured system to remember, hospitality depends on individual server memory. And individual memory doesn’t scale. When a server quits, all the accumulated knowledge of guests goes with them.
The problem: data exists but doesn’t reach the floor
Most restaurants already have some guest information. It’s scattered: bits in the reservation emails, scribbles on the paper book, things in the owner’s head, WhatsApp threads. The problem isn’t lack of data. It’s that the data doesn’t reach the floor at the right moment.
When the manager opens the book at 6:45 for the pre-shift, they need to see, for every table of the night:
- Who the guests are (first-timers or regulars)
- The last three visits
- Relevant preferences
- Allergies
- Notes from the previous service
If this information lives in five different places (paper book, email, WhatsApp, personal memory, post-its on the wall), the manager doesn’t pull it in time. They walk into the pre-shift prepared on the two or three tables they personally remember.
The remaining 80% of the service goes through without the data advantage. The regular gets treated like a first-timer. The couple back for their anniversary doesn’t get the surprise glass. The gentleman with a lactose intolerance ends up with a white-chocolate dessert in front of him.
Not catastrophes. Micro-failures. But exactly the spot where the difference between service and hospitality gets decided.
The ideal flow: from reservation to pre-shift to gesture
Here’s how it should work in a restaurant that uses CRM and pre-shift in an integrated way.
Step 1 — The reservation populates the profile
Mark books online for Thursday night, two people. He’s already booked twice in recent months. The reservation system, connected to the CRM, recognizes his email and automatically populates the guest profile with the new reservation. Notes from previous visits are already there: first time he came with his fiancée, ordered the steak and a Chianti; second time with two friends, tasting menu.
Step 2 — Notes from the previous service are fresh
After Mark’s last visit, the server who took care of him added two lines to the profile: “Lovely couple, really enjoyed the Chianti recommendation. He’s into natural wines. Engagement anniversary March 14 (3 years).” This is the practice of keeping curated server notes — sounds basic, changes everything.
Step 3 — The pre-shift surfaces the data
It’s 6:45 on Thursday. The manager opens the reservation system dashboard and sees tonight’s list. Filters for “guests with profile” and identifies the 4 tables with history. For each, a three-line summary is already visible.
For Mark’s table, the manager tells the team: “Table 9, 9 PM. Mark and Laura, third visit. He’s into natural wines — Andrea, do you have two or three suggestions for him? And one detail: in October it’s their 4th engagement anniversary, they mentioned it last time. Tonight isn’t the date, but if they bring it up, consider a small gesture.”
Step 4 — The gesture happens (or doesn’t, and that’s fine)
Mark and Laura arrive. Greeted by name from the first step. The sommelier, while opening the menu, suggests a Pelaverga from Piedmont that isn’t on the visible wine list. “I noticed last time you really enjoyed the Chianti. This is a natural Piedmont wine I think you’d like — if you want to try it, we’ll bring you a taste.”
This is the one-inch dive Will Guidara describes in his book: a small dive (one inch, not a hundred) into the guest’s data, never invasive, always in service of the experience. The gesture isn’t over the top. It’s perfectly calibrated. Mark feels seen. Laura feels taken care of. The sommelier looks brilliant — but they only read the profile ten minutes ago.
What you need to get to this flow
You’d expect us to say “expensive, sophisticated software.” Not really. What you need is fairly basic.
A reservation system with integrated CRM. Not a paper book. Not a booking system that only saves name and phone. A system where every reservation links to a guest profile, where notes can be added and read in seconds, from the server’s phone or the front-of-house tablet.
The habit of taking notes. The best system in the world is useless if nobody writes anything in it. Two minutes after each service, where the server or manager adds a line on significant guests. After a month, you have data. After three months, you have an asset.
A structured pre-shift meeting. Without the pre-shift, the data stays in the database. The pre-shift is the moment when data transfers from the system into the head of the server who will work that table. If you don’t yet run a structured pre-shift, start with our pillar on pre-shift meetings and the practical 15-minute agenda guide.
The ROI: what this is actually worth
Let’s put numbers on this, because it’s not a styling exercise.
A loyal guest is worth, on average for a mid-tier restaurant, $2,500–$4,000 over a three-year horizon (visit frequency × average check + word-of-mouth introductions). A one-time guest is worth $50–$80.
If a restaurant doing 1,500 covers a month moves its first-time guest return rate from 15% to 20% — a modest but realistic lift — you’re talking 75 newly loyal guests per year. At $3,000 of three-year value per loyal guest, that’s $225,000 of incremental revenue on the three-year horizon.
The driver of that +5% is one thing: the experience the guest had on their first and second visit. And experience is built on recognition, attention, and the right gesture at the right moment. Which means: guest data + pre-shift meeting.
Compare that to the cost of an empty table or to the staff turnover cost, and you can see why ten minutes a day plus a few dollars a month on a reservation system pays for itself many times over.
Mistakes to avoid
1. Don’t overload the pre-shift with data. For each table, two or three relevant points. Don’t read the whole profile. The team needs to memorize what’s actionable.
2. Never use data to be intrusive. A sommelier suggesting a wine “because we noticed you enjoyed the Chianti last time” works. A sommelier saying “I see from your profile you turned 45 last month” is creepy. The rule: data must improve the guest’s experience, never make them uncomfortable.
3. Keep the data updated and protected. If you take notes on guests, you’re doing so under data privacy regulations (GDPR in Europe, CCPA in California, similar regimes elsewhere). Information must live in a secure system, accessible only to authorized staff, deletable on request. A good reservation system handles this for you.
4. Don’t lose history when a server leaves. If notes live in one server’s head, the day they quit you lose everything. Knowledge about guests must belong to the restaurant, not to individuals.
The difference between theory and practice
You can talk about memorable hospitality forever. But it only happens concretely if two things are in place: a system that remembers for you, and a ritual (the pre-shift) that delivers that memory to the right table.
Without both, unreasonable hospitality stays a nice idea you read in a book. With both, it becomes something your team produces every single night, repeatably, without depending on any one person’s brilliance or having a good day.
And your guests notice. They don’t need to know how it works behind the scenes. They just know that, when they walk into your restaurant, somebody recognizes them. Somebody remembers. Somebody thought about them before they even walked in the door.
Coperti combines reservation management and guest CRM in a single tool. Every reservation auto-populates the guest profile with history, preferences, special dates, and notes. Your team walks into the pre-shift with the data ready, at a glance. Explore the features, compare pricing, or request a demo.