Maqetin emails customers between one delivery and the next order.
A customer’s order arrives and the next one does not follow. Maqetin reads the delivery and the next order in your app’s events, and emails the customers who have not ordered again.
Sample scene: a grocery delivery app in Singapore.
The journey starts when your app sends order.delivered. It waits 14 days, then checks whether order.placed arrived since the person entered. If it did, they leave and no email goes. If not, the email goes.
The order makes the email.
It offers the last order again in one tap. The journey of this email is the reorder template.
- List what they ordered. Send the items with order.delivered, and the email can list them.
- The wait runs from the delivery. The 14 days count from the moment the person entered the journey, which is the delivery.
- Receipts take the send API. A receipt or a delivery update sent through the send API reaches people who opted out of marketing; a journey email skips them.
Hi Jane,
Your last order was two weeks ago. Everything in it is in stock today, and it can be with you by 7pm.
ReorderEvents to send.
Your server sends each one when the order moves. The journey above uses the first two.
- order.delivered
- An order reaches the customer.
- order.placed
- A customer pays for an order.
- order.cancelled
- An order is cancelled before it arrives.
- cart.updated
- A customer changes the basket.
The food delivery template.
Start with the customers who ordered once.
Book a demo and we'll show you Maqetin on reorder journeys like yours.