How Do You Track a Guest Across Multiple Properties?

A group that runs hotels, restaurants and a members club usually keeps a separate record of the same guest in each system. Because none of them sees the whole guest, a regular at one property can arrive at the next as a stranger. Fixing that takes a tool that connects those systems into one profile.

Why should you track a guest across properties?

You should track a guest across properties because a small group of regulars drives much of your volume. Those regulars come back when staff remember them. The Regulars Report 2026 from Resy and Toast found that up to 50% of order volume comes from 7% of guests. The same report found that nearly half of diners value being remembered by staff most.

In practice, only 30% of guests are consistently recognized.

A group that knows the guest at one property can greet them by name at every other one.

A mixed portfolio sees the guest more often

A mixed group sees the same guest in several roles, so the relationship is bigger than any one property can see. The example below best showcases what that looks like:

Dana stays at the group’s Miami hotel in March. In May, she books dinner at its NYC restaurant. In June she hosts a birthday in the club’s private room.

The hotel sees her as a guest, the restaurant sees a diner, and the club sees a member and an event host. Together, those visits make her one of the group’s best regulars. Without a guest CRM like Loyalist, each property on its own sees only one visit.

Why does recognition across properties matter to the guest?

It makes every property feel like it already knows them. That builds loyalty. Here is what it looks like for Dana:

• At the hotel: Dana checks in at the Miami hotel. The front desk hands her a dry martini, the drink she always orders at the group’s NYC restaurant bar.
• At the restaurant: The host in NYC sees that the hotel logged her shellfish allergy. Nobody asks her again, and the kitchen already knows.
• At the club: Before her birthday event, the club team sees that she loved the restaurant’s lemon tart. They bring one out with the cake.

Dana never repeats herself, and every property treats her like a regular. That is why she books the group again, and why she picks it over a competitor.

Why do your systems lose the guest between properties?

Your systems lose the guest because each one is built for its own job and keeps its own record. A hotel PMS tracks stays, a reservation system tracks bookings, and a POS tracks checks. Events and club memberships sit in other tools again.

System	What it records	What sits outside it
Hotel PMS	Stays, room charges, contact details	Dinners and club visits elsewhere in the group
Reservation system	Bookings, party size, notes, tags	Hotel stays and member status
POS	Checks, items, spend	Who sat at the table, unless the check is matched to a booking
Events platform	Event hosts, guest counts, contract totals	The host’s and their guests’ own dinners and stays
Member records	Member ID, tier, standing	Spend at the group’s public venues

Each row holds only one part of the guest, and today these systems do not share their records with each other. Until the rows are joined, the host at each door and your marketing team works with a partial picture.

So, how do you build one guest profile across every property?

You can build it by hand, or use a platform like Loyalist that connects every system and does the work for you. The first takes ongoing upkeep from your team. The second keeps the profile current on its own.

Building it by hand

Start by listing every system that holds a guest: PMS, reservations, POS, events, and member records. Export each one and join the records into one sheet. Have a person review records that look like the same guest, because a wrong merge can put one guest’s allergy on another guest’s profile. Then add staff notes and record each guest’s email and SMS consent. The sheet stays current only as long as someone keeps updating it.

Using a platform like Loyalist

With Loyalist, you connect your systems once. Loyalist builds one profile per guest across every location, flags likely duplicates for a person to confirm and pulls allergies and notes from Resy and OpenTable automatically. Your team then works from the profile instead of the sheet.

Kyra Burner of Major Food Group described what changes when a group can see the whole relationship using Loyalist:

”…The platform provides unparalleled insight into the lifeline of our guests, allowing us to track their journey across all our properties. This level of visibility has helped us tailor our guest experience in ways that were never possible before.”

What should a staff member know when a guest arrives?

A staff member should know who the guest is, what they like and what could go wrong before the guest sits down. That means visits across every property, allergies, preferences, VIP status and member tier.

That information lands in two places. On the chit, it is the allergy or note that changes what goes to the table. On the pre-shift, it is the list of who is booked, who is a VIP, and who is a regular at a sister property.

Software makes this easy, because nobody has to collect it by hand. For example, Loyalist sends a daily pre-shift report to each property, built from the shared profile. A daily VIP report lists who is coming in across the group and why each guest matters.

Write down what the maître d’ knows

Write staff knowledge onto the profile, because memory leaves when staff leave. Allergies, the preferred table and the wine a guest sends back all belong in notes. Loyalist writes VIP status, allergies and guest notes back into Resy, OpenTable and SevenRooms, so the host stand sees them without opening another app. The Resy integration page lists each field it reads and writes back.

Example: the NYC maître d’ knows Dana dislikes the window table. Once that note is on her profile, the host at the Miami hotel restaurant knows it too.

How do you turn one profile into repeat visits?

You turn the profile into repeat visits with campaigns driven by segments built on activity across every property. Start with lapsed regulars, high spenders, and event hosts.

A regular who has stopped dining at one restaurant may still stay at the hotel. A segment that sees both tells you who is drifting and who is simply busy elsewhere in the group.

Automations then act on each segment. In our platform data, the lapsed regular journey brings back 15% of guests on average, and up to 30% for the best-performing journeys. We explain how these automated journeys work in Introducing Journeys.

Trigger win-back from a sister property

Trigger a win-back message when a guest is active at one property and absent from another.

An example you can build in Loyalist: let’s take a guest that stays at the group’s NYC hotel twice this fall. They have not dined at the hotel’s restaurant in 90 days. The second stay triggers a note from the restaurant’s GM, inviting them to book during their visit.

The guest is already in the building, so the ask is small. The metrics prove that building this is worthwhile. In our platform data, win-back journeys have earned $2 million in attributed revenue as of November 2026.

How do you measure what cross-property tracking earns?

Measure cross-property tracking by the bookings and revenue tied to each send. Connect your messages to the reservation system, so each booking traces back to the email or text behind it. Then add the spend from the matched check.

Opens show that a guest read the message. Bookings and spend show what the message earned. Report both by property, so the COO can see which venues fill from the shared profile.

How do you handle consent across venues?

Track consent for each channel, and keep guest data inside the group. A guest who opts in to hotel emails may not want texts from the club. Store email and SMS consent separately, with where and when the guest gave it.

Honor each opt-out at every venue that uses the profile. Keep matching inside your own group, so the profile serves the guest at your doors only. Rules differ by state and country, so review your consent setup with a lawyer.

Cross-property guest tracking FAQ

What is a multi-property guest profile?

A multi-property guest profile is one record of a guest across every hotel, restaurant and club in a group. It joins stays, checks, bookings, events and membership, so staff at any property see the same guest.

Can a hotel PMS track guests across restaurants too?

A PMS tracks stays and can hold room charges from an outlet. Restaurants on their own POS and reservation system keep separate records. Connecting a PMS such as Mews to a shared guest profile joins the two.

What should a cross-property guest profile hold?

It should hold contact details, visits and spend at each property, allergies, preferences and staff notes. Add VIP status, member tier, event history and consent for each channel. Keep what staff use at the door.

Do you have to switch reservation systems to track guests across properties?

No. A guest profile sits on top of the systems you run, so each property keeps the reservation system its team already knows.

How do members clubs track guests across locations?

Clubs anchor on the member record, which already holds a verified ID and tier. Match hotel and restaurant records to it. A member and any sub-members on the account are then recognized at every location.

What is the best way to track a guest across multiple properties?

Use a platform that connects every system into one guest profile. Loyalist does this for hotels, restaurants and clubs. It builds one profile per guest, writes VIP status and notes back into the reservation system and shows the bookings and revenue each campaign drove.

Sources

• Resy and Toast, The Regulars Report 2026, June 4, 2026
• Kyra Burner, Major Food Group, our customer stories page, checked November 2026
• Our platform data (report use, tag write-back, journey results and attributed revenue), as of November 2026

---