Managed IT
What hotel IT support actually covers, and what it doesn't
What hotel IT support covers: systems in scope, who owns the PMS and door locks, contract tiers, exclusions and how response targets really work.
IT support for hotels covers the day-to-day running of the systems a property trades on: guest Wi-Fi, the network, back-office, telephony and the service desk that fields every fault. MicroNet Global, a hospitality IT specialist operating across 15+ countries, delivers that cover and coordinates the specialist vendors who own the PMS, EPOS and door locks.
Most proposals are vague about the second half of that sentence, and that is where hotels get caught out. A hotel runs a dozen platforms with a dozen different owners, and the value of a good partner is as much in knowing who to call as in fixing things directly.
What is hospitality IT support?
Hospitality IT support is a managed service that keeps a venue's technology working while it trades. It normally combines a service desk staffed to match trading hours, proactive monitoring of the network and critical interfaces, onsite engineering when a fault cannot be cleared remotely, and coordination of the third-party vendors who own systems such as the property management system, EPOS and electronic door locks.
The systems in a hotel, and who owns each one
A 120-room hotel typically runs between eight and fifteen distinct technology platforms, and almost none are owned end-to-end by the IT support provider.
| System | Typical owner | Who you call first |
|---|---|---|
| Property management system (PMS) | PMS vendor, usually cloud-hosted | Service desk triages, escalates to vendor for application faults |
| EPOS / till estate | EPOS vendor | Service desk for hardware and network, vendor for the application |
| Payment terminals | Acquirer or payment provider | Payment provider; IT partner confirms connectivity first |
| Door locks and access control | Lock manufacturer and their integrator | Lock vendor; IT partner owns the server and network path |
| Guest Wi-Fi | Managed IT partner, sometimes the ISP | Managed IT partner |
| In-room entertainment and casting | IRE vendor | IRE vendor; IT partner owns the VLAN and bandwidth |
| Back-office, Microsoft 365, file and print | Managed IT partner | Managed IT partner |
| Telephony and PBX | Telephony provider or IT partner, depending on contract | Whoever holds the platform contract |
| CCTV, NVR and interfaces | Security integrator | Integrator; IT partner owns storage and network |
| Structured cabling and containment | Cabling contractor | Contractor, under installation warranty |
| Booking, channel manager, revenue tools | SaaS vendor | Vendor; IT partner owns identity and access |
Coordination is the job, not a cop-out
When a reception terminal cannot load a guest folio, the fault could be the PMS cloud service, the internet circuit, the local switch, the workstation, DNS or a certificate. The guest at the desk does not care which. A support desk is measured on whether it takes ownership, proves where the fault sits and drives the right vendor to fix it.
Ask how vendor escalation works in practice. Do they hold your vendor portal logins? Will they open the ticket themselves, or send you the reference and step back? The difference between "we'll raise it with them" and "we own it until it's closed" is most of the value in a [[24/7 managed IT support]{.underline}](about:blank) contract.
The four tiers of a hospitality support contract
Support is usually priced across four layers. Knowing which layer a line item sits in tells you what you are buying.
**Remote service desk.** Ticket intake by phone, email and portal, triage and remote fix. This is where most tickets end: MicroNet Global resolves around 90% of network faults remotely without a site visit, on a desk running 24/7 across UK, US and UAE offices.
**Proactive monitoring.** Agents and probes watching circuits, switches, access points and critical services, raising tickets before the duty manager does. Monitoring only earns its keep when someone is rostered to act on the alert at 3am.
**Onsite escalation.** An engineer attending when the fault is physical: a dead switch, a failed access point, a till that will not power on. Check what the contract says about travel, out-of-hours attendance and included visits.
**Project work.** New sites, refurbishments, migrations, refresh programmes. This is almost always separate, and should be, because it needs [[dedicated IT project management]{.underline}](about:blank) rather than being squeezed between support tickets.
What sits outside a support contract
Being clear about exclusions early prevents the argument later. A standard hospitality support agreement does not normally include:
- **Hardware capital cost.** Switches, access points, servers, tills
- and workstations are capex. Support keeps them running; it does not
- replace them at end of life.
How response targets actually work
Three numbers get confused in almost every proposal, and operators sign up to the wrong one.
| Term | What it means | What to check |
|---|---|---|
| Response target | Time until a human acknowledges the ticket and begins work | Whether it is a person or an autoresponder |
| Resolution target | Time until service is restored | Whether it is a target or a contractual commitment |
| Workaround | Service restored by another route, ticket stays open | Whether a workaround stops the clock |
| P1 definition | The priority level that triggers the fastest targets | Exactly which scenarios qualify as P1 |
How to read a support proposal
Five questions separate a serious hospitality proposal from a generic MSP template.
1. Which systems are in scope by name, and which are coordination-only?
2. What exactly is a P1, and does a dead payment estate qualify?
3. Is out-of-hours cover a rota of engineers, or an on-call phone?
4. How many onsite visits are included, and what triggers a chargeable one?
5. Who holds the vendor relationships, and will the partner escalate for you?
A partner working across [[hotels and resorts]{.underline}](about:blank) answers those without hesitation, because their existing clients already asked them. Guest-facing systems deserve most scrutiny, and [[guest Wi-Fi in hotels and restaurants]{.underline}](about:blank) is usually the first place a weak contract shows. To have an existing arrangement reviewed against those questions, [[talk to MicroNet Global]{.underline}](about:blank).
Frequently asked questions
It includes a service desk for fault reporting, remote fixes, monitoring of the network and critical services, onsite engineering when a fault is physical, patching and security updates for managed devices, user administration, and coordination with the vendors who own the PMS, EPOS and door locks. Hardware purchases, vendor licence fees and new-site projects are normally separate.
Written by the MicroNet Global team. If you are working through any of this for your own estate, the specialists here are happy to talk it through.