Maqetin emails guests who have not booked again.
A guest visits and a month passes with no booking. Maqetin reads the visit and the next booking in the events your server sends, and emails the guests who have not booked again.
Sample scene: a restaurant booking app in Austin.
The journey starts when your app sends visit.completed. It waits 30 days, then checks whether reservation.booked arrived since the person entered. If it did, they leave and no email goes. If not, the email goes.
The visit happens off the screen.
It gives one reason to return: what is new on the menu.
- Your server sends the visit. Maqetin does not read a booking or till system. Your server sends visit.completed when the system records a visit.
- Stop when they book. The journey looks for reservation.booked since the person entered, so a guest who booked within the 30 days gets no email.
- Print the location. Send the location with visit.completed, and the email can say which restaurant the guest visited.
Hi John,
You came in for dinner last month. The autumn menu starts Thursday, with the mushroom risotto back on it.
Book a tableEvents to send.
Your server sends each one when your booking or till system records it. The journey above uses the first two.
- visit.completed
- A guest has eaten and paid.
- reservation.booked
- A table is booked.
- reservation.cancelled
- A booking is cancelled.
- order.placed
- A guest pays for an online order.
Templates.
No template is written for restaurants yet. The gallery lists the templates for other kinds of app.
Browse the templatesStart with the guests who came once.
Book a demo and we'll show you Maqetin on guest journeys like yours.