The word CRM is on a lot of hospitality products that do not really have one. So rather than argue about definitions, here is a more useful test: the five jobs a hospitality CRM is actually for. Judge any product against these and the marketing falls away quickly.
For the bigger picture of why this matters commercially, the hospitality CRM guide is the full version. This piece is the working checklist.
Job one: recognise the returning guest
When someone who has been in before books or walks in again, the system should know. Not "has this email booked before", but a real, single record that says this is the same person, here is their history, here is what they like. If your CRM treats each visit as a fresh transaction, it is failing the first and most basic job. Recognition is the foundation everything else is built on.
Job two: show value, not just activity
Plenty of tools can show you who books most often. Far fewer can show you who is actually worth most, because that needs spend, and spend lives in the till. A guest who books every week and spends little, and a guest who comes monthly and spends heavily, are very different to your business. A CRM that cannot draw on real spend is showing you activity and calling it value. The two are not the same, and confusing them leads you to fuss over the wrong people.
Job three: flag the guest who is slipping away
This is the job most products quietly skip, and it is the one with the most money in it. Your regulars do not usually quit in a dramatic moment. They drift. The fortnightly table becomes monthly, then stops, and unless something tells you, you find out months later when you happen to wonder whatever happened to so-and-so. A CRM worth the name watches for that pattern and surfaces it while you can still do something, a message, an invitation, a reason to come back.
Job four: keep preferences and allergies in front of the team
The personal touch that makes an independent special is mostly memory, and memory does not scale past the people who happen to be working that night. A CRM holds the corner-booth preference, the dietary need, the fact that it is their anniversary, and puts it in front of whoever is on, not just the manager who happened to learn it. This is also a safety job, not only a charm one. Allergy information that lives in one person's head is a risk. In the guest record it is shared.
Job five: track consent properly, per channel
This one is not glamorous and it is not optional. You need to know who has agreed to be emailed, who has agreed to be texted, and who has asked you to stop, tracked per channel and kept current. A CRM that handles consent loosely is a liability waiting to happen. A good one makes doing the right thing the easy thing.
What fails the test
Run the three usual suspects through those five jobs. A reservation log does job one for bookers only and little else. An email list does none of them, it is a contact channel. A loyalty database knows who has points, which is a sliver of job two at best. Each is a useful tool. None is a CRM, because none holds the whole guest and acts on it.
Where Grace fits
In Grace the CRM is the Guest Book, and it is built to do all five jobs in one place because it draws on the whole platform. Bookings and walk-ins, spend from the till, loyalty, marketing and consent all land on one record per guest, so recognition, value, churn signals, preferences and consent are not five integrations you have to maintain. They are one record doing its job. You can see it on the Guest Book page.
If a product you are looking at cannot do these five things, it does not matter what the homepage calls it. It is storing data, not managing a relationship.
FAQ
What does a hospitality CRM do day to day?
It recognises returning guests, shows you who your regulars are by real value, flags guests who are drifting away, keeps preferences and allergies in front of the team, and tracks marketing consent. Those are the working jobs. Anything that only stores names and email addresses is not doing them. - q: "How is a hospitality CRM different from a booking system?" a: >- A booking system knows the booking. A CRM knows the person across everything they do, bookings, walk-ins, spend, loyalty and marketing. A booking history is one input to a CRM, not a CRM in itself. - q: "Do I need a CRM if I already have an email list?" a: >- An email list tells you who you can contact, not who is valuable, who is loyal, or who has stopped coming. A CRM answers those questions. The list is one channel the CRM feeds, not a substitute for it.