Build a symptom description

Ask the helper to capture the intended task, the action taken, the result seen and what the user expected instead. Avoid demanding screenshots before knowing whether they are needed. A description of the problem may be enough to select the right guidance. Keep private account details out of a group exercise and use fictional cases for practice.

Distinguish observation from diagnosis

Have trainees mark which statements were observed and which are guesses. 'The project link opened an older document' describes an event; 'the entire platform is broken' is a conclusion. A better description helps the proper support owner investigate without making the customer repeat the story. It also shows when the helper should stop improvising and seek specialist assistance.

Imagine this

Hypothetical programme scene

Hypothetically, a helper receives 'my card does not work'. Careful questions reveal that the profile opens but a brochure is outdated. The issue can now be routed as a content problem rather than treated as a failed physical card.

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.