22 problems · 21 fully documented
Systems problems in hotels arise at the interfaces between PMS, POS, CRM, payment and data protection, which is why a migration or rollout almost always affects more than the one system.
Two systems live, neither one trusted by the team.
The server in the basement still runs, but every vendor only talks about cloud.
Half board, spa and packages get organised around the system instead of inside it.
A letter from the new owner, a date, and suddenly the system switch is no longer a choice.
Saturday, 5 pm, the system hangs, and the hotline is closed until Monday.
Guest data lives in silos, so personalisation is impossible.
Twenty years of guest history sit in a system nobody can get them out of.
Channel manager, CRM, door locks, POS: every connection is its own contract.
No 360-degree view of the guest.
Billing and reconciliation are error-prone.
Dinner gets rung up at the bar, retyped at the front desk and hunted for at month end.
A wrong name on an invoice costs reception half an hour and the accountant an email.
Every guest writes down at check-in what they already entered when booking.
Ask the room number, find it on the list, tick it off. At nine the queue reaches the door.
Decisions take too long.
Outages disrupt guests and operations.
Investments happen ad hoc, not strategically.
Housekeeping, maintenance and reception have their own system: the group chat.
Requests get lost, replies take too long.
Licences keep running, the benefit is unclear.
The per-room price is right; nobody read the lines underneath.
These problems are in the catalogue but not yet fully documented. If one of them is yours, tell us. Cases are what turn a logged problem into a documented one.
Hospis from the network whose work covers this category.
Your problem isn't listed? Tell us your case