Skip to content
FORGENO ADS GAMESUnlock all $8

IT Support & Networks · Unit 8 of 8

Unit 8: Help desk skills and IT careers

Tickets and priorities, talking to people under stress, security at the help desk and how to start an IT career.

Opens the first lesson of this unit in IT Support & Networks. Every lesson is open from the start.

Lesson 1: Tickets and priorities

Goal: Prioritize tickets by impact and urgency.

IT teams track every request in a ticketing system, so nothing is forgotten, work can be shared and patterns can be spotted. A good ticket records who is affected, what is happening, what has been tried and what was done.

Not every ticket is equally important. Teams set priority by combining:

  • Impact: how many people or how much of the business is affected?
  • Urgency: how quickly does it cause real harm? Is there a workaround?
Low urgencyHigh urgency
High impactMedium-high: the whole office's shared calendar is slowCritical: nobody can process payments
Low impactLow: one user wants a new mouseMedium: the CEO cannot join a call starting in 10 minutes

Many teams also agree service levels: targets like "respond to critical tickets within 15 minutes". And they distinguish an incident (something broken that needs fixing now) from a service request (something new someone needs, like an account, software or a device).

Worked example: triaging a morning queue

  1. Ticket A: "Can I get a second monitor?" (low impact, low urgency).
  2. Ticket B: "The card machine at the front desk won't connect; customers are waiting." (high impact, high urgency).
  3. Ticket C: "My mouse is a bit laggy." (low, low).
  4. Handle B first, then A and C. Updating A and C with a time estimate keeps those users informed.
Ticket
A record of a support request, tracking it from report to resolution.
Impact
How much of the business or how many users a problem affects.
Urgency
How quickly a problem causes harm if it is not fixed.
Incident
An unplanned interruption or failure of a service.

Remember: Priority = impact × urgency. Fix what stops the business first, and keep everyone else informed.

Lesson 2: Talking to people

Goal: Communicate clearly and calmly with users who are frustrated or not technical.

Technical skill gets problems fixed; people skills get them fixed smoothly. Users often contact IT when they are stressed, behind on work and feeling embarrassed.

  • Listen fully first. Let them explain without interrupting, then summarize back: "So since this morning, you can't open shared files, and you have a deadline at noon. Is that right?"
  • Acknowledge the impact: "That's really frustrating with a deadline coming."
  • Use plain language. Say "the connection between your laptop and the Wi-Fi" instead of "your WLAN adapter's DHCP lease".
  • Never blame. Say "Let's check the cable" instead of "You unplugged it".
  • Set expectations: say what you are doing and how long it might take.
  • Confirm before closing: "Can you try opening the file now?" and check the user agrees it is fixed.
AvoidTry instead
"That's impossible.""That's unusual. Let's look at it together."
"Just reboot.""Restarting clears out temporary glitches. Can you try it while I wait?"
"I don't know.""I'm not sure yet. Let me find out and get back to you by 2 p.m."
Active listening
Listening fully, then summarizing what you heard to confirm you understood.
Plain language
Clear, everyday words instead of jargon.

Remember: Listen, summarize, acknowledge, explain plainly, never blame, confirm it is fixed.

Lesson 3: Security at the help desk

Goal: Verify identity and resist social engineering.

Attackers know help desks exist to help, and they exploit it. Social engineering means manipulating people, instead of hacking computers, to get access, for example by calling the help desk pretending to be a stressed executive who is locked out.

  • Verify identity before resetting a password or granting access, using the company's approved method: calling back on the number in the staff directory, a verification code or a manager's confirmation. Never only "they sounded legitimate."
  • Never ask for a user's password. IT never needs it; administrators can reset accounts instead.
  • Watch for pressure tactics: urgency, authority ("I'm the CEO!"), anger or flattery are all designed to make you skip steps.
  • Least privilege: grant only the access a person needs for their job.
  • Report anything suspicious to the security team, even if you are not sure.

Worked example: the urgent caller

  1. Caller: "This is Dana from Finance. I'm about to present to the board and I'm locked out. Reset my password and read it to me now!"
  2. Pressure and urgency are red flags, even if the caller is genuine.
  3. You: "I can help right away. For security, I'll call you back on your directory number in two minutes," then follow the verification process.
  4. A real Dana will understand. An attacker will hang up.
Social engineering
Manipulating people into giving up access or information.
Identity verification
Confirming a person is who they claim to be before acting on their request.

Remember: Verify before you reset. Never ask for passwords. Pressure is a red flag.

Lesson 4: Starting an IT career

Goal: Map an entry path into IT and the next steps after this course.

IT support is one of the most common doorways into technology careers, and many people start without a degree, by proving their skills.

RoleWhat you doOften leads to
Help desk / IT supportFirst-line support: tickets, accounts, devices, troubleshootingDesktop support, systems, networking or security
Desktop support technicianHands-on hardware and software supportSystems administration
Network technicianSetting up and maintaining networksNetwork engineering
Systems administratorServers, accounts and cloud servicesCloud or DevOps engineering
Security analystMonitoring and responding to threatsSecurity engineering

Widely recognized entry-level certifications include CompTIA A+ (IT support fundamentals), CompTIA Network+ (networking) and CompTIA Security+ (security basics), plus beginner programs such as the Google IT Support Professional Certificate. Check each provider's official site for current exams, prices and requirements, since these change.

Ways to build experience before your first job:

  • Fix computers and home networks for family and friends, and keep notes as if they were tickets.
  • Set up a home lab: an old PC, a spare router or free virtual machines to practice on.
  • Volunteer with schools, libraries, community centers or nonprofits.
  • Write up what you learn: a simple portfolio of problems you solved and how.

This course's certificate shows you completed real training. Certifications and hands-on experience are what employers use to judge readiness, so treat this course as your launch point.

Remember: Start at the help desk, prove skills with certifications and a home lab, and document what you fix.

Practise it in IT Support & Networks

Each lesson ends with two or three questions that check you can use the idea, not just recognise it. Wrong answers explain why and come back in Review. The unit ends with a 6-question quiz; pass it with 80% or more to master the unit. Hands-on lab: Help desk simulator.

Every lesson is free: no ads, no lives and no paywall.