The Short Answer
Explain The Impact And What You See — We Can Investigate The Cause
Tell IT support what work is affected, who is affected, where the fault happens, when it started and what you see instead of the expected result. Add the exact error message, a few repeatable steps if safe, and your best contact. You do not need to identify the technical cause before asking for help.
A clear request gives your technician a useful starting point. It can reduce the back-and-forth over basic details and help distinguish a single-device problem from an issue affecting the whole business. Below is a copyable brief, examples and a safe way to share evidence.
Need help with a business IT issue on the Sunshine Coast or in Gympie? Tell Ultra IT what is happening. Our local team can help assess the problem and the appropriate support scope, including website or custom-system issues that need a developer rather than a scripted answer.
What Matters Most
- Start with the work affected, who is affected and any real deadline.
- Separate expected behaviour from the exact error or symptom.
- Use the thirteen-field brief; unknown is better than a guessed cause.
- Keep passwords and private records out, and agree a safe support route.
01
Start With The Work That Is Blocked
Lead with the business effect, not a guessed diagnosis. “Our three reception staff cannot open the shared booking calendar” gives a different picture from “the calendar will not open on my laptop.” Both matter, but the technician needs to know which situation they are dealing with.
For example: “Two staff cannot send invoices from the accounting app. The invoice drafts are still visible. We need to send today's invoices before 3 pm Brisbane time.” That describes the impact without declaring the server broken or promising how quickly the fault can be fixed.
If the issue is urgent, use your provider's agreed urgent contact route. Do not wait to finish a perfect report before contacting them about a serious outage or suspected security incident.
Use this business-impact checklist:
- The task you cannot complete: sending invoices, taking bookings, opening a shared file or submitting a website form.
- How many people or devices you know are affected. Say “not checked yet” when you do not know.
- Whether the problem stops work completely or whether there is a safe, approved workaround.
- Any real deadline and what happens if it is missed.
02
Name The App, Device And Time
Identify the place where the problem occurs. For a website, give the public address and the page or feature involved. For an application, name it and the task you were performing. For a device, describe the type and, if relevant, whether it is managed by your business.
Useful timing is “first noticed at 9:10 am on Tuesday, Brisbane time; last worked on Monday afternoon”, not simply “recently”. An approximate time is fine if that is all you have. Label it as approximate rather than making one up.
Add the browser, operating system or connection when it helps explain the difference. For example, the same work page might fail in one browser but work in another, or work on office Wi-Fi but not from home. You do not need to hunt for every version number before making the request; the technician can ask for relevant details.
Do not put a private reset link, sign-in token or customer-record URL into an ordinary enquiry. Describe the screen and ask how to share sensitive evidence through an approved channel.
03
Separate Expected From Actual
Write one sentence for what should happen and one for what actually happens:
“After I select Save, the new booking should appear in Tuesday's calendar. Instead, the page returns to the calendar and the booking is not there.”
Copy the exact error wording if it is visible. If there is no error, say what you can observe: a blank page, a spinning indicator, a missing record or an application closing. Avoid replacing the message with your interpretation.
Clear steps, expected behaviour and useful screenshots are also principles in Chromium's official bug-reporting guidance. You can use the same reporting pattern for a business support request without needing to become a software tester or post your business information publicly.
04
Give A Short Sequence Of Steps — When It Is Safe
Keep one action per step. Say whether it happens every time or only sometimes. For an intermittent issue, note the successful and unsuccessful times and anything you observed that was different. A pattern is useful even when you cannot reproduce it on demand.
Do not repeatedly submit payments, send messages, delete records or make other consequential changes just to capture the fault. Report what already happened and ask the technician how to test safely. If you suspect an account has been compromised or a message is malicious, do not keep clicking it to demonstrate the problem; use your verified IT contact and the business's incident procedure.
A useful example might be:
- Open the staff scheduling page.
- Select the Tuesday view.
- Choose an available staff member.
- Select Save once.
- The page returns to the calendar without the new booking.
05
Share Evidence Without Sharing Secrets
A cropped screenshot can show an error clearly. Check it before attaching it: remove unrelated customer details, private messages, financial records and anything else the recipient does not need. Use an authorised support channel, not a public forum or social-media comment.
Never include passwords, MFA codes or recovery codes in this brief. Do not approve an unexpected sign-in prompt. The Australian Cyber Security Centre explicitly warns against sharing passwords and MFA codes in its practical cyber security tips for business leaders.
For a screen recording, first consider what could appear while you move between windows. If you cannot confidently keep private information out, send the error wording and a description instead. Your support team can arrange an appropriate way to inspect the problem.
06
Say What Changed And What You Already Tried
Mention relevant changes such as a new computer, software update, website edit, different network or changed sign-in method. Treat them as context, not proof that they caused the fault.
List each check and its result. “Closed and reopened the browser; the same error appeared” is useful. “Tried everything” is not specific enough for someone else to know what was checked.
Do not reset a device, remove security tools, change DNS or reinstall software merely to make the report look thorough. If no safe checks have been performed, write “not tried yet”. Preserving the current state may be more useful than changing it before the technician can review it.
Finish with a contact name, an agreed way to reach you and a time when someone can test. If several staff are affected, nominate one contact to gather updates so the technician receives a consistent account of what is happening.
07
Copy This IT Support Request Brief
Use the fields you can answer. “Unknown” is better than a guess. Leave passwords and private access links out, and only attach evidence you are authorised to share.
For an initial public website enquiry, a short summary of the impact, application and symptom is enough to start the conversation. Keep detailed logs and sensitive attachments for the support channel agreed with the technician.
- What work is affected:
- Who is affected:
- What should happen:
- What happens instead:
- Website/app/device:
- When it started (include timezone):
- Steps to reproduce:
- Exact error message:
- Recent relevant changes:
- What I tried and the result:
- Safe screenshot or evidence attached:
- Business deadline or impact:
- Best contact and time to test:
08
Three Examples Of Clear Requests
These are illustrative examples, not Ultra IT customer stories or diagnosed causes.
One Computer Cannot Open A Shared Folder
“I cannot open the Accounts shared folder on my work laptop. It first failed around 8:45 am Brisbane time. A colleague can open it on their computer. I see 'Access denied'. I have not changed permissions or deleted anything. I am available to test after 10 am.”
This separates a known single-device symptom from an unverified whole-business outage and preserves the error wording.
A Website Enquiry Does Not Appear
“Our website contact page shows a thank-you message, but the authorised test enquiry has not appeared in the expected mailbox. The test was sent at 11:20 am Brisbane time. We have checked the correct mailbox and junk folder. We have not submitted more tests or changed mail settings. Please advise how to check the delivery path.”
This distinguishes a visible form confirmation from verified email delivery without assuming either the website or mailbox is the cause.
A Booking App Sometimes Freezes
“The booking app freezes when I open next week's calendar. It happened twice today, at approximately 9:05 and 10:40 am Brisbane time, but worked between those times. Only my workstation has been checked. I have a cropped screenshot of the error and can show the steps during a support session.”
This gives an intermittent fault a useful timeline without inventing a repeatable pattern.
09
Get A Clear Next Step From Local IT Support
You do not need a polished technical diagnosis to ask for help. Bring the brief you have, explain what work is blocked and let us help identify the next step.
Ask Ultra IT about remote IT support for an issue that may be investigated remotely. For recurring problems or ongoing business support, discuss Managed IT with our Sunshine Coast and Gympie team. We will review the situation and agree the relevant scope before work proceeds.
Common Questions
Clear Answers Before You Decide
Do I Need To Know The Cause First?
No. Describe the work affected and the behaviour you observe. A technician can investigate the cause; a guessed diagnosis can hide useful facts.
What If I Cannot Reproduce The Problem?
Record when it happened, what you were doing and the exact message if available. Mention that it is intermittent. Do not keep performing risky actions just to make it happen again.
Should I Send My Login Details With The Request?
No. Leave passwords, MFA codes, recovery codes and private sign-in links out. If access is needed, agree the appropriate access method with the verified support team separately.
What If Everyone Is Affected?
Say how many people or devices you have checked, which work is blocked and whether an approved workaround exists. Use your provider's agreed urgent route where appropriate and nominate a contact for updates.
Can Ultra IT Help With A Website Or Custom Business System?
Ultra IT provides website development and custom business systems as well as business IT support. Tell us which system is involved and what happens; we can assess whether the next step is remote support, managed IT or separately scoped development work.
Sources And Review Notes
This guide combines Ultra IT's practical service experience with the current primary sources below. Product availability, pricing and platform guidance can change; check the linked source or ask us to review the current environment before acting.
