Maqetin emails guests before they arrive and after they leave.
A stay has two dates your system knows: the arrival and the checkout. Maqetin starts an email from each event, and asks for a review only from guests who have not left one.
Sample scene: a hotel booking app in London.
The journey starts when your app sends stay.checked_out. It waits 1 day, then checks whether review.submitted arrived since the person entered. If it did, they leave and no email goes. If not, the email goes.
The stay sets the dates.
It thanks the guest for the stay and asks for two minutes. The journey of this email is the review request template.
- Your system sets the arrival. A wait runs from the moment the person entered, so an email days before arrival starts from an event your booking system sends then: arrival.approached.
- One email needs no wait. A journey with a trigger and one email sends as soon as the event arrives, as the pre-arrival template does.
- Link the form. Send the review link and the property with stay.checked_out, and the email can link to the form.
Hi Mary,
Thank you for staying with us for three nights. If you have two minutes, tell the next guest what you thought.
Leave a reviewEvents to send.
Your booking system sends each one at the moment it knows. The journey above uses the first two, and the third starts the pre-arrival template.
- stay.checked_out
- A guest checks out.
- review.submitted
- A guest leaves a review.
- arrival.approached
- Your booking system sends it a few days before the arrival.
- booking.confirmed
- A guest books a stay.
The hospitality templates.
Start with the day after checkout.
Book a demo and we'll show you Maqetin on guest journeys like yours.