IT Support Playbooks / IT Support Guides
Build a useful first-response support ticket
A ticket saying only it does not work creates avoidable back-and-forth. Start with the exact symptom, scope, time and impact so the next engineer can act on evidence.
Environment and inputs: Everyday IT support · Windows PowerShell examples unless specified
Try the diagnostic command
Use the stated shell and platform. Replace sample domains, addresses, services and paths with values from the system you are authorized to support.
Get-Date -Format o
hostnameHow to read the result
These PowerShell commands provide a timestamp with timezone offset and the device name. They are useful anchors for matching a user report to endpoint and service logs.
What to do next
Record the exact error text, affected application, expected behavior and steps to reproduce. Ask whether other users are affected and note recent changes, then attach only the evidence needed for the next decision.
Before you make a change
Avoid passwords, recovery keys and unrestricted screenshots in tickets. A device name alone is not sufficient verification of the person requesting support.