Set the relationship clearly

Tap Tap Go brings several product areas into one ecosystem, including identity, showcase, programmes and conditional financial features. A referrer can explain their own relevant experience, but should not imply authority to resolve account access, reward qualification or provider eligibility. Those questions belong with the appropriate official team.

Provide a clean handover

When the recipient needs help, share the current support route and the context they can provide themselves. Avoid asking them to send private account information to you first. A warm referral remains valuable when it helps the person reach the right owner without creating an unofficial layer of sensitive information handling.

Keep goodwill separate from obligations

You may choose to help someone understand a portfolio or prepare questions, but do not promise service outcomes or timing outside your control. Programme recognition does not transfer operational responsibility. The recipient should know who actually owns their enquiry after the introduction, especially if several product or partner services are involved.

Imagine this

Hypothetical programme scene

Hypothetically, a referred user asks a friend why a programme event is pending. The friend can point to the programme explanation and support channel. They should not ask for the user’s login or promise approval, even if they originally made the introduction and hope it qualifies for recognition.

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.