Stop losing regulars over forgotten preferences

Your regulars are the backbone of your restaurant. They come back not just for the food — they come back because they feel known. The booth by the window. No cilantro. A birthday coming up. When a host forgets to log that, or a new team member has no idea it ever existed, that customer quietly notices. Do it twice, and they start trying somewhere new.

The problem isn't that your staff doesn't care. It's that guest preference tracking has no real home in most small restaurants. It lives in someone's head, or in a notebook that disappears with the person who wrote it. Here's how to change that.

1. Give preferences a single place to live

Verbal handoffs die at shift change. Pick one tool — even a shared Google Sheet — and make it the single source of truth for guest notes. Columns that actually matter:

• Guest name (and phone number if they've shared it)
• Seating preference
• Dietary needs or allergies
• Personal details worth remembering (anniversary, kids' names, usual order)
• Date last visited

The format matters less than the commitment: every preference gets written down before the shift ends, not "when there's time."

2. Build the logging habit into your close-out checklist

Habits form when they're attached to something people already do. Your hosts already run through a close-out routine — wiping the stand, printing tomorrow's reservations, counting the wait-list. Add "log any new guest notes" as a non-negotiable step in that checklist.

Make it take under two minutes. If your team dreads it, it won't happen. Three short fields per guest is enough. The goal is capture, not a novel.

3. Brief the floor team before every service

A guest preference log is useless if only the host sees it. Spend five minutes before each service calling out the regulars on tonight's reservation list and any notes attached to them. Servers who know that table four always orders the same Barolo and skips dessert can have that conversation ready — and that feels like magic to the guest.

This briefing also catches walk-ins you recognize. If your host spots a familiar name in the book and flags it to the server, the guest gets a warmer experience even when nothing was pre-arranged.

4. Capture walk-in regulars, not just reservations

Walk-ins are where preference data falls through the cracks most often. There's no booking record to attach a note to, so nothing gets written down. Fix this with a simple end-of-shift habit: after a busy Friday, your host takes two minutes to jot notes on any familiar faces who came in without a reservation.

If you use a POS with a customer database (Toast, Square for Restaurants, and others have this), link the note to their name there too. Over time you build a profile without any single person having to hold it all in their head.

5. Recover fast when something slips

Even with good systems, a preference gets missed. Someone gets seated in the wrong spot. A server doesn't know about the allergy. What separates restaurants that keep regulars from those that lose them is what happens next.

Train your team to own the recovery immediately — acknowledge it, fix it where possible, and comp something small if the mistake was meaningful. Then log what happened so it doesn't repeat. A guest who watches you handle a mistake well often becomes more loyal than one who never experienced a problem at all.

---

Tracking preferences, briefing your team, and keeping the log up to date is exactly the kind of operational work that eats up your mental bandwidth without feeling urgent — until a regular stops coming in. If you'd rather focus on the floor and let someone else handle the admin, that's what a Sidekyk is for. Message your Sidekyk on WhatsApp and it can help you build the tracking system, draft your pre-shift briefing template, and remind your hosts to log notes at close — no app to learn, no extra tab to open. Find out more at sidekyk.ai.