TAP TAP GO
Separate the customer and programme events
Tap Tap Go’s referral and reward model can involve customer activity, but an order and a reward are not the same record. If a purchase changes, first understand the order’s status. Then check whether the relevant programme links qualification to that purchase and how it handles later changes.
Avoid automatic assumptions
Do not assume that every return cancels a reward, that every pending order earns one or that a previously displayed amount can never change. The current programme terms determine those mechanics. Participants and operators need the current terms and the actual event history to interpret a particular case.
Keep both journeys explainable
A support request should identify the original programme event and the changed order without exposing unnecessary customer details. Clear explanations protect the referred customer from pressure to keep a purchase solely because somebody else expects a reward. Their product decision should remain their own.
Hypothetical programme scene
In a hypothetical referral journey, a customer changes the order before fulfilment. The referrer should not calculate a reward from the original value or pressure the customer to proceed. The programme’s current qualification and adjustment rules determine the separate reward outcome.
Make it practical.
Use this checklist as you read. Checks are not stored.Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
