Feature
Automated guest messaging for hostels
The right message goes out at the right moment in a guest's stay — check-in link, reminder, guidebook link, review request — without anyone typing any of it by hand. Guests pick their own channel at check-in, and every message respects that choice.
What is automated guest messaging for a hostel?
Automated guest messaging means sending journey messages — check-in links, reminders, the guidebook link, review requests — on a schedule tied to the booking, instead of messaging each guest by hand. Door codes are never sent by message: they appear only in the guidebook, which opens once the guest's own online check-in is complete. In EZ2Stay, the guest chooses a preferred channel (WhatsApp, SMS, email, or no proactive notifications) at Step 1 of online check-in; messages go out on that channel — WhatsApp from a linked device on the property's own number, SMS through an SMS gateway, or email — with an automatic fallback if delivery fails and delivery tracked per message.
What does it do today — and where does it stop?
Every capability with its honest limit and its status: Live, Beta or Roadmap.
| Capability | Limit | Status |
|---|---|---|
| Automated journey messages: check-in link, reminders, guidebook link, review requests | timing is tied to the booking's own schedule, not freely adjustable per message | Live |
| Guest-chosen preferred channel: WhatsApp, SMS, email or no proactive notifications | the owner can hide the choice and set one default channel instead | Live |
| Automatic fallback chain on delivery failure | retries first, then switches to the guest's fallback channel; a final failure shows in the owner's admin feed | Live |
| Transactional vs marketing consent kept separate | refusing marketing stops every promotional message; check-in links and confirmations still arrive | Live |
| Door codes never travel by message | the code is shown only in the guidebook, after the guest's own online check-in | Live |
| Sent in the guest's preferred language when known | online check-in and the guidebook run in 31 languages today; more languages are on the roadmap | Live |
How does it work, step by step?
The booking arrives
EZ2Stay knows the guest, the dates and which messages the stay will need, before the guest ever opens the check-in link.
The guest picks a channel
At Step 1 of check-in, the guest chooses WhatsApp, SMS, email, or no proactive notifications at all.
Journey messages fire automatically
Check-in link, reminders, the guidebook link once check-in is complete, and a review request after the stay — each sent on the guest's chosen channel.
Delivery is tracked
Sent, delivered, read and failed states are logged per message; a failed send retries, then falls back to the guest's configured fallback channel.
The owner sees what needs attention
Messages that still fail after retries and fallback show up in the owner's admin feed, so no time-sensitive update is lost.
What can the owner configure?
Defaults you get on day one, and what stays fixed by design.
| Setting | Default | Who can change it |
|---|---|---|
| Whether guests choose their own notification channel | guests choose (WhatsApp, SMS, email or none) | Owner — can hide the choice and set one default channel |
| Fallback channel after delivery failure | SMS | Not configurable — system default |
| Marketing consent for promotional messages | off until the guest opts in | Guest — kept separate from transactional consent |
| Where the door code appears | only in the guidebook, never in a message | Not configurable — by design |
| Message language | guest's preferred language when known | Not configurable — follows the guest's language |
Where does it run in production?
In production · Popcorn Hostel, Bucharest
This messaging flow runs at Popcorn Hostel, Bucharest — 49 beds, 15 smart locks — on WhatsApp from a linked device, SMS and email. Door codes stay in the guidebook only.
Read the Popcorn Hostel case studyNot a fit if
- You want to message guests manually from a shared inbox — EZ2Stay automates the journey messages; it isn't a live chat inbox.
- You need guest-facing content in many languages today — check-in and the guidebook run in 31 languages; more languages are on the roadmap.
- You want to message guests regardless of their preference — EZ2Stay always enforces the guest's chosen channel, including a 'no notifications' option.
FAQ
Guest messaging — questions operators ask
Which channels can guests choose for messages?
WhatsApp, SMS, email, or no proactive notifications at all — chosen at check-in Step 1, and changeable later from the guidebook.
What happens if a WhatsApp message fails to deliver?
It retries automatically, then falls back to the guest's configured fallback channel. A message that still fails shows up in the owner's admin feed.
Do guests who choose 'no notifications' miss anything critical?
No. Door codes are never sent by message anyway — they appear only in the guidebook, which opens after the guest's own online check-in. Everything else is also available anytime in the guidebook.
Can guests skip marketing messages without losing operational ones?
Yes. Marketing consent is separate from transactional consent — refusing marketing stops every promotional message, while check-in links and confirmations keep arriving.
Are door codes sent by WhatsApp, SMS or email?
No. The 4-digit code is generated on the arrival day at 07:00 property time and shown only in the guidebook, which opens once the guest has completed online check-in.
Can guests get messages in their own language?
Partly — messages use the guest's preferred language when it's known. Online check-in and the guidebook run in 31 languages today; more languages are on the roadmap.
Run your hostel without a front desk
EZ2Stay is in closed beta. Request access and we'll onboard your property — typically live in 1–2 weeks, with the channel manager and PMS included.