What should you include in an IT support request?
Include the affected service, when the problem began, who is affected, the business impact and any visible error message. Use your agreed support channel. Do not include passwords, one-time codes or confidential customer information in an ordinary enquiry.
Give the team enough context
Explain what you were trying to do and what happened instead. State whether the issue affects one person, one site or everyone. Include the time and timezone if the incident needs to be matched against logs.
Describe recent changes
Mention updates, equipment moves, new users or configuration changes that may be relevant. Report what has already been tested so the next engineer does not repeat the same steps unnecessarily.
Share evidence safely
A screenshot can help, but remove sensitive information that is not needed. Use the secure channel agreed with your provider for logs or other confidential material. Never send account secrets to prove your identity.
Use the right route
Existing customers should use the support route and escalation contacts in their service agreement. A general website enquiry is suitable for discussing a new project, but it should not be assumed to be a monitored emergency incident channel.
If the impact increases, update the existing incident reference where possible. One clear record with accurate context is easier to coordinate than several disconnected messages about the same issue.
Put this guidance to work.
Explore the relevant emtech service, then discuss the scope that fits your business.