The guest portal.

Identify instead of log in.

Booking number, email address and last name, all three together. If they match, the guest sees their booking. There is no password to forget.

Anyone who no longer has the number requests the confirmation again with email and last name. The server slows down guessing, and the reply never reveals whether a booking exists.

What the guest handles themselves.

View dates and room, see the open amount and pay it by card, request the confirmation again, download the stay as a calendar entry, receive the self check-in link by email. And, if it must be, cancel the booking.

Additional payment only covers what is open, and the amount comes from the stored booking. A cancellation requires a reason and reaches you with a notification.

Check in before the guest arrives.

Seven days before arrival, self check-in opens. The guest clicks the button in the pre-arrival email and enters the registration data: for themselves and for everyone travelling with them. Plus the planned arrival time.

Afterwards the booking in the property shows: self check-in received, with all data. The front desk reviews and takes it over instead of typing on arrival day. You switch self check-in on in the widget settings; before that there is neither link nor button.

The fields the registration needs.

Date and place of birth, nationality, country of residence, document type and number, issuing country, optionally the tax code. For fellow travellers the shorter list. Exactly what the report to province and police requires.

If your tourist association offers the South Tyrol Guest Pass, self check-in asks for consent per person. Never pre-ticked.

What it is not.

No portal with login, no app, no chat. A guest should handle their booking in two minutes and leave the page again. Anything that takes longer belongs in a conversation with your property.