Being remembered (a name, a usual order, a preferred table) is one of the most consistently cited reasons guests describe a venue as a favourite. It's also one of the hardest things to do consistently at scale, once a venue has more regulars than any one staff member can personally track.
How recognition surfaces in practice
The moment a reservation is checked in, or a loyalty pass scanned, the guest's profile appears on the relevant screen (visit history, usual order, dietary notes, any special occasion on record) without a host or server needing to already know that guest personally.
Why this scales what a great host does naturally
A skilled, longtime host remembers regulars by instinct. This makes that same experience possible even when the guest is served by someone working their first week, recognition doesn't depend entirely on tenure.
A guest who mentioned a dairy allergy on their last visit three months ago has that note surface automatically at the next booking, not dependent on the same server remembering, or the guest having to repeat themselves.
The data behind it
This draws from the same unified guest profile covered in Customer CRM: recognition isn't a separate feature, it's that profile made visible at exactly the moment it's useful: the point of service.