What to send when you ask for IT help

Say whether the issue prevents all work or affects a particular task. Mention a deadline or a wider team interruption. This helps establish an appropriate starting point without requiring you to name the technical fault.

Copy the error wording or take a screenshot. Check it for personal details, account numbers and customer records before sharing. A delivery failure notice or a repeated sequence of steps can be more useful than a general description.

Mention a new device, software update, changed password or recent settings change. Say what you have already tried. Avoid making several unrelated changes while someone is investigating.

A support provider may need an agreed remote session or administrator access. Keep that out of the first enquiry. Discuss how access will be granted and removed before connecting.

After the work, retain the explanation and any maintenance steps. If the issue returns, those notes provide a useful starting point. The handover should say what changed and what remains to be done.

A useful enquiry might say that Outlook stopped sending on one Windows laptop this morning, the web inbox still works and a customer quote is due today. Include the exact error after checking it for private information. Say whether the issue affects one person or the whole team.

If you do not know the software name, describe the screen or the task. The support request should establish the problem and its impact. It does not need to predict the cause or include your administrator credentials.

Say that you suspect an account access problem and describe what you observed, such as an unexpected sign in or messages you did not send. Include the affected service and when you noticed it. Avoid deleting useful evidence or changing several systems without a plan.

An ordinary website enquiry is not a confirmed urgent response channel. Use your agreed incident process or contact the relevant provider if the issue requires immediate action. The Australian Government's small business cyber security resources provide official guidance for preparing and responding.

Know which device and account are affected and choose a time when you can show the fault. Keep a safe copy of important local records where practical. The provider should explain any requested access and what the session is intended to check.

Confirm the result before the session ends. Record whether the task works, whether more investigation is needed and who owns the next action. That note is useful if the problem returns or another vendor needs to take over.