Maqetin emails the traveller who searched and did not book.
A traveller searches a route and leaves. Maqetin reads the search and the booking in your app’s events, and sends the search back a day later to anyone who has not booked.
Sample scene: a trip booking app in Singapore.
The journey starts when your app sends search.performed. It waits 24 hours, then checks whether booking.completed arrived since the person entered. If it did, they leave and no email goes. If not, the email goes.
Quote the search.
It repeats the route and the dates that were searched, and links back to them.
- Send the route and the dates. Send the destination and the dates with search.performed, and the email can print them.
- Choose the re-entry rule. A traveller who searches often can enter the journey once, or again after a number of days you set.
- Confirmations take the send API. A booking confirmation sent through the send API reaches people who opted out of marketing; a journey email skips them.
Hi Jane,
You searched Lisbon for 14 to 18 May yesterday. The link below opens that search again.
See your searchEvents to send.
Your app sends each one when it happens. The journey above uses the first two.
- search.performed
- A traveller searches a route and dates.
- booking.completed
- A booking is paid.
- trip.completed
- A trip ends.
- review.submitted
- A traveller rates a trip.
Templates.
No template is written for travel yet. The gallery lists the templates for other kinds of app.
Browse the templatesStart with the searches that did not book.
Book a demo and we'll show you Maqetin on booking journeys like yours.