Maqetin emails people who got a quote and have not bought.
Someone sees a price and leaves. Maqetin reads the finished quote and the purchase in your app’s events, and links back to the saved quote of anyone who has not bought.
Sample scene: a car insurance app in London.
The journey starts when your app sends quote.completed. It waits 24 hours, then checks whether policy.purchased arrived since the person entered. If it did, they leave and no email goes. If not, the email goes.
The quote is the story.
It says the quote is saved and until when it is valid. The journey of this email is the quote follow-up template.
- Print the quote. Send the product and the date it is valid until with quote.completed, and the email can print both.
- Stop when they buy. The journey looks for policy.purchased since the person entered, so nobody who bought gets the email.
- Policy documents take the send API. A policy document or a renewal notice sent through the send API reaches people who opted out of marketing; a journey email skips them.
Hi John,
Your quote from yesterday is saved, with the details you entered. It is valid until Sunday.
Return to your quoteEvents to send.
Your app sends each one when it happens. The journey above uses the first two.
- quote.completed
- A person is shown a price.
- policy.purchased
- A person buys a policy.
- quote.started
- A person opens the quote form.
- renewal.approached
- Your system sends it before a policy renews.
The insurance template.
Start with the quotes nobody bought.
Book a demo and we'll show you Maqetin on quote journeys like yours.