HospisHospis
Back

Support replies days later

Saturday, 5 pm, the system hangs, and the hotline is closed until Monday.

Typical for: leisure hotels with weekend arrivals and office-hours support · houses whose ticket replies take longer than the problem · operations with an international vendor and no German-speaking team

Documented by Hospis

Updated: 8 November 2026

How you recognize it

  • Support is available Monday to Friday, arrivals are on Saturday
  • Tickets get an automatic reply and then nothing for days
  • Reception keeps its own list of workarounds for known errors
  • The long-standing contact disappeared since the vendor grew or was acquired
  • German-language support exists only at certain times, or not at all
  • The contract says “support included”, but no deadline

Matching Hospi

Josef Walch

Josef Walch

Digitalisation · AI in operations · Systems · Lech am Arlberg
Works with protel · Mews · Mews POS · Smart Host
AdviseImplement

Knows support questions around a cloud PMS from the Mews rollout at Rote Wand.

Mapped to root cause
Response time in the contractPath to a humanInternal first responder
View profilePersonally vetted · independent match

Software that solved this problem

Tools appear here next to the problems they solved, marked as partners, with honest limits and the person who runs the rollout. No ranking.

B
PMSPartnerExample

Beispiel PMS

Implementation Hospi: Senior implementation consultant

The core system that finally puts arrivals, housekeeping and billing on one beat.

View partner profile

Which path fits your situation?

01

Diagnosis

390 € fixed price

A vetted Hospi analyses your situation in a structured way, in conversation and with a written result. Every statement clearly labelled: FACT, BENCHMARK, HYPOTHESIS or CONCLUSION. You get a concrete path, not a sales meeting.

  • A legitimate outcome is also: no engagement needed.
  • If an engagement follows, the diagnosis fee is fully credited.
02

Urgent support

Acute situation? Your case is reviewed with priority, with a response within 48 hours.

Cause fields and how to tell them apart

Support is a side note at purchase and the most important difference between two systems in operation. What is not agreed will not be delivered.

These fields are complete, and many properties get there on their own. That is what this page is for. The cost simply does not appear on an invoice: internal hours, a few attempts, and a season that keeps running in the meantime.

01

Response times were never agreed

How you spot it

The contract says “support included”. What that means (hours, language, response deadline, escalation) is written nowhere. The vendor delivers what it currently can; the house has no claim, only frustration.

The way out

Renegotiate support as a contract item: availability on the house's arrival days, response deadline for a system outage in hours, not days, German-speaking, with an escalation level. In writing. A vendor who will not commit to that should not claim it in the quote either.

02

The vendor has grown, the support hasn't

How you spot it

You used to know the developer's number. Today there is a ticket portal, a chat window and a queue. Acquisitions and rapid growth hit support first.

The way out

Clarify the path to a human: is there a fixed contact or a regional partner who knows the house? Many vendors work with implementation partners who react faster than headquarters. Have that person named in the contract.

03

The house has no emergency knowledge of its own

How you spot it

Every problem goes to support, including the ones reception could solve itself. The queue gets longer, and in a real outage preparation is missing: no offline plan, no list of critical functions.

The way out

Name an internal first responder who knows the system better than anyone else and can solve the ten most common faults. Plus an emergency sheet: how to check in when the system is down, how to catch up afterwards. Support then only gets what it really has to solve.

Frequently asked

What is a reasonable response time?
For a system outage: a reply within an hour, a fix or a workaround within a few hours. For normal questions: one working day. Anything beyond that is a reason for the next sales conversation with another vendor.
Does better support cost extra?
There are often support tiers at a surcharge. For a leisure hotel with Saturday arrivals the higher tier may be the right one. Compare: what does one arrival day without a system cost?
German-speaking support, does it really matter?
For reception on a Saturday evening: yes. For the back office during the week: less so. What matters is that the person with the problem can describe it in their own language.

Describe your situation

The problem context is automatically included, you do not need to repeat anything.

Problem
Support replies days later

We use your details only to answer your request. Details are in our privacy policy.

Related situations

PMS migration stalled mid-rollout

Two systems live, neither one trusted by the team.

View solution

Our PMS vendor was acquired and we're told to migrate

A letter from the new owner, a date, and suddenly the system switch is no longer a choice.

View solution

Our Wi-Fi and IT aren’t up to standard

Outages disrupt guests and operations.

View solution
See all problems