The connection is back, but the temporary records cannot be put away yet. Colleagues accepted bookings, handled payments and arranged rooms during the disruption. The system still needs to catch up with what happened at the property.
Keeping guests looked after took judgement and teamwork. Recovery deserves an equally clear handover, so the next shift can build on that effort rather than reconstruct it from the beginning.
The guests were looked after. The work your colleagues recorded deserves the same care.
Separate confirmed facts from your property's situation
Preno's 6 November update described its partner SU/STAAH's security incident and service restoration. Preno stated that its customer data was not compromised. [1]
This does not establish that every outage is an attack or every connected hotel suffered a data breach. Separate August research by ITOCHU examined phishing and hotel-account takeover, not the same incident. [2]
The framework below is MythAsia's general operational guidance, not a vendor-specific recovery procedure. Reconnection, automated jobs and synchronisation changes should follow the property's approved arrangements and instructions from its provider or authorised technical team.
Give reception and record-keeping a shared starting point
Identify the unavailable function: channel synchronisation, PMS, payment, keycards or an interface between them. One platform being online does not establish that every connected step is working.
Use the hotel's approved contingency process. Record the minimum booking reference, action time, confirmed status, operator and outstanding work needed for reconciliation, in an approved location with appropriate access. Do not put passwords, API keys or full payment-card details into the handover log.
When a booking, payment or room status cannot be reliably confirmed, escalate to an authorised person. Do not bypass required identity, payment or room checks to clear a queue, or assume a kiosk can replace an unavailable service offline.
Reconcile four different states after restoration
Assign a reconciliation owner. Confirm the affected period and restored service scope with the provider. Match original booking references against approved temporary records; the hotel must define the evidence and owner for each category below.
Booking: already created or still pending?
Compare channel confirmations, PMS entries and temporary records. Check whether a reappearing booking matches one already created manually before acting. Track amendments, cancellations and pending items separately; a synchronised entry is not automatically a new reservation.
Payment: verified, unverified or not collected?
Use authorised transaction evidence to reconcile room charges, deposits, refunds and processing times. Missing on-screen data does not prove non-payment. Do not charge again solely because a field is blank. Refer uncertain transactions to the authorised owner and relevant provider.
Rooms and keys: does the system match the property?
Compare actual arrivals, departures and housekeeping status with PMS records. Verify key validity through the hotel's approved process. Do not arbitrarily move rooms, issue duplicate cards or reset an occupied room simply to make the records appear tidy.
Handover: what remains unresolved?
Separate confirmed results from open questions. Every open item needs a next action, owner, next check time and escalation route, rather than just 'system issue'. Apply the hotel's existing priority and authority rules when guests are waiting.
Leave the next shift a record it can use
Copy these fields into the property's approved handover record. This is not a collection form for identity documents, passwords or card details. Collection, access and retention remain subject to the hotel's policies.
- Item / booking reference — minimum necessary information
- Incident period and last check time
- Confirmed result and supporting evidence
- What remains unconfirmed
- Next action and authorised owner
- Next check time / escalation contact
Have the designated person record closure evidence and time when an item is resolved. Keep unresolved items visible; do not turn an unknown into 'complete' merely to close a shift.
When can reconciliation be considered complete?
The responsible people should confirm the relevant booking, payment and on-site states have been checked. Unresolved items still need owners and next actions. Validate the restored journey within the approved scope and test where required before resuming related automated jobs. A technical restoration statement and the hotel's operational reconciliation are different confirmations.
Review temporary changes to notices, payment arrangements, website entry points and operating instructions. Decide which should remain, be withdrawn or be handled by the provider. Do not copy another property's recovery steps into a different configuration.
Debrief with colleagues: which record was hard to find, which responsibility was unclear and what could be prepared earlier? Capture the experience of keeping the hotel running without turning the review into a search for one person to blame.
Where can MythAsia help scope the workflow?
A hotel self check-in or automation assessment starts with reservations, PMS, payment, keycards and staff takeover. We map dependencies, exception ownership and the evidence that needs checking. Integration, support, training and recovery cooperation must be confirmed for each property.
This article does not establish that MythAsia can keep operating through every channel manager outage. It offers no guarantee against attacks, downtime, missing records or financial loss. Technical investigation and incident handling belong with the relevant providers and the hotel's authorised specialists.
Explore the manager's operating guide, actual product workflow and case evidence. Bring one recurring recovery handoff to an assessment; there is no need to prepare an entire procurement checklist first.
Questions managers ask
Can all automation restart as soon as login works?
Login alone is insufficient evidence. Confirm which services are restored, complete the property's approved validation and reconciliation, and have the authorised owner decide on the relevant operations.
Does missing payment information mean the guest has not paid?
Not necessarily. Verify through authorised transaction evidence and distinguish collected, uncollected and unknown states before taking further payment action.
Can a kiosk replace a channel manager recovery plan?
Do not assume so. A kiosk may depend on PMS, network, payment and keycard interfaces. Verify the property's configuration and its staffed alternative.
Continue to workflow and evidence
Bring your PMS, channel manager and keycard setup, plus one handoff that is easy to miss. Clarify dependencies and responsibilities before deciding what to change.
Book a hotel arrival workflow assessment ↗