A mismatch needs a careful response

Tap Tap Go’s intended lead assistance may help identify requests that appear outside the current offering. That can save time, but it should not automatically reject a person or close a conversation without review. The apparent mismatch may come from unclear wording, missing context or a request that belongs with a different team member. Read the enquiry and confirm the product boundary before deciding whether to decline, clarify or route it elsewhere.

Close the loop respectfully

Ask the assistant to draft a concise explanation only after the human decision is clear. Review the draft for accuracy, tone and promises of alternatives the team cannot provide. Avoid revealing an internal score or speculative assessment as if it were an objective fact about the person. Confirm the recipient and the appropriate contact channel, then send manually. Keep a useful reason in the authorised record so future reviews can distinguish a genuine scope mismatch from a temporary timing issue.

Imagine this

Hypothetical example

A request appears unrelated to the available service, but a salesperson notices it could be a terminology mismatch. They ask one clarification question rather than sending an automatic rejection. When the answer confirms the mismatch, they provide a clear, respectful response without referencing a score.

Make it practical.

Use this checklist as you read. Checks are not stored.

References & further reading

Tap Tap Go Journal: product context and editorial approach ↗

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.