OR has often failed to identify repeat guests, even though emails, phone numbers, etc, are the same. Even when it does, files from the guest record (such as a picture ID) are not carried forward.
I Suggest
1) That, at the least, any new guest with any matching characteristics of a prior guest’s Full Name, address, phone, email, or CC number, be at least presented as a possible match for us to approve or ignore, or tag for further review. The address could help to identify a bad guests who now has their spouse or other household member make the reservation.
2) That with any prior guest match, including through the process suggested above or through whatever algorithm is being used, that we be given the option of carrying forward prior files, tags, and notes.
I think that tags are being currently carried forward, but have been told that files do not. If I have stored a picture ID or other information, I prefer to retain it with the new reservation.
Thanks! Please vote.
Charlie
Charlie, you bring up an interesting point. I had to go make a few mock bookings to make sure I was thinking clearly.
I see TAGS associate with bookings, not guest records. While I have been using them this way, I think a tag associating with a contact would be a great idea. Currently, custom fields may be the only option.
Check our this forum topic: Repeat Guests - Custom message triggers - Feature Requests - Forums - OwnerRez