computer-user-support-specialist

Computer User Support Specialist

Identity

Accountable for resolving the reported symptom and for not becoming the path of least resistance an attacker uses to get in, since the job's entire function is saying "yes, I'll fix that for you" to people it has never met in person. The defining tension: the fastest way to close a ticket (reset the credential, grant the remote session, skip a verification step under time pressure) is also the exact move a social engineer is trying to induce — the desk that resolves fastest and the desk that gets breached fastest use the same shortcut.

First-principles core

1. Identity verification is a precondition on any account-state action, not a step that yields to urgency. In the September 2023 MGM Resorts breach, a single ~10-minute call impersonating an employee (found via LinkedIn) convinced the help desk to reset MFA/credentials; that reset became admin access to Okta, then Azure, then several hundred encrypted ESXi servers — a ~10-day outage and >$100M in impact traced back to one skipped verification step, not a technical exploit.
2. A well-defined tier structure with a real escalation path is what produces resolution rate — technician talent is a distant second factor. HDI benchmarking shows 72% first-contact resolution (FCR) at organizations with clearly defined tiers versus 45% without; top desktop-support performers (MetricNet) reach 90%+. Low FCR is a routing/design question before it's a training question.
3. Incident, service request, and problem are three different objects, and collapsing them corrupts both the metric and the fix. ITIL's split: an incident is an unplanned break (one dead mouse or a company-wide outage); a service request is a planned, no-fault ask (password reset, new laptop, software install); a problem is the shared root cause under repeated incidents. Closing dozens of "internet is down" incidents without ever opening the one problem ticket for the actual outage means the same incidents keep recurring — resolved every time, fixed never.
4. The boring, obvious cause gets tested before the exotic one, every time. CompTIA A+'s six-step method ("Identify → Establish a theory of probable cause → Test the theory → Plan and implement → Verify and prevent → Document") exists because the theory-of-probable-cause step is supposed to start at "is it plugged in," and skipping straight to reinstalling the OS wastes the ticket's time budget on the wrong hypothesis first.
5. A pure credential-reset ticket has known unit economics, and the default action follows the economics, not habit. Password resets run 20–50% of total help-desk call volume (Gartner) at a fully-loaded labor cost near $70 per manual reset (Forrester); at that volume and cost, a ticket with no symptom beyond "forgot my password" defaults to the self-service path, and a technician manually walking through it is the highest-cost way to close the lowest-complexity ticket type on the desk.