Don't Panic — Technical Support Fundamentals

Technical support turns a report such as "my account does not work" into a shared, testable problem. The job is not to guess a fix. You establish what the user expected, what happened instead, who is affected, and what changed.

The problem it exists to solve is the one where a user reports a symptom and the responder acts on the description without confirming it — chasing a fix for something nobody has reproduced. Before the practice had a loop, support was guesswork: change something, see if it works, change something else if it didn't.

Two ideas hold up the rest. One change at a time means every test isolates a single variable, so the result means something. A workaround is not a resolution means restored access does not identify the cause, and the next incident will be the same incident unless someone followed the evidence to the root.

The part that surprises people is that the report is not the diagnosis. A user report is a symptom, not a problem. The support loop exists to turn it into a testable hypothesis before anyone changes anything. Skip that step and every later step inherits the guess — which is why the same incident keeps coming back with a different ticket number.

The Cheatsheet has the case intake checklist and the triage matrix. The Slides compress the support loop into a single pass. Field Notes carries the traps that turn a respectable ticket queue into a workaround factory. The Quiz checks whether the distinctions survive a label shuffle.