TAP TAP GO
Understand the requested scope
Check which product, entity, data flow and customer use case the question concerns. A broad yes-or-no answer may be inaccurate if the service relies on multiple partners or configurations. Ask for clarification where the meaning materially affects the response.
Use the right owner
Route technical, security, financial and contractual questions to the appropriate team or professional adviser. Keep a controlled set of approved answers with review dates. Copying a previous response without checking changes can create inconsistencies between customer promises and actual operations.
State limitations directly
If a requested capability is unavailable, planned or dependent on a partner, explain that status clearly. Offer relevant supporting information without implying that a future plan is already implemented. An honest limitation enables a sound procurement decision and reduces later disputes about expectations. Preserve the exact response submitted to each customer. If the approved answer later changes, the team needs to know which customers received the earlier version and whether a follow-up clarification is appropriate for their particular implementation or commercial discussion.
Illustrative operating example
A hypothetical questionnaire asks whether every payment service is available to all employees. If availability depends on product, market or eligibility, a blanket yes would be misleading. The response should define the relevant scope and the process for confirming customer access.
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.
