When two guest profiles should stay separate
Imagine a receptionist preparing for an arrival and finding two profiles with the same surname and a similar email address. One includes a room preference; the other has a note about an unresolved complaint. Combining them may look like tidy housekeeping, but a wrong match can shape the next conversation in the wrong way.
Treat similarity as a question
Names are shared, transliterated, shortened, and entered with typos. A family may use one email address for several travelers, while a booking contact may not be the person staying. A matching phone number can belong to a company, an assistant, or a household. These details can justify a closer look; alone, they do not prove identity.
The practical risk is not limited to a messy database. A preference, accessibility request, service recovery note, or contact permission may be attributed to the wrong person. Staff acting on that history may send an awkward or inappropriate message.
Check before changing the record
Use a simple stop-and-check routine. Compare independent details that are already available for the booking, such as the guest’s full name, the dates and property of a prior stay, and a contact detail confirmed directly with the traveler. Ask a neutral question when needed: “I see two records that may be yours. Could you confirm which email or previous stay belongs to you?” Avoid reading private notes aloud as a way to test recognition.
If the evidence remains mixed, leave the profiles separate and record what needs review under the hotel’s existing process. Do not copy notes or preferences across while identity is uncertain. Ask the designated supervisor or data owner to review the case, and keep the original records available until that decision is documented.
Use a clear decision threshold
A useful criterion is whether at least two independent identifiers align and the guest or an authorized colleague has confirmed the relationship. The hotel should define which identifiers count and who may approve a change; local privacy and record-retention rules still apply. This is a cautious operating guideline, not a universal identity standard.
After a confirmed correction, check that the right history remains with the right person and that no unrelated note or permission moved with it. The goal is not to merge every plausible pair, but to make the next service decision from information the team can reasonably trust.