By matching records that belong to the same person even when the details do not match exactly – a name spelled differently, an old email address, a phone number entered with and without a country code – then merging them into one profile and enriching it with what each source knew. This is work nobody does by hand at any scale, which is why most properties have a guest database several times larger than their actual guest count.

Not quite – it solves the problem a hotel CRM depends on. A CRM manages campaigns and communication; guest data unification makes sure the records those campaigns run against are accurate in the first place. Sending a returning-guest offer to someone who exists three times in your database, under two different email addresses, is a data problem rather than a marketing one. VISIT's guest data layer sits inside the PMS, so the profile is correct at the point it is created.

No. Guest profiles and the AI that maintains them sit inside VISIT PMS, so staff see the guest's history, preferences and previous stays on the screen they already use at check-in – no second login, no separate tool, no switching context mid-conversation with a guest standing in front of them. That last point is why in-PMS placement matters more than the feature list: a guest insight nobody sees at the right moment has no value.

It lets staff act on things the guest never has to repeat. A returning guest's room preference, the allergy noted last visit, the anniversary they mentioned, the fact that the last stay had a problem that was resolved – all visible at check-in rather than in someone's memory or a note nobody opens. Guests rarely notice good data. They notice being asked the same question for the third time.

Yes, by making the offer relevant rather than routine. A guest who booked the spa on both previous stays is a different prospect from one who has never used it, and a family booking in July is not the same offer as a couple in November. With one accurate profile per guest, upsell prompts can be based on what that guest has actually done. Generic upsells get ignored; that is not an offer problem, it is a data problem.

Yes, and multi-property is where it matters most. A guest who has stayed at three properties in the same group is one guest, not three – but without a shared profile each property treats them as new, and the group loses the one thing it has that a single independent hotel does not. With unified profiles, a returning guest is recognised at whichever property they arrive at, and group-level guest history becomes usable rather than theoretical.

It removes the reassembly. Without one profile, answering a simple question – has this guest stayed before, did anything go wrong, what did they book last time – means checking the PMS, the spa system and an email thread. With one profile it is one screen. The saving is small per instance and constant, which is why it is easy to underestimate and hard to give up once you have it.