Fill your quiet hours and get repeat orders.
A delivery customer orders a few times a week, and almost all of it lands at weekday lunch or Friday to Sunday evening. You cannot widen those peaks, and paying for orders inside them changes nothing. What is worth paying for is a Tuesday at 3pm, when your couriers are idle.
Almost every order lands in the same few hours.
Most orders land at weekday lunch and between Friday evening and Sunday night. Those hours are already busy, and a discount inside them is money spent on an order you were going to get anyway.
Reading the chart: each bar is one day. Monday to Thursday are low and roughly equal. Friday to Sunday are about three times taller and already at capacity, so an incentive there buys an order you were getting anyway. The band marks the weekdays worth paying for.
Build a cuisine collection, a lunch streak and off-peak missions by zone.
A cuisine-exploration collection
Repeat customers narrow. One small mission per cuisine, each satisfied by a single order. The minimum basket line stops the reward paying for tiny orders.
A weekday-lunch streak
A streak counts strictly consecutive calendar days. You write the condition for whether today counted. Point it at a rolling week and the run survives the days nobody orders.
Off-peak missions targeted by zone
Your dispatch system is the only thing that knows which slots are slack. It stamps that
on the order as delivery_window, and the condition filters on it. The reward
is points, not a discount.
The same engine, set up for another industry.
E-commerce
Orders in bursts, with weeks of silence between them.
Read the pageMobility
A commute you can predict, and demand worth moving.
Read the pageCollections
How a themed set is assembled from missions.
Read the pageSend us one order event.
Send us the shape of a single order event. We will build the cuisine collection and an off-peak mission in a test account while you watch.