Hotel communication mostly happens at the edges of a stay. A booking confirmation arrives by email. A pre-arrival message sends check-in details. A post-checkout survey asks how things went.
The middle — the part where the guest is actually in the hotel, in their room, deciding how to spend the next few hours — is largely silent.
That silence is not because hotels have nothing to say. It's because there's no obvious channel. Most hotels can reach a guest before arrival via the email on the booking. Reaching that same guest during their stay, without requiring them to open an app or hand over a phone number, is harder than it sounds.
Why the in-stay communication problem is structural
The tools hotels have for outbound communication — email, SMS, WhatsApp, messaging platforms — were built for pre-arrival and post-checkout. They work by collecting contact data during the booking flow, then using it to send messages on a schedule.
That model breaks down once the guest is in the building.
After check-in, the hotel often doesn't have permission to send SMS. Email inboxes are associated with planning and confirmation, not moment-to-moment awareness. And guests don't check their booking confirmation to find out what's happening at the hotel this evening.
The result is that hotel events, promotions, and announcements rarely reach in-house guests in a useful way. A spa promotion gets printed and stuck to the bathroom mirror. A live music night gets written on a whiteboard in the lobby. A restaurant deal for hotel guests gets mentioned at check-in, once, and is forgotten by the time the guest is hungry.
What hotels actually need to communicate during a stay
The announcements that matter to in-house guests fall into a few categories:
- Events happening on the property: live music, happy hours, poolside activities, chef's specials
- Practical information that changes: pool hours adjusted for maintenance, restaurant closed for a private event, Wi-Fi password updated
- Local recommendations: a restaurant nearby offering a discount to hotel guests this evening
- Operational reminders: check-out time, luggage storage options, late check-out availability
These are time-sensitive. A guest deciding where to have dinner at 6 pm is not going to find a flyer helpful if they saw it at 2 pm and forgot it. A pool closure announcement posted at the pool is useful only to guests who already made the trip.
The channel needs to reach guests in-room, at the moment they're planning, without requiring the hotel to have collected a phone number.
How the Guest Hub works for in-stay announcements
When a guest scans the QR code on the Room QR Card in their room, their browser opens the hotel's Guest Hub — a hotel-specific page that lives on the web, with no app download required.
The Guest Hub is already where guests submit service requests: a towel request, a maintenance report, a question for reception. Each request routes to the Staff Dashboard in real time. The same Guest Hub is where hotels publish announcements and events.
A hotel manager adds an announcement — tonight's live music, a spa offer running through the weekend, a pool closure tomorrow morning — directly in the Staff Dashboard. That announcement appears the next time any in-house guest opens the Guest Hub.
Because the Room QR Card is always present in the room, the hotel doesn't need to push a notification or collect contact information. The channel exists as long as guests are willing to scan. For guests already using the hotel guest request platform to get things done during their stay, opening the Guest Hub again to check what's on is a natural habit, not an extra step.
The add-to-calendar detail
For events with a specific time, guests can add them to their calendar directly from the Guest Hub in one tap.
This is a small feature with a disproportionate effect on attendance. A guest who adds "rooftop happy hour — 6 pm" to their calendar has made a lightweight commitment. They're more likely to show up than a guest who saw a flyer and thought "maybe."
No SMS. No email. No account. The guest decides at the moment they see the announcement, and the calendar entry keeps it visible until the time comes.
For hotels that run recurring weekly events — a live performance every Thursday, a Sunday brunch — the add-to-calendar option means guests on a multi-night stay can plan around the schedule without having to remember it.
Local businesses as a second announcement layer
The Guest Hub also includes Discover Near Us, where guests browse local businesses the hotel has chosen to surface: restaurants, tour operators, transfer services, local activities.
These are not ads or paid placements. They're the hotel's curated recommendations — the places the hotel would mention at the front desk if the guest asked.
Local businesses can update their listing with time-sensitive offers: a dinner special running tonight, a tour with last-minute availability, a discount for guests arriving from a partner hotel. When a guest submits a lead through Discover Near Us, that lead routes to the business in its own dashboard.
For a hotel that already sends guests to the same two or three restaurants every week, Discover Near Us makes those referrals trackable for the first time. The hotel sees how often guests clicked, which businesses they engaged with, and which recommendations generated real leads.
How this looks in a real hotel operation
A front office manager at a 90-room city hotel has a roster of partners: two restaurants offering hotel guest discounts, a walking tour company with morning departures, and a transfer service for airport runs.
Before the Guest Hub, those relationships existed as verbal recommendations at check-in. Some guests heard them. Most did not — because check-in is transactional, rushed, and the guest is carrying luggage and thinking about the room, not dinner.
With the Guest Hub, the hotel's event announcements and Discover Near Us listings are available at any moment during the stay, in the guest's browser, when they're in their room and actually planning. Staff in the same 90-room property handle guest service requests through the Staff Dashboard — a shared view where requests move from pending to in progress to completed with timestamps. The announcement feature sits in the same dashboard, updated by whoever manages it that day.
The operational ask is small: update the announcements when something changes. The guest-facing result is that in-house guests actually know what's happening.
What a pilot covers
A Stayhos pilot starts with 50 to 100 rooms. Each room gets a Room QR Card. Staff log in to the Staff Dashboard. The Guest Hub is live from day one.
Announcements and events can be added at any time after setup. Local partners can be added incrementally — starting with one or two businesses the hotel already recommends verbally, then expanding as the team gets comfortable with the dashboard.
No PMS integration is required to start. Hotels can optionally connect active stays to validate QR scans against checked-in guests, but that's an option rather than a prerequisite.
After two weeks, the hotel has real data: how many guests scanned, which announcements generated calendar saves, which Discover Near Us listings drove leads. That data is available in the Staff Dashboard as read-only aggregate analytics — no individual guest tracking, no PMS required.
A practical next step
If you manage a hotel and want to see how in-stay announcements work in practice, the Guest Hub demo runs on a fictional hotel with real interface features. You can see what a guest experiences after scanning a Room QR Card, what announcement display looks like, and what arrives in the Staff Dashboard when a service request comes in.
If a pilot sounds right for your property, contact Stayhos to talk through what a 50–100 room rollout looks like. Hotels that already run without a PMS can start the same week.