A guest who ordered once, months ago, and never came back looks lost on paper. In practice, a short, specific win-back message often recovers a real share of that group, since many lapsed guests simply drifted rather than made an active decision to stop.
Defining "Lapsed" Clearly First
A reasonable definition varies by vendor type, a coffee shop's lapsed guest looks different from a catering company's, but picking a specific window, say 60 or 90 days without an order, gives the campaign a clear target list to work from.
A vendor with genuinely frequent guests, like a coffee shop where a regular might order several times a week, may need a shorter window, like 30 days, to catch a real drop-off early. A vendor with naturally infrequent orders, like a caterer whose average guest only books a few times a year, needs a much longer window before absence actually signals anything meaningful.
What a Simple Campaign Actually Includes
- Identify guests who haven't ordered within the chosen lapsed window.
- Send a short, specific message referencing something they've ordered before, if known.
- Include a clear, simple way to order again, not a generic link to the homepage.
- Track whether the specific message coincided with an order from that guest.
None of these four steps require anything beyond the guest list a vendor already has. A win-back campaign built this simply can run in an afternoon, without any dedicated software purchase or a marketing agency's involvement, which makes it one of the more accessible tactics available to a vendor of any size.
Keeping It Low Pressure
A win-back message reads better as a genuine "we noticed and wanted to reach out" than as a hard sell. An overly aggressive discount can feel like a bribe rather than a reconnection, particularly if it arrives paired with heavy pressure to act immediately.
A message that simply asks whether everything was alright with the last order, without any offer attached at all, can sometimes outperform a discount-led message, since it reads as genuine curiosity about the guest's experience rather than an attempt to buy back their business.
Segmenting Lapsed Guests by Their Own History
Not every lapsed guest lapsed the same way. A guest who ordered ten times over a year and then stopped is a meaningfully different case from a guest who ordered exactly once and never returned, and treating both with an identical message misses an opportunity to tailor the approach. The frequent former guest likely needs a simple reminder that the door is still open, while the single-order guest may need a stronger reason to give the vendor a second try at all.
How AUANI Handles This
AUANI's exportable guest list makes it possible to identify exactly which guests fall into a lapsed window, based on real order history rather than a guess.
Because the list already includes each guest's past order history, a vendor can reference something specific in the win-back message directly from that data, rather than sending a generic note that reads the same to every recipient regardless of what they've actually ordered before.
That same export also makes it straightforward to build the frequent-versus-single-order segmentation described above, since both groups can be filtered directly from existing order history rather than reconstructed manually from memory or a separate spreadsheet.
Running this same win-back check on a recurring schedule, rather than as a one-time project, keeps the lapsed-guest list current as new guests naturally drift out of their own active ordering window over time.
Frequently Asked Questions
What's a reasonable lapsed window to use?
It depends on typical ordering frequency for the vendor; 60 to 90 days is a common starting point for many food and drink categories.
Does a win-back message need a discount to work?
Not necessarily; a genuine, low-pressure reconnection message can work on its own, though a modest, time-limited incentive can help for guests who need more of a nudge.
How often should a win-back campaign run?
Periodically, rather than continuously, since the same lapsed guest shouldn't be messaged repeatedly without a meaningful gap.
Can this be automated based on order history?
Yes, since the guest list is built from real order data, identifying who has crossed the lapsed threshold can be done on a regular schedule.
What is the wider guide this fits into?
The marketing & repeat orders guide covers this alongside message frequency and guest list data limits.
Should a frequent past guest and a one-time guest get the same win-back message?
Ideally not; a frequent past guest usually just needs a simple reminder, while a one-time guest may need a stronger incentive to give the vendor a second try.
For the wider picture on repeat orders, see the marketing & repeat orders guide.