Repair Customer Trust After a Late Delivery

Noor’s catering delivery arrives late to a corporate lunch in Shah Alam. The trays finally reach the table, but Kelvin Ooi has already spent his lunch break explaining the delay to colleagues. Noor sends a RM100 voucher within the hour and, hearing nothing back, assumes the matter is closed.

Kelvin accepts it, never uses it, and quietly books elsewhere. Noor, Kelvin and this business are fictional; all figures in this article are illustrative. The gesture has acknowledged the inconvenience without answering Kelvin’s real concern: will the next lunch arrive on time?

1. Kelvin receives an acknowledgement. Noor authorises the voucher within the hour and logs it against him, without treating acceptance as closure.
2. Kelvin hears what changed. Noor calls the next day to explain the delay and the kitchen’s revised dispatch check, whether he uses the voucher or not.
3. Kelvin does not start again. Staff consult the reward record and Noor’s separate complaint notes before their next conversation, including after redemption.
4. Kelvin’s next delivery tests the repair. Noor checks for another late-delivery complaint; redeeming RM100 alone does not establish success, and no further order leaves the outcome unknown.

flowchart LR
 A[Apology received] --> B[Kitchen fix explained]
 B --> C[History remembered]
 C --> D[Next delivery checked]

Noor selects the first 10 approved late-delivery cases over 30 days. She offers each client one RM100 voucher, valid for 60 days from issue, with no added minimum spend; her written terms explain how orders below RM100 are handled before anyone accepts.

She reserves RM1,000 for the vouchers and RM600 for calls, recordkeeping and the dispatch change. She manually records approval, expiry and budget use, and stops new trial enrolment at the cap while continuing to handle complaints.

For Kelvin, she checks the kitchen handover, assigns a dispatch owner and explains the actual correction next day. After redemption, she checks delivery performance rather than issuing another incentive; follow-up lasts through each client’s 60-day window.

• Repeat complaint rate: later deliveries to trial clients with another lateness complaint divided by all their later deliveries; target no more than 10%, with at least 10 deliveries observed.
• Next-day follow-up rate: completed explanation calls divided by approved cases; target 100%.
• Incremental contribution: additional-order contribution minus actual operating costs and discounts on baseline orders; compare with the six-order minimum target.

Common mistake: Noor marks Kelvin’s case resolved when he accepts the voucher. That records acceptance, not a corrected delivery process.

Safeguard: Noor uses a named-authoriser record stating that accepting the voucher never closes the complaint or requires silence. Staff must honour that condition throughout the trial.

Keep when the minimum target, complaint and follow-up thresholds, and safeguard hold. Improve a promising mid-trial signal with one bounded dispatch or call-timing change; stop expansion if contribution is non-positive, the safeguard fails or a pre-set threshold is missed at the final review, including insufficient delivery observations.

Must Kelvin order again to receive the apology?

No purchase is required to receive the voucher or explanation. Using the voucher does require a later order, so describe it honestly as future-order value.

Does Pixalink decide who can authorise it?

That approval policy belongs to Noor. An issuance audit record is not a merchant approval workflow.

What if Kelvin never redeems it?

Make the promised follow-up anyway. No redemption does not prove dissatisfaction, and no later delivery cannot demonstrate that the problem stopped.

What about a cancelled order or unused balance?

Noor must explain those terms before launch and review exceptions herself. Automatic voucher restoration or balance carry-forward is not established for this recipe; do not promise either.