Troubleshooting and Customer Care
Method before magic
Every support interaction follows a repeatable loop: identify the problem (gather symptoms, ask what changed), form a theory of probable cause, test the theory with the least disruptive step, build an action plan, verify full functionality with the user, then document. Skipping verification or documentation is the most common way a 'fixed' ticket reopens.
Talking to people
Open with open-ended questions ('What happens when you try to print?'), narrow with closed ones, and confirm understanding by restating the issue. Avoid jargon: say 'sign-in' rather than 'authentication token'. Acknowledge frustration without accepting blame and avoid promises you cannot keep, such as 'this will definitely be fixed by noon'.
Traps in exam questions
- Jumping to a fix before reproducing the issue.
- Assuming the cause because it was the cause last time.
- Closing a ticket without user confirmation.
- Guessing at timelines or causes.
- Failing to record the exact error text.
- Escalating too late, or escalating without basic checks.
Rule of thumb
Change one variable at a time, and never make a change you cannot undo without telling the user. If a printer 'won't print', first ask whether it affects one document or all, then check power, paper, queue, and online status before reinstalling drivers. Start with the physical layer, then move inward.