Message every stage.
Once your PMS is connected, each reservation triggers the right message — a welcome, a note before arrival, a check-in during the stay and an invitation after checkout. Use it so guests hear from you at the moments that matter, without anyone remembering to send anything.
Sent on the reservation.
A scheduled WhatsApp message goes out partway through the stay, so the question reaches every guest without anyone remembering to send it. Replies land in the same inbox as every other guest conversation, so answering is not a separate job for anyone.
Complaints become tasks.
When a guest reports a problem, your team turns the message into a task for the right department, attached to the room and tracked from New to Completed — it does not stay as an alert somebody has read. The guest gets the fix before checkout, and the room keeps the record, so if the same air conditioner is reported twice you can decide to replace it.
Invite after checkout.
After checkout, a scheduled message sends guests who had a good stay a short thank-you and a direct link to the platform they actually booked on — Booking, TripAdvisor or Google. Most hotels never ask at all, so the only guests motivated enough to write a review unprompted are the annoyed ones.
Every stage covered.
Journey campaigns sit on the same engine as your inbox, tasks and rooms, so it turns into work rather than into a report nobody opens.
Welcome on booking
The guest hears from you as soon as the reservation lands, with your details and how to reach the hotel. The first message is not one asking for something.
Before arrival
A note a few days out with arrival times, directions and the extras they can add. It reaches them while they are still planning the trip.
In-stay check-in
Partway through the stay you ask how it is going, while there is still time to fix whatever they mention. A problem heard on day two is one you can still solve.
Straight to the right team
A complaint becomes a task for housekeeping, maintenance or the front desk, with an owner and a room. It stops being everyone’s problem and therefore nobody’s.
After checkout
Guests who had a good stay are invited to leave a review or join your loyalty programme. A guest who told you something went wrong is not asked to rate it.
Driven by the reservation
The PMS decides who gets which message and on what day, so nobody builds a list by hand or remembers to press send.
Messages become work.
Other tools notify you that a guest is unhappy. Here the complaint becomes a task with an owner, a room and a status, so you can prove it was actually fixed.
The question, the complaint and the thank-you are the same thread on the guest's own channel. Nobody is asked to open a survey tool or download an app.
One price per hotel, with no charge per room, per user or per survey sent.
It runs on top of the PMS you already use, in the same inbox as guest communication.
Common questions.
When are guests contacted?
On the dates the reservation sets: a welcome when the booking lands, a note before arrival, a check-in partway through the stay, and an invitation after checkout.
How is the message sent?
As a WhatsApp campaign, using an approved WhatsApp template and a connected WhatsApp Business account. The Log records what actually went out and to whom.
What happens when a guest reports a problem?
Your team turns the message into a task for the department that has to fix it, attached to the room and tracked from New to Completed.
Do unhappy guests get asked for a review?
No. A guest who told you something went wrong is not sent a review request after checkout. The invitation goes to guests who had a good stay.
Do guests need an app or a login?
No. It is a message on the channel they already use, and they reply the same way they would reply to anything else.
Can I run it across several hotels?
Yes. Campaigns are scoped by property, so each hotel runs its own journey without the lists crossing.
See it on your hotel.
Book a 30-minute demo and we will set up the mid-stay question on your property. Or start free and set it up yourself.