Hi @Jasmin H., 

thank you for the question. 

I understand that it would be more convenient to retrieve a lost key simply with your surname. However, for security reasons it would be very risky. A guest could simply have access to other rooms just because they know somebody else’s last name (such as friend, colleague, or anyone else) without the consent of the person staying in the room. That is why there should be at least two factors to authenticate the guest in order to grant them access to a room (in this case, a surname and a reservation number). 

Hope it’s clear :) 

Thank you @alzbeta skrabalkova 

But then it makes more sense to ask for personal information, such as your birthday, than the confirmation number. Or a resend button for the booking number. 
This is not an advantage for us, because guests still call at night because they can't find the booking number. 

Hi @Jasmin H., 

I understand. Currently, in order to authenticate the guest we need to use a piece of information that MUST be attached to the guest/ reservation. If you check in a guest in person, there is no guarantee that you collected their birthday (and in some legal environments it is not obligatory at all), same with address or other personal details. 
That is why we currently can use the only data that we know for sure exist - which is the booking number. 

The team is however looking into other solutions how to deal with situations like you described, so we’ll hopefully be able to offer more options. 

Hope it helps :) 

hi @alzbeta skrabalkova I can only comment that adding that ‘resend confirmation’ button would be a very nifty and especially fast solution for this? 

Hey @mauritsbots, 

I’ll make sure to share this with the team for consideration :) 

Thank you!