“My password stopped working.”
User was typing the password into the username field.
Did you restart it?
Technical support for the everyday problems that stop work, interrupt meetings, confuse users, break printers, lock accounts, disappear files, disconnect VPNs, and somehow become “an IT emergency” five minutes before somebody needs to present.
User was typing the password into the username field.
Monitor was turned off. Power button successfully reintroduced to user.
Laptop was not connected to the internet. VPN declined to manufacture Wi-Fi from nothing.
Printer is powered, connected, reachable, sufficiently supplied, and choosing violence.
All tickets are fictional demonstration content. The printer, however, knows what it did.
A good support ticket does not need to be technical. It just needs to contain slightly more information than “computer broken.”
Tell us what is not working. “Outlook will not open” is significantly more useful than “email issue.”
Tell us when the problem started and whether anything changed immediately before it happened.
Tell us which device, application, account, location, or network is affected instead of making us conduct digital archaeology.
Send the actual error message. A screenshot is excellent. A phone photo taken from across the room is less excellent.
Unfortunately, restarting solves enough problems that we are contractually obligated to keep asking.
We know. The operating system has been documenting your commitment to that strategy for eleven months.
Excellent. We have narrowed the search to every writable location accessible by your account.
Include what happened, what you expected to happen, the device or application involved, and the exact error message if there is one.