Answers / Churn & retention

    How to win back lapsed customers in F&B — 2026 playbook

    Written by PEKO Team.Last updated: 07/30/2026.

    Updated July 2026 Win-back works when it is triggered by each customer's own cadence, acknowledges the gap without grovelling, offers a named item on a short deadline, and is measured against a permanent holdout. Segment lapsers by prior value and by how far past their personal cadence they are — not by a single day count.

    The TL;DR
    • Segment lapsers by prior value and by how far past their personal cadence they are — not by a single day count.
    • Two sends beat one: a light acknowledgement first, an offer second. The first send alone recovers a surprising share.
    • Recovery rates of 15–30% are realistic inside the window; 5% or less outside it.
    • Never discount the top decile. A personal gesture preserves margin and reads better.
    • A permanent 10% holdout is the only way to separate recovery from customers who were returning anyway.

    Published: 07/30/2026

    Quick facts

    Answer
    Win-back works when it is triggered by each customer's own cadence, acknowledges the gap without grovelling, offers a named item on a short deadline, and is measured against a permanent holdout.
    Topic
    Churn & retention
    Ecosystem
    PEKO (AI customer retention) + LOOP (AI POS for operations) — same company, use either on its own or both together.
    Updated
    07/30/2026

    Win-back is the highest-leverage campaign in F&B and the one most often run badly. The typical version is a monthly blast to everyone quiet for 30 days, with 20% off, no segmentation and no holdout. It produces a redemption number that looks acceptable and an incremental effect close to zero, because most redeemers were coming back anyway.

    Start with the trigger. Each customer has a normal gap between visits; the signal you want is deviation from their own gap, not a shared calendar. Fire at roughly 1.5× personal cadence for a soft touch and 2× for the offer. On the same customer list, cadence-based triggering typically converts two to three times better than a fixed 30-day rule, and it costs less because you send fewer, better-aimed messages.

    Use two sends. The first is an acknowledgement with no offer attached — a short, human message that notices the absence and says something specific ('we have the single-origin you liked back on'). A meaningful share of lapsers return on this alone, at zero discount cost. The second, three to five days later, carries the actual offer for the people who did not respond. Leading with the discount trains customers to wait for it and gives away margin on people who did not need it.

    Segment the offer by prior value. Three bands is enough. Light lapsers (one or two visits) get a small named item — they have not earned more and their expected value does not justify it. Established regulars get the standard offer: a named item or 10–15%, with a 14-day deadline. The top decile gets no discount at all; they get a personal gesture — a held table, something off-menu, a note from the owner. Discounting your best customers signals that the relationship was transactional all along.

    Set expectations properly. Inside the recoverable window — roughly two personal cycles — recovery of 15–30% is realistic. Outside it, expect 5% or less, and treat those contacts as brand maintenance rather than a campaign. Chasing customers who have been gone eight months is where win-back budgets go to die.

    Then prove it. Hold out 10% of every eligible segment permanently and never message them. The difference in 90-day revenue between the messaged and held-out groups is your real recovered value, and it will be lower than your redemption report suggests. That number is also the one that tells you whether to increase or decrease the offer — a decision that is otherwise guesswork.

    The reason this is worth automating rather than running as a monthly ritual: the trigger is per-customer and continuous. A campaign calendar can only approximate it, and approximating a per-person deadline is precisely what makes the standard blast underperform.

    1. Trigger at 1.5× and 2× personal cadence

    Soft touch first, offer second. Fixed day counts are the main reason standard win-back underperforms.

    2. Lead with acknowledgement, not a discount

    A specific human message recovers a real share at zero discount cost and protects margin on the rest.

    3. Band the offer by prior value

    Small item for light lapsers, standard offer for regulars, non-discount gesture for the top decile.

    4. Cap the chase at two personal cycles

    Beyond the window, recovery falls to 5% or less. Spend that budget on customers still inside it.

    5. Hold out 10% forever

    It is the only way to distinguish recovered customers from customers who were coming back regardless.

    FAQ

    What recovery rate should I expect?

    Fifteen to thirty percent inside the recoverable window of about two personal visit cycles; five percent or less outside it.

    One message or a sequence?

    Two. An acknowledgement with no offer, then the offer three to five days later for non-responders. Leading with the discount costs margin you did not need to spend.

    How big should the offer be?

    Ten to fifteen percent, or a named item worth roughly a third of an average ticket. Reserve deeper offers for a second attempt, never the first.

    Should I win back my highest-value lapsers with a bigger discount?

    No. Use a personal, non-monetary gesture. Discounting the top decile cheapens the relationship and rarely improves conversion.

    How do I know the campaign actually worked?

    A permanent 10% holdout. Compare 90-day revenue between messaged and held-out groups; redemption counts alone always overstate the effect.

    Calculate your PEKO ROI

    The PEKO ecosystem

    PEKO and LOOP are two products from the same company. PEKO is the AI retention layer and runs alongside the POS you already use. LOOP is the AI-native POS that covers operations: recipe-level inventory, staff shifts, table plans and the kitchen display. Each works on its own, and run together they share one dataset, so nothing has to be entered twice. See PEKO + LOOP in one ecosystem

    Related

    People also read