Win Back Quiet Customers Without Giving Everyone RM12 Off

Roslan straightens the empty tables in his casual restaurant in Klang and wonders where his regulars have gone. His usual answer is RM12 off for anyone who has not visited in 30 days. Hana received that offer two days after eating there, costing him margin on a return he had already won.

Roslan, Hana and this restaurant are fictional; all figures in this article are illustrative. Meanwhile, quieter customers are learning to wait for a discount. Roslan needs a gentler first approach and a reliable purchase record: how can he match the offer to the silence without rewarding people who already came back?

1. Thirty quiet days: Hana hears about the new menu. There is no voucher to wait for or claim.
2. Still quiet at sixty: Hana can choose a small soup or drink with a qualifying meal. She has a fortnight to use the offer.
3. Ninety quiet days: Hana receives the strongest offer, RM12 off. This is the first cash discount, although the earlier add-on also costs Roslan money.
4. Hana returns and pays: Her recorded purchase resets the clock, so remaining stages stop selecting her while she is below their thresholds. Roslan then watches for another ordinary paid visit.

flowchart LR
    A["Menu reminder"] -->|Still quiet| B["Choose an add-on"]
    B -->|Still quiet| C["RM12 off"]
    A --> D["Return and pay"]
    B --> D
    C --> D
    D --> E["Purchase clock resets"]

Roslan tests the ladder manually before automating it. For automation, he plans separate launches about four weeks apart; switching everything on together would select already long-lapsed diners for all three messages on the same night.

At his Klang restaurant, staff offer Hana one soup or drink after checking her RM40 bill and 14-day deadline. They record the choice against the shared 20-redemption allowance; she cannot take both. At the final rung, the same qualifying bill becomes RM28 after RM12 off, within a separate 20-discount allowance.

These are merchant-managed offer terms, including outlet eligibility and no stacking. Messages state the limited quantities and ask diners to confirm availability before travelling. After redemption, staff ensure the purchase is recorded; Roslan does not promise that an already scheduled message will disappear.

• KPI 1 — Incremental reactivations by stage: paid returns above the matched baseline, counted once per customer.
• KPI 2 — Retained contribution by stage: cash less fulfilment, incentives and allocated operating costs.
• KPI 3 — Subsequent paid-return rate: reactivated diners buying again within 30 days, without another win-back benefit.

Common mistake: treating all three campaigns as one contact limit. Earlier contact does not exclude later stages, so Roslan must space launches and coordinate other promotions.

Safeguard: honour contact status throughout the test. Pixalink automatically excludes Do Not Contact and Blocked members; staff must not bypass that exclusion through manual follow-ups.

Keep when at least 15 incremental returns cover actual costs and the safeguard holds. Improve one offer, timing or cost assumption in a new bounded test if the signal is promising. Stop the current test if contribution is non-positive, the safeguard fails, or returns miss the pre-set threshold.

Does opening the message reset the clock?

No; only a purchase resets inactivity. Hana needs a recorded purchase, not simply interest in the offer.

Will a purchase cancel a queued message?

Do not assume automatic cancellation of an already scheduled message. The verified promise here is that purchase history changes future selection.

Can I cap messages at one outlet?

This campaign has neither an outlet filter nor a recipient cap. Manage outlet eligibility operationally and cap the reward exposure instead.

Is the add-on free for Roslan?

No; its illustrative fulfilment cost is RM3. Record that cost even though Hana sees a complimentary choice.