One Guest Profile Across All Your Hotels
Keep one guest profile per person across every property, stop OTA relay emails merging strangers, and catch duplicate bookings early.
Every guest, corporate client and travel agent you have ever sold to is held as one record. A stay at one of your properties shows up when the same guest books another. Your front desk creates the record and the Hotel CRM reads it; no imports needed.
An email alone doesn't identify a guest
OTAs put their own relay email on every reservation. Once, two bookings sharing that address turned one guest into someone else, so matching on email alone has been dropped. A guest is matched on name, phone and email together; an email by itself matches nobody.
Catching a double booking
Suppose your desk enters a manual booking for someone who already holds one for that night, perhaps because the OTA booking had no room yet and was hidden from view. The system flags it before a second stay is created. A single question, a single sentence, and the duplicate the audit would later have marked as a no-show never exists.
Moving a stay to someone else
A guest checks out early and wants the invoice made out to a colleague. Your administrator can reassign the stay to another person at any stage, in house, departed or billed, and the log notes who did it, when and from where. This is not the same as fixing the spelling of a guest's own name, which updates their profile everywhere.
What the profile stores
ID details, nationality, preferences, a GSTIN for B2B invoices, and a do-not-email flag that is never overridden.
