A guest asks for extra towels at 9pm. Somewhere, a member of housekeeping needs to find out about that request within the next few minutes, not at the next shift huddle. That's the entire problem hotel staff notifications are supposed to solve, and yet most of the advice available to independent hotel operators skips straight past it to a much bigger, much more expensive question: which native mobile app should we buy.
Native apps make sense for large chains with IT departments, device budgets, and a reason to build custom software. They make much less sense for a 40-room boutique property or a family-run independent hotel, where the honest options have usually been a walkie-talkie, a shared WhatsApp group, or an expensive PMS add-on that only half the staff actually use. None of those are really a notification system — they're workarounds. This post is about the option in between: staff getting real push notifications on their own phones without a native app, an app store, or a PMS.
Why native apps are the wrong default for most hotels
When a GM searches for how to notify staff about guest requests, most results assume a specific starting point: a dedicated app, built or bought, submitted to the App Store and Google Play, installed on hotel-owned devices. That path involves app store review timelines, ongoing app maintenance, and, in many cases, a requirement to purchase and manage phones or tablets for every staff member.
For a hotel already running lean on operations staff, that's not a minor cost. It's often the reason the project gets shelved entirely, and the hotel falls back to whatever informal channel it was using before — which is usually some mix of paper logs, radio calls, and a front desk agent physically walking to find someone.
There's a second, quieter assumption buried in a lot of that advice: that staff notifications need to be bolted onto a property management system. That works if a hotel has a modern PMS with an open ecosystem, but it excludes a large share of independent hotels running older or simpler systems, or no PMS at all. Stayhos works without a PMS, which means the notification problem doesn't have to wait for a PMS upgrade or migration project to get solved.
The installable web app, explained plainly
The alternative Stayhos uses is a progressive web app, usually shortened to PWA. It sounds technical, but the concept is simple enough to explain to a GM in one sentence: it's a website that behaves like an app once you add it to your phone's home screen.
There's no app store involved at any point. A staff member opens a link in their phone's browser, taps "add to home screen," and from then on there's an icon that opens like any other app — full screen, with its own icon, and critically, able to send push notifications the same way a native app would. No download step, no waiting on app store approval, no separate install file to manage.
This matters operationally in a few specific ways:
- No app store approval cycle. Updates to the Staff Dashboard roll out the way website updates do — immediately, without submitting a new build for review.
- No device management. Staff use their own phones. The hotel isn't purchasing, provisioning, or tracking a fleet of devices, and isn't responsible for enrolling anything in a mobile device management system.
- Push notifications still work. The "web app" part doesn't mean staff have to keep a browser tab open and watch it. Once installed, the Staff Dashboard can send a push notification the same way any app on the phone can, so a new request shows up as an alert even if the phone is locked.
What actually happens when a guest sends a request
Understanding the alert side is easier once you see the whole loop it's part of. A guest scans the QR code on their Room QR Card, which opens the Guest Hub in their phone's browser — no install or account needed on the guest's side either. Inside, they choose a category: towels, cleaning, maintenance, or reception help.
Because the guest reached the Guest Hub through a QR code tied to their specific room, the room number is resolved automatically. The guest never types it in, and there's no step where they could get it wrong. That single detail is what makes the alert to staff useful rather than just noisy — a maintenance request that already says "room 214" is something staff can act on the instant they read it, instead of a request that needs a follow-up call to figure out where to go.
That request is then auto-assigned based on role, shift, and, for housekeeping, room mapping. A maintenance issue routes to maintenance staff on shift. A housekeeping request routes according to which rooms are assigned to which attendant. The person who gets the push notification is already the right person to handle it, not just whoever happened to be near the radio.
From there, the request is tracked through a visible lifecycle — pending, in progress, completed — on the Staff Dashboard, and that status is guest-visible too, so the guest isn't left wondering whether anyone saw their request.
Getting staff onboarded without IT involvement
The onboarding side follows the same logic as the notification side: no app store, no manual account creation by an administrator for every hire. Staff join through a QR invite link. A manager generates the invite, a new staff member scans it, and they're added with a role and shift assignment.
From the moment that setup is complete, the staff member starts receiving requests that match their role and shift — nothing further to configure, no separate step to "turn on" notifications beyond the normal permission prompt a phone shows when an installed web app asks to send push notifications.
This also solves a practical turnover problem specific to hospitality. Housekeeping and front-desk staff change more often than management teams would like, and a notification system that depends on IT provisioning a device or manually adding a user to a backend system becomes a bottleneck exactly when a hotel needs coverage fastest. A QR invite link removes that bottleneck: onboarding a new hire takes about as long as it takes them to scan a code and fill in their name.
Where this fits with the rest of hotel operations
Staff notifications don't exist in isolation — they're one half of the request loop that starts at the Room QR Card and ends with a completed task the guest can see. Hotels that have looked at why a guest request system stops working often find the failure point wasn't the request itself, but the gap between a request being logged somewhere and a specific staff member actually finding out about it in time. A push notification that reaches the right person's phone, tied to a specific room, closes exactly that gap.
It's also worth being clear about what this setup is not. It is not a native mobile app distributed through an app store, and Stayhos does not offer one — a native app remains on the roadmap rather than something live today. It is not an automated dispatch system that resolves requests on its own; a person still has to see the alert and do the work. What it removes is the friction between a guest asking for something and a staff member finding out, without asking a small hotel to take on app store management or a device fleet to get there.
A practical next step
If you're weighing staff notification options for a property that doesn't have the budget or IT support for a native app, the Guest Hub and Staff Dashboard demo shows the full request-and-alert loop end to end, from a guest scanning a Room QR Card to a staff member receiving the push notification.
To talk through onboarding your own staff with QR invites, or to ask how this fits with the systems you already run, contact Stayhos directly.