Turn a vague problem into a useful goal
Fictional example: Rosa says her phone is not working properly. A few questions reveal that she cannot save pictures from one particular message. Before the appointment, she notes the app and what happens after she taps the picture. The goal is to find and save one needed image. Questions about her new camera go onto a separate list. This makes it possible to work calmly on the first task without spending the whole afternoon jumping between unrelated problems.
Separate observations from guesses
Record what you actually see: the exact error text, when it occurred and the steps immediately before it. A guess such as “my account was hacked” is different from the observation “I have been unable to sign in since yesterday”. Keeping these separate avoids starting with an unsupported diagnosis. Note any attempted fixes and their results. If a screenshot helps, remove unrelated messages, account numbers and private details. One short, organised description is often more useful than a pile of unexplained images.
Choose the support route deliberately
Ask someone you already know or contact a provider through its official contact point, which you navigate to yourself. Numbers appearing in unexpected warning pop-ups are not a suitable starting point. For paid support, clarify the agreed task, cost and whether device access is necessary. Public assistance differs between countries: a French service such as 17Cyber is not automatically the appropriate authority everywhere. For a work device, your organisation’s IT team may be the right first contact, even if a relative is technically confident.
Work through the appointment in small steps
Charge the device and have relevant accessories ready. Wherever possible, the account owner should sign in themselves. Before making changes, agree what will be tried and what its effects could be. Deleting information or resetting a device should not be an unexplained quick experiment. If important files are involved, first discuss existing backups and whether the action is necessary. Take a break if concentration drops or the task needs a different specialist. Ending with a clear unresolved question can be a useful outcome.
Record the outcome and recognise genuine urgency
Finish with a brief record of what changed, what now works and what remains to do. Keep passwords out of that summary. Let the person repeat the most important operation themselves. If there is ongoing unauthorised money movement or another acute security situation, do not wait for the next family visit; use the relevant official contact promptly. An ordinary learning appointment cannot replace a payment provider’s incident response or professional assistance with a serious problem. Match the route to what has actually happened.
Your checklist
The checkboxes are for your own reference. No entries are sent to us. To keep a copy, print the page or save it as a PDF using your browser menu.
Common questions
Do I need to know technical terminology?
No. Explain in your own words what you did and saw. The exact wording of an error is more useful than guessing its technical cause.
Should I send my password beforehand?
No. An appointment can be prepared without sending credentials. Sign in yourself where possible and arrange any additional assistance through appropriate official options.
What if the problem does not happen during the appointment?
Show your short description and privacy-checked screenshot. Note what differs from the original situation. Not every intermittent issue can be fully explained during one session.
Sources and further information
Primary sources from public authorities, consumer organisations and providers. A source may be in another language; follow the guidance that applies to your service and where you live.
- FTC: How To Spot, Avoid, and Report Tech Support ScamsSource review date:
- Microsoft: Tips for opening support requestsSource review date:
- Cybermalveillance.gouv.fr: 17Cyber assistanceSource review date:



