IT Fundamentals / Help Desk

Help desk is the front door of IT. You're the first human a frustrated user reaches, and most of the job is triage: figure out what's actually wrong, fix what you can, and hand off what you can't with enough context that the next tier doesn't have to start from zero.

Support is usually organized in tiers:

• Tier 1 (you, at first): password resets, basic troubleshooting, ticket triage
• Tier 2: deeper technical issues — server-side problems, escalated hardware failures
• Tier 3: specialists — network engineers, security, senior sysadmins

The soft skills matter as much as the technical ones: staying calm with a frustrated user, asking good clarifying questions, and knowing when you're out of your depth are what actually separate good help desk technicians from mediocre ones.

A ticket is the record of everything that happened with a problem — and it outlives the conversation. Six months from now, someone (possibly you) will need to know what you actually did, not just that "it's fixed."

A good ticket includes:

• What the user reported, in their words
• What you actually observed (not just what they said)
• Every step you tried, including the ones that didn't work
• The final fix, and how you verified it

Common tools: Zendesk, Freshdesk, ServiceNow, Jira Service Management. They all do roughly the same job — capture, categorize, and track a request from open to close. Learn whichever one your employer uses; the underlying discipline transfers everywhere.

The universal method — identify, form a theory, test it, plan and act, verify, document — isn't abstract theory. Here's what it looks like on an actual ticket:

Ticket: "My computer is really slow today."

1. Identify: Ask when it started, what they were doing, and whether anything changed recently (update, new software).
2. Theory: Could be a runaway process, low disk space, malware, or a pending update stuck mid-install.
3. Test: Open Task Manager, check CPU/memory/disk usage first — cheapest check with the most information.
4. Act: If one process is consuming everything, address that specifically rather than guessing at a broader fix.
5. Verify: Confirm with the user that performance is actually back to normal, not just quieter for a moment.
6. Document: Note the cause and fix so the next person (or you, in six months) doesn't start from scratch.

Most hardware tickets fall into a small number of buckets: power, peripherals, connectivity, and printers.

• Power: always check the obvious first — cable, outlet, battery — before assuming a dead component.
• Peripherals: mice, keyboards, monitors, docks — reseating the connection resolves more of these than you'd expect.
• Printers: the single most-dreaded ticket category. Check the queue, the driver, and the physical connection, in that order.

A habit worth building early: note any error codes or beep patterns exactly, even if you don't recognize them. They're searchable, and they're the fastest path to a real answer.

Software tickets are usually one of: the app crashed, the OS is misbehaving, an update broke something, or a user profile got corrupted.

• Restart the app, then the device — genuinely resolves more than it should.
• Check whether the issue started right after an update; if so, that's your leading theory.
• Check logs (Event Viewer on Windows, Console on macOS) for the actual error, not just the symptom the user described.
• Try a clean or guest profile to rule out corrupted local settings before assuming the app itself is broken.

A frustrated user is usually frustrated at the problem, not at you personally — even when it doesn't feel that way. A few habits go a long way:

• Acknowledge the impact before diving into technical steps ("I understand this is blocking your work, let's get it fixed").
• Set realistic expectations. Never promise a timeline you don't control.
• Explain what you're doing as you do it — silence while you work feels worse to the user than it actually is.
• If you genuinely don't know the answer, say so, and say what you're doing next (escalating, researching) rather than guessing out loud.

Remote desktop tools (RDP, TeamViewer, remote assistance built into your ticketing platform) let you see and control a user's screen directly — often faster than talking them through steps verbally.

Security matters here: always confirm you're connecting to the right, authorized device, never leave a remote session open longer than needed, and be transparent with the user about what you're doing while connected. Remote access is also a common social-engineering target — legitimate IT will never pressure a user into installing remote software unexpectedly.