Guest Profile
A unified record of every interaction a guest has had with the hotel, stays, charges, preferences, communication and consents.
A guest profile is the single record of truth about a guest across every system in the hotel. At minimum it holds identity (name, email, phone, ID), stay history, preferences, marketing consents, and a lifetime-value summary. In a well-built PMS it also unifies F&B charges, spa visits, channel of acquisition, message threads and any complaints or compliments.
A clean guest profile is the foundation of every personalisation, every loyalty programme, every "welcome back" gesture, and every GDPR-compliant marketing campaign. Profiles fragmented across PMS, POS and email tools are the single biggest reason hotels under-monetise their repeat guests.
Where this term shows up in daily operations.
Returning guests, recognising a past guest at check-in, knowing their last room, their preferences and their lifetime value.
Personalisation, sending pre-arrival messages with the right language, tone and offer, based on past behaviour.
GDPR, a single profile is the only sane way to honour data subject access, rectification and deletion requests across every system.
Group reservations, a master guest profile for the booker plus profiles for each in-house guest is the only architecture that survives weddings, conferences and tour groups.
What people get wrong.
Fragmented profiles, the same guest appearing as four different records (PMS, POS, email tool, OTA import) breaks every metric you compute on top.
Storing too much. Over-collection of guest data, beyond what the stay or marketing actually needs, is a GDPR liability.
Mixing identity (name, email) with consent (marketing opt-in) in the same field. Marketing consent must be auditable and timestamped, not a checkbox in a notes field.
Not deduplicating. Without a fuzzy-match step on email + phone + name, the guest list drifts into thousands of duplicates within a year.
HotelBee Guest Experience in HotelBee.
HotelBee unifies guest profiles across PMS, POS, channels and direct bookings, with consent-aware messaging, segmentation and a single GDPR control plane.
What should a guest profile contain?
Identity (name, email, phone, ID/passport where required), preferences (room type, floor, pillow, allergies), stay history with totals, source channel mix, marketing consents with timestamps, and any operational notes (VIP, do-not-rent, special requests).
How is a guest profile different from a CRM?
A CRM is broadly a marketing/sales tool. The guest profile is the operational record inside the PMS. A modern hotel PMS effectively is the CRM, the profile lives where every stay, charge and message gets attached automatically, rather than syncing to a separate system.
Are guest profiles GDPR-compliant by default?
Only if the system supports lawful-basis tracking, marketing consent timestamps, retention policies, and data subject access / deletion workflows. The HotelBee guest profile bakes these in.