Auto-Tagging

Auto-tagging exists in most customer relationship management tools. The hospitality version belongs to a particular kind of product: a restaurant CRM, sometimes called a guest data platform. It connects to the reservation book on one side and the point of sale on the other, and keeps a single profile per guest.

How does auto-tagging work in a restaurant CRM?

Auto-tagging in a restaurant CRM works by rule rather than by hand. An operator defines a condition, such as a level of wine spend across visits or a number of visits inside a year. The platform checks that condition against every guest record and applies the label to whoever matches.

The distinction worth understanding is that an automatic tag is a standing question rather than a stored answer. The rule is re-evaluated as new reservations and checks arrive. So the tag is true at the moment it is read, not on the day somebody typed it. A manual tag is a note about the past, and a rule is a description of the present. A good automatic tag removes itself too. When a guest stops matching, the label goes. This is why guestbooks kept by hand accumulate VIPs who last visited in 2019.

What guest data can you tag on?

The data available for tagging is bounded by what a restaurant’s systems pass through, and that varies far more than vendors imply. Point-of-sale systems differ in whether they send item-level detail with each check or only a total, and some send guest contact information while others send none. A restaurant whose POS reports totals only can build a rule about how much a guest spends, but not one about what that guest drinks.

Guest data for tagging arrives in three streams. Reservation platforms supply visit counts, party sizes, no-shows, and booking notes. The point of sale supplies spend and, where the integration allows, individual menu items and categories. Reviews, private events, hotel stays, and messaging engagement supply the rest. That context is usually the most interesting material to tag on and the least likely to be connected.

Do guest tags sync back to Resy and OpenTable?

In a restaurant CRM built for it, yes, and the sync runs in both directions. A restaurant CRM reads reservations and guest records out of Resy and OpenTable. It applies its rules to the combined reservation and point-of-sale history. Then it writes the resulting tags and guest notes back into those same reservation platforms.

Bidirectional sync is the detail that decides whether auto-tagging changes service or only changes marketing. A tag that lives only inside a CRM can populate an email segment. It cannot tell a host anything, because the host is looking at the reservation book. Writing the tag back into Resy or OpenTable puts it on the reservation itself, where the person greeting the guest will actually see it. In hospitality the book, not the CRM, is the screen the floor team works from.

Can a general CRM like HubSpot do this?

A general-purpose CRM such as HubSpot cannot do this natively, because it has no built-in connection to a reservation platform. Bridging HubSpot to Resy or OpenTable means commissioning a custom integration, and the connectors that exist mostly pull bookings in as marketing contacts.

The direction of the data is the real difference. A general CRM imports a reservation so a marketer can email the guest afterwards. A restaurant CRM reconciles that reservation against the check the table actually spent. It derives a tag from the two together, then pushes it back to the screen the host reads at 7:45 on a Friday. Marketing automation platforms and email tools sit on the same side of that line as HubSpot. They can act on a list. They cannot recognize a guest at the door.

Why do manual guest tags decay in restaurants?

Manual guest tags decay in restaurants faster than in most industries because the institutional memory leaves. Aggregated across 2001 to 2025, annual turnover in accommodation and food services has averaged 75.6% on Bureau of Labor Statistics JOLTS figures, against 43.4% for all nonfarm employment. A restaurant can reasonably expect to replace most of its staff inside a year. The manager who knew that table 12 always wanted the corner booth leaves, and what they knew goes with them.

Tagging conventions drift on the same curve. One room’s VIP marks a regular. Another’s marks a friend of the owner. A third’s marks anyone who once complained. Eventually the team stops trusting the labels and stops reading them. A rule survives a handover because it is written down as a condition; a convention in somebody’s head does not.

Some platforms also offer bulk cleanup for guestbooks that already carry years of inconsistent manual labels. Loyalist’s version, Guestbook Studio, is rolling out account by account and runs passes an operator reviews before anything changes: what we learned cleaning hundreds of guestbooks.