Skip to main content

Help guide

How to raise an IT support request without sharing secrets

A useful IT support request says what is not working, when it started, who or what is affected, and how it is disrupting work. Add safe observations and checks already made, but leave out secrets and private records. You do not need to diagnose the cause before asking for help.

This guide is for staff and business managers reporting an IT fault. If there is a safety emergency or you suspect a cyber incident, use the appropriate urgent route first.

Choose the right urgent route

Immediate danger to people or property: move to safety if you can and follow your workplace emergency procedure. If you need urgent police, fire or ambulance assistance, call Triple Zero (000); do not wait for an IT request. See the ACMA’s emergency calling guidance.

Suspected compromise: signs might include an unexpected sign-in approval prompt, a ransomware message or activity you do not recognise. Stop interacting with the suspicious message or prompt. Contact your organisation’s incident lead or IT administrator immediately using an independently verified number or other trusted channel. If you suspect your account or network is compromised, use a separate trusted device and connection to report it. Do not delete evidence, restart or wipe equipment unless your incident lead directs you to.

If you are unsure about the government reporting pathway, the Australian Cyber Security Hotline is 1300 CYBER1 (1300 292 371), available 24 hours a day. That page’s online incident form is for specified organisations, so check its eligibility guidance. If banking details may be at risk, contact your bank using a separately verified number.

A useful request

Give support the picture, not the password

  1. What Describe the issue and any non-sensitive error.
  2. Where Name the affected site, device or service.
  3. When Say when it started and whether it is ongoing.
  4. Impact Explain who is affected and what work is blocked.

You do not need to diagnose the cause before asking for help.

Your support request checklist

For an ordinary fault, use the points below. Give what you know; write “unknown” rather than guessing. Do not delay an urgent report just to fill in every detail.

  • Subject and service: name the affected service or device and the problem, such as “Office printer does not print”. Use a site label only if it is safe to share.
  • When: note when the problem first appeared, when it last worked if known, and whether it is constant or intermittent. Include the time zone if relevant.
  • Scope: say whether one device, several people or a whole location seems affected. Distinguish what you have observed from what has not been checked. A count is usually more useful than a list of people’s names.
  • Impact: describe the work affected and any safe workaround, for example “The front desk cannot print labels; another printer is available”. Explain if the interruption is urgent without guessing its cause.
  • Observed symptoms: describe what you expected and what happened instead. Include only non-sensitive error wording and simple steps already taken. Do not repeat a risky action just to demonstrate it.
  • Checks and contact: note safe checks already made and their results. Ask for follow-up through your organisation’s existing approved business contact method rather than adding private details to the description.

For a useful example of separating expected from actual behaviour, see Microsoft’s Power Automate support-request guidance. Its product-specific steps are not required for every IT problem.

Information to leave out

Never put passwords, multi-factor authentication (MFA) codes, recovery codes, financial credentials, bank PINs, payment card details, secret keys or access tokens in a request, chat or attachment. Do not read an authentication code to someone claiming to be support, and do not approve a sign-in you did not initiate. The Australian Cyber Security Centre’s scam guidance advises against sharing passwords, authentication codes and banking details.

Do not include personal or customer data, confidential records or sensitive screenshots unless your organisation and the recipient have approved a secure procedure. If information is genuinely needed, agree on the minimum and the approved way to share it first; never send the secrets listed above. The OAIC’s privacy guidance explains data minimisation for entities collecting personal information.

Screenshots and logs can reveal names, messages, account details, browser addresses or codes. A cropped image is not automatically safe. If you cannot verify what a file contains, leave it out and ask how to share evidence securely. You can often describe a non-sensitive error in words instead.

Keep these out

Never put secrets in a support ticket

  1. Passwords Do not send account passwords or secret keys.
  2. Verification codes Keep MFA and recovery codes private.
  3. Sensitive records Do not attach customer or staff records by default.
  4. Screenshots Check for private information before sharing.

Use a separately approved secure process when genuinely required.

A fictional request

This example contains no real staff or customer information. Adapt the structure to the facts you have observed.

Subject: Front-desk computers cannot open the company intranet

When and scope: The intranet last worked at about 9 am local time. At about 10:15 am, two front-desk computers on Wi-Fi could no longer open it. We have not checked other devices.

Impact: The front desk cannot view the internal stock list, so answering stock enquiries is delayed.

Observation: We expected the intranet home page to open. Instead, each computer showed “Page can’t be reached”. Other websites opened on both computers. We have not changed settings or restarted equipment.

Follow-up: Please use our organisation’s existing approved business contact method.

This gives the support person a starting point without asserting why the fault occurred. If a time or observation is uncertain, say so instead of copying the example as fact.

Send it and follow up safely

Use the support route your organisation has verified with its provider or administrator. The appropriate channel still needs to be confirmed with its owner before using the Comm Centre Support page; the link alone does not confirm that a request has been delivered. For urgent issues, use your organisation’s verified urgent route rather than relying on a general form.

Keep a safe record of what you sent and any reference number you actually receive. If the problem changes or the impact grows, update the support contact through the verified channel. If someone unexpectedly asks for a password, code or remote access, stop and independently verify the request with your administrator before taking any action.

A clear request should give the person helping you enough context to decide what to check next. They may still need to ask questions; the information above does not guarantee a diagnosis or a particular response time.

Sources and further reading