A few minutes of preparation can make an IT support call more focused. Before reaching out, write down what is happening, who and what is affected, and when the problem began. Capture any error messages and note recent changes to devices, software, accounts, or network settings. These details help the support technician understand the situation and choose useful next steps. You do not need to diagnose the cause; clear observations are enough to get started.
Describe the Issue Clearly
Summarize the problem in one or two sentences. Explain what you expected to happen and what happened instead. For example, say that a staff member can open email on a phone but not on a laptop, rather than saying only that email is broken. Include when you first noticed the issue and whether it happens every time or only intermittently.
Note the steps that reproduce the problem, if you know them. Record what the user clicked or attempted immediately before the issue appeared, and whether restarting the app or device changed anything. Avoid repeated troubleshooting that could risk data loss or disrupt other users. Tell support what you have already tried so the technician does not need to repeat those steps.
List Affected People and Devices
Identify who is affected: one person, a team, or everyone at the business. Note whether the issue follows a specific user across devices or stays with one device regardless of who signs in. This distinction can help support narrow down whether to examine an account, an application, a device, or a shared service.
For each affected device, gather its type, make and model if available, operating system, and the name your business uses for it. Include whether it is a desktop, laptop, phone, printer, or network device. Note how it connects, such as office Wi-Fi, an Ethernet cable, or a remote connection. Do not send passwords in ordinary email or include them in your notes.
Capture Error Messages
Write down the exact wording of any error, including codes, punctuation, and the application where it appeared. A photo or screenshot can help, provided it does not expose customer information, passwords, or other sensitive data. If the message disappears quickly, note the approximate time and the action that triggered it.
Record what still works alongside what fails. For example, note whether the website opens on another device, whether other staff can use the same application, or whether only one feature is unavailable. These comparisons give support useful context without requiring you to guess at a technical cause.
Note Recent Changes
List changes made shortly before the issue started. Include software or operating system updates, new applications, password or account changes, equipment replacements, network adjustments, and changes to permissions. Note who made each change and approximately when. If nothing changed that you know of, say so rather than leaving the question unanswered.
Before the call, gather relevant account or device names and a reliable way for the technician to contact the affected user. Keep private information secure, and share access details only through a method the support provider approves. If the problem is disrupting essential work, mention its business impact and any safe workaround currently in use.
A concise record of the symptoms, affected devices, exact errors, and recent changes gives an IT support technician a practical starting point. Keep these notes together and update them if the issue changes before the call. When you are ready, contact Okanagan IT Support to discuss the problem and arrange a useful next step.