Improvement proposal for system downtime situations

I wanted to propose an improvement and share a comment after the system crash that lasted several hours. In our case, as we did not have 24-hour reception, this caused us quite a few complications: some guests could not access the door opening codes because they depended exclusively on the link, and others could not make pending payments for the same reason. This forced us to travel to the accommodation to attend to them in person.

As a result of this situation, we have discovered that from Paycomet we can generate payment links directly, without depending on the Hotelgest link, which already represents an important advance.

Our suggestion is to be able to include the opening codes (in our case TESA) as a column within the arrivals report, and that this can be programmed to be sent automatically every X amount of time. This would give us a backup solution in case of system downtime, as we could at least have a document accessible for quick action, without the need to log into the system.

As this would cover only the arrivals, perhaps the most complete would be areport with all the accommodation units, including both the arrivals of the day and the clients that are already accommodated, and that in that report the opening codes would also appear. This way, we would easily know where each client goes and what code they need to access.

We know that these are specific situations, but having a plan B makes the difference when we work with autonomous check-in without 24h reception. Hopefully this option can be considered as a possible improvement of the system.

Best regards and thanks, as always.