What Happens When Your PMS Breaks at 6pm on a Saturday
Peak arrivals are a weekend evening. In-hours support is a weekday morning. That gap is the one worth asking about.
The gap nobody prices in
Check-in peaks between about 4pm and 8pm, and Saturday is the busiest night of most weeks. Standard support hours are Monday to Friday, roughly nine to six, frequently in a different timezone.
Put those two facts together and the conclusion is uncomfortable: for a large share of the hours when a hotel most depends on its PMS, the people who maintain it are not working. That is survivable with a duty manager and a fallback process. At a small property, where the person calling support is also the person checking guests in, it is the whole problem.
Three things to check before you need them
The status page. Ask for the URL during evaluation. A public status page is a vendor agreeing to be caught out, and its incident history is the most honest document they publish. Read the last twelve months: how often, how long, and — most revealing — how quickly incidents were acknowledged rather than resolved.
The out-of-hours path. Not "do you have emergency support" but what specifically counts as an emergency, how it is raised outside business hours, and what response is committed to. If the answer is a monitored inbox, you have your answer.
What still works when the connection does not. Most small-hotel "outages" are not the vendor at all — they are hotel wifi, an ISP, or a power cut. Ask what degrades gracefully and what stops dead, because that determines whether you are running a manual desk for ten minutes or for the evening.
The paper fallback that takes fifteen minutes to build
Every small property should have one, and almost none do. It is not sophisticated.
Print tomorrow’s arrivals list at the end of each night audit, with names, room assignments, rates and balances. Keep the current in-house list beside it. That single sheet lets a front desk check guests in on paper and reconcile later, converting a systems outage into an administrative annoyance.
Add the vendor’s emergency contact route and status page URL to the same folder, along with which of your staff has the authority to escalate. Fifteen minutes of preparation, and it never expires.
Judging the recovery, not the incident
Every hosted system has incidents. Vendors that claim otherwise are either new or not looking. What actually distinguishes them is the behaviour afterwards.
Was it acknowledged before customers reported it, or after? Was there an update while it was unresolved, or only once it was fixed? Did anyone explain what happened, in language a hotelier can read? A vendor that communicates badly during a thirty-minute outage will communicate badly during a four-hour one — and you are choosing which of those experiences you want years of.
Where Frontdesko sits
The honest version: incidents happen here too, and the useful questions are the ones above rather than any uptime number on a marketing page.
What is different is the access. Support is not a tier, so there is no queue position to buy your way out of, and the contact page carries a direct phone number and live chat rather than only a form. The published email target is four hours, and the people answering came out of hotel operations, so an evening call about a stuck check-in starts from the operational problem rather than from a script.
The rest is preparation, and it is on all of us: build the paper fallback, know the escalation route, and ask these questions of every vendor you shortlist — including this one. The full pre-purchase checklist is the place to start.
Frequently asked questions
What should a hotel do if the PMS goes down during check-in?
Fall back to the printed arrivals list from the last night audit — names, rooms, rates and balances — check guests in on paper, and reconcile once the system returns. Raise the incident through the vendor’s out-of-hours route and check their status page to see whether it is a known issue.
How do I judge a PMS vendor’s reliability?
Read twelve months of their public status page rather than the uptime figure on their pricing page, and pay attention to how quickly incidents were acknowledged and updated, not just resolved. Communication during an incident predicts the experience far better than any headline number.
Why is PMS downtime worse for a small hotel?
A large property has a duty manager, a second terminal and a documented fallback, so the outage degrades service. At a small property the person contacting support is the front desk, so the outage stops service entirely.
Does Frontdesko offer out-of-hours support?
The contact page lists a direct phone line and live chat alongside a four-hour email target, and support is not sold as a paid tier, so there is no faster queue reserved for larger accounts. As with any vendor, ask for the specifics of the out-of-hours path during evaluation.