United Kingdom · Technical roles · Entry Level (0-2 years)

Help Desk Technician I

Here is the whole job, in plain words. What it is, a real day, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

Experience bandEntry Level (0-2 years)
Direct reportsNo direct reports
Reports toSenior Help Desk Analyst
UK framework levelUsually someone starting out, or keeping a process running

Also advertised as Junior IT Support Assistant · Entry-Level Technical Support Specialist · First Line Support Engineer

Built on an analysis of 43,079 real UK job descriptions · grounded in qualifications employers recognise

Start with a free Future Fluency check, tuned to Help Desk Technician I

Ten quick questions, one per Future Fluency, asked against this role rather than a generic one. About five minutes, and no card.

Start the check, free

1What this role really is

This isn't just about fixing computers; it's about helping people stay productive. As a Help Desk Technician I, you'll be the friendly face (or voice) of IT, solving everyday tech headaches for our colleagues. You'll handle the initial wave of incoming requests, from password resets to software installs, making sure everyone can get on with their work. It's a crucial role, really, because you're the first point of contact, setting the tone for how our users experience IT support.

2What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Jira Service Management (or similar ITSM)Basic

Logging new tickets, updating existing tickets with notes, assigning tickets to yourself or escalating them, using pre-defined workflows to resolve issues.

TeamViewer / Splashtop (or similar Remote Access)Basic

Initiating remote sessions to users' computers to troubleshoot software, install applications, or check system settings directly.

Confluence / Guru (or similar Knowledge Base)Basic

Searching for and applying existing knowledge base articles to resolve common issues, and flagging articles that are incorrect or out of date.

Okta / Azure AD (or similar Identity & Access Management)Basic

Performing password resets, resetting Multi-Factor Authentication (MFA) tokens, and assigning users to pre-defined application groups based on requests.

Microsoft Intune & Jamf (or similar Endpoint Management)Basic

Enrolling new devices, deploying approved applications from the company portal, and initiating remote wipes on lost or stolen devices.

Slack / MS Teams (or similar Collaboration)Basic

Using channels for internal team communication, answering user questions via chat, and using basic integrations like Jira bots to check ticket status.

PowerShell / Bash (Script Execution)Basic

Executing pre-written scripts provided by senior colleagues to perform routine tasks like clearing user caches, checking disk space, or gathering system information.

3What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choice	Coming in	Where you are now	The step above
Troubleshooting Approach for Routine Issues (e.g., password reset)	Follows documented scripts and knowledge base articles. Escalates if the script doesn't work or if it's an unusual variant.	Chooses the most efficient troubleshooting path based on experience. May adapt standard approaches slightly. Escalates if novel.	Designs new troubleshooting workflows and diagnostic trees. Authorises deviations from standard procedures for complex cases.
Software Installation Requests	Installs pre-approved software from the company portal or via documented procedures. Requires approval for anything outside the standard catalogue.	Evaluates requests for non-standard software against policy. Can approve low-risk, pre-vetted applications. Escalates high-risk requests.	Defines the software catalogue and approval process. Makes recommendations on new software to be added or removed from the approved list.
Escalation of Complex Issues	Escalates any issue that cannot be resolved using documented Tier 1 procedures or within the specified AHT. Consults Senior Analyst.	Determines appropriate escalation path (e.g., Tier 3, Network, Security) based on issue type and impact. Informs manager.	Defines escalation matrices and service level agreements (SLAs) with other IT teams. Can override standard escalation paths for critical incidents.
User Account Management (e.g., new user setup, access changes)	Executes account creation and access assignments based on HR requests and predefined templates. Requires review for unusual access requests.	Manages group memberships and application access within established policies. Troubleshoots access issues. Can approve minor deviations.	Designs and audits access control policies. Implements automation for user lifecycle management (onboarding/offboarding).

4How you'll be judged

The scoreboard, honestly: the hard targets, how often each one is actually looked at, and the quiet human signals that never make it onto a dashboard.

First-Contact Resolution (FCR)

The percentage of issues you fix on the very first interaction with a user, without needing to pass it on or follow up later.

Target · > 70%

You take a call about a password reset, fix it there and then, and the user confirms it's sorted before you hang up. That's an FCR.

Average Handle Time (AHT) for Tier 1 Issues

The average amount of time you spend on a ticket, from when you open it to when you close it, specifically for those simpler, routine problems.

Target · < 20 minutes

A user calls about a printer not working. You spend 15 minutes troubleshooting, reinstalling drivers, and testing, then close the ticket. That's within target.

Customer Satisfaction (CSAT) Score

This is how happy our users are with the support you've provided, based on a quick survey they get after their ticket is closed.

Target · > 4.5 out of 5.0

You help a user with a tricky software installation, they leave a 5-star rating and a comment saying 'really helpful and patient!'

Ticket Documentation Quality

How well you've logged the problem, what you did to fix it, and any relevant notes in the ticketing system. This helps everyone later.

Target · 95% adherence to template

A Senior Analyst reviews your tickets and finds that 98% of them clearly state the issue, steps taken, and resolution, following our internal guidelines.

Adherence to Standard Operating Procedures (SOPs)

This is about consistently following the established steps and checklists for common issues, ensuring we're all doing things the same, correct way.

Your Senior Analyst will review your tickets and observe your troubleshooting process. They'll be looking for consistent application of our documented procedures, like always checking the knowledge base first or following the exact steps for a new software deployment. If you're always doing things 'your own way' without good reason, that's a flag.

Clear and Empathetic Communication

How well you explain technical issues and solutions to non-technical users, making sure they understand and feel respected, even when they're frustrated.

We'll look at feedback comments from CSAT surveys, listen to recorded calls (with your permission, of course), and your Senior Analyst will observe how you interact. Are you using jargon? Do you sound patient? Can you translate 'DNS resolution failure' into 'the internet connection is a bit wobbly, we're looking into it'? That's what we want to see.

Proactive Learning and Skill Development

Your willingness to learn new tools and techniques, ask questions, and actively seek out knowledge to improve your problem-solving abilities.

This shows up in a few ways: how often you ask clarifying questions to your Senior Analyst, your engagement in team training sessions, and your personal development plan. Are you taking the initiative to read up on new software we're deploying? Are you asking 'why' something broke, not just 'how do I fix it'? That curiosity is key.

5Would you like it

The honest version. What people enjoy, and what grinds them down.

What people enjoy

Helping People Solve Problems

You get a genuine buzz from unblocking someone's day, whether it's getting their email working again or helping them connect to a new printer. That 'thank you' really means something to you.

A colleague is stuck before a big client call because their headset isn't working. You quickly diagnose and fix it, and they're able to join on time. That's a good day for you.

Learning New Technology

You're always keen to understand how new software or hardware works, even if it's just for a basic fix. You enjoy diving into a new system to figure out its quirks.

When a new security tool is rolled out, you're one of the first to read the documentation and ask questions, eager to understand how it protects our systems.

Being Part of a Supportive Team

You appreciate having colleagues you can ask for help, and you're happy to chip in when someone else is swamped. You like the camaraderie of working together to tackle the daily queue.

You're struggling with a tricky Wi-Fi issue, and your Senior Analyst jumps on a call with you to walk through it, teaching you a new diagnostic trick along the way.

What frustrates people

Dealing with users who mark a simple password reset as 'Business Critical' when you know there are genuinely urgent issues waiting in the queue.
Spending ages troubleshooting an issue, only for the user to casually mention they installed some unsupported software yesterday that's clearly the cause.
Having to enforce unpopular but necessary security policies (like mandatory multi-factor authentication) and taking the heat from frustrated colleagues.
The sheer monotony of resolving the same five basic issues (password resets, printer mapping, VPN access) dozens of times a day.
Being the scapegoat for a slow network or a buggy software update that was actually pushed by a completely different team.
Solving a technical issue perfectly, but still getting a low CSAT score because the user was just having a bad day and you couldn't fix that for them.

What this role does not give you

You won't be designing new IT systems or setting strategy here; that's for more senior roles.
You won't have a lot of autonomy to deviate from established procedures; consistency is key at this level.
You won't be working on cutting-edge research or development; your focus is on stable, reliable support.
You won't be managing a team or a budget; your impact is individual contribution.

6Who you work with

This role is absolutely critical for maintaining daily business operations. You're the first line of defence against lost productivity. If you're quick and effective, our employees can focus on their jobs without tech getting in the way. If support is slow or ineffective, it can cause widespread frustration and really slow down important work across the whole organisation. You're basically the engine oil that keeps the machine running smoothly.

Inside the business

All company employees (our end-users)
Your immediate Help Desk team colleagues
Senior Help Desk Analysts (your mentors and escalation point)
IT Operations team (for infrastructure issues)
HR team (for new starter setups and leaver processes)

Outside the business

None directly, your focus is purely internal support at this level.

7What you need before you start

Not a wish list. The things you would be expected to already have.

A genuine interest in technology and a desire to learn how things work.
Previous experience in a customer service role (any industry) where you regularly helped people solve problems.
Basic computer literacy: you can navigate Windows/macOS, use office applications, and understand how to connect to the internet.
Excellent communication skills, both written and verbal, in English.
The ability to remain calm and professional when dealing with frustrated users.
A strong work ethic and a willingness to follow instructions and learn from feedback.

8What to practise next

Where the job is going, and what to do about it starting this week.

Intermediate Scripting (PowerShell/Bash)

While you start by running pre-written scripts, the next step is to understand them, then modify them, and eventually write simple ones yourself. This will allow you to automate repetitive tasks you encounter daily, saving yourself and your team time.

Basic command syntax and parameters · Variables and data types · Conditional logic (if/else statements) · Looping constructs (for/while loops) · Error handling basics

This week: Ask your Senior Analyst to explain a script you frequently use, line by line.
This month: Take an online course on PowerShell or Bash basics (e.g., Codecademy, Udemy).
Month 2: Try to modify a simple existing script to do something slightly different.
Month 3: Attempt to write a very basic script to automate a task you do manually every day (e.g., checking a service status).

Quick win: Start by simply reading the scripts you execute. Try to guess what each line does. It's like learning a new language, one word at a time.

Deeper Network Diagnostics

Many user issues stem from network problems. Moving beyond basic 'ping' commands to understanding network topology, DHCP, DNS, and VPN issues will make you a much more effective troubleshooter, reducing escalations.

TCP/IP fundamentals · Subnetting and routing basics · DNS resolution process · VPN connection troubleshooting · Firewall concepts (basic)

This week: Ask the Network team for a quick 15-minute chat about common network issues they see.
This month: Read up on how DHCP and DNS work in simple terms. There are loads of great YouTube videos.
Month 2: Learn to use tools like `tracert` or `nslookup` and understand their output.
Month 3: Try to diagnose a 'slow internet' issue by looking at router logs (if accessible) or using more advanced network commands.

Quick win: Whenever a user reports a network issue, spend an extra 5 minutes trying to understand the underlying cause before escalating. Ask 'why' it happened.

9Staying current once you are in

What people here do to keep up

Shadowing senior colleagues to see how they tackle complex issues and interact with users.
Actively participating in team training sessions and sharing your own learnings.
Taking online courses (e.g., on LinkedIn Learning, Udemy, Coursera) in areas like basic networking, Windows administration, or customer service skills.
Building your own 'lab' at home – even a virtual one – to experiment with different operating systems or software configurations.
Attending industry webinars or local tech meetups to stay updated on new trends and tools.

10How the AI economy is changing work like this

Before we ask anything of you, here's what we can already say about AI and work of this kind:

The new skill this role is being asked for: Prompt Engineering for Support Tools

AI is already integrated into our ticketing systems and knowledge bases. Knowing how to ask the right questions (or 'prompts') to these AI tools will unlock faster, more accurate solutions for you. Technicians who master this will be significantly more efficient.

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

Prompt Engineering for Support Tools

AI is already integrated into our ticketing systems and knowledge bases. Knowing how to ask the right questions (or 'prompts') to these AI tools will unlock faster, more accurate solutions for you. Technicians who master this will be significantly more efficient.

Clear and concise prompting for specific issues
Providing context to AI for better answers
Iterative prompting to refine results
Understanding AI limitations and when to trust its
Using AI to summarise long ticket histories

What you’ll use

Skills this role draws on

Technical

ITIL Framework (Basic Incident Management)
Knowledge-Centered Service (KCS) Principles
Basic Root Cause Analysis (RCA)
SLA/SLO Awareness
Security Incident First Response

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

1
Customer Service Representative to Help Desk
6-18 months
Skills to master
- Transferring your excellent communication and problem-solving skills to a technical context, learning basic IT terminology, understanding technical troubleshooting methodologies.
You're ready to move on when
- You're already the 'go-to' person for basic tech issues among your current colleagues.
- You enjoy figuring out how things work and helping others with their tech problems.
- You've started self-studying basic IT concepts (e.g., networking, operating systems).
2
IT Apprenticeship / College Leaver
0-6 months
Skills to master
- Applying theoretical knowledge to real-world user problems, developing strong customer service instincts, learning our specific internal systems and processes.
You're ready to move on when
- You've completed an IT-focused apprenticeship or BTEC and are eager for your first full-time role.
- You have a foundational understanding of IT concepts and are keen to put them into practice.
- You're comfortable with the idea of being the first point of contact for technical issues.
3
Self-Taught Enthusiast
Varies (often 1-3 years of dedicated self-study)
Skills to master
- Formalising your technical knowledge, developing professional communication skills, understanding corporate IT environments and security best practices.
You're ready to move on when
- You've built your own computers, tinkered with home networks, or self-studied for certifications like CompTIA A+.
- You have a portfolio of personal tech projects or demonstrable troubleshooting experience.
- You can articulate complex technical concepts clearly and concisely to non-technical people.

11Where this role leads

The long view:Your journey here starts with helping people, but where it goes is really up to you. We'll give you the tools, the training, and the opportunities to explore different paths within IT. The most important thing is your willingness to learn and your drive to make things better for our users.

Pay & demand

Pay and demand for this role will appear here, each figure traced to a named authoritative source (e.g. the ONS Annual Survey of Hours and Earnings, under the Open Government Licence). We don’t show numbers we can’t attribute.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Help Desk Technician I is actually changing. In about two minutes, the free confidence check asks where you stand on each of the ten. That's the whole check, and it's what makes the plan yours rather than generic.

12The team that's yours

No two people are taught the same way. This is one-to-one, not one-to-many.

Zavmo is a hyper-personalised AI learning platform. Twelve virtual tutors, each with a different way of teaching, and one orchestration agent that picks the right one for the moment. So every single lesson is shaped around you, your role, and the way you learn. Not a course everyone sits through. A conversation built for you, and no one else.

…and nine more, matched to you after your first chat. Meet all twelve

Start free and meet yours

13What it feels like

A conversation, not a course

Because your tutor knows your role, your projects and your last session, learning sounds like this. And it's different for every single person:

IT Software FundamentalsLevel 2

Applied to your work in Help Desk Technician I

The objective of this unit is to provide learners with a fundamental understanding of IT software and its applications. Learners will be able to select and use appropriate software to meet specific needs, develop and format information effectively, and present information clearly and concisely using IT tools.

How the thinking builds

Remember
Understand
Apply
Analyse
Evaluate
Create

An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

One to one, not one to many

No two people run this the same way

A course is written once and handed to everyone. This is assembled around you, and keeps changing as it learns you. Five things it reads, and what each one changes.

Your actual work Every lesson is taught against a live piece of your own work, not a worked example from a textbook.
What you already know The first conversation finds your starting point, so you skip what you can already do and spend the time on what you cannot.
The conditions you learn under Not a learning-styles quiz. The evidence does not support those. The dimensions the research does back, read once and used to shape the plan.
How far you got last time It picks up mid-thought. The tutor knows what you said, what you struggled with, and what it asked you to try.
Which tutor suits the moment Twelve of them, each for a different kind of thinking. The one who walks you through a first idea is not the one who stress-tests it.

See how you learn, free. Eight questions, no sign-up. A directional taster; the diagnostic inside Zavmo goes deeper and keeps adapting.

DemonstrateIllustration

Evidenced on your work in Help Desk Technician I

You do not finish by watching something. You finish by showing it on the work you already do, against the measures this job is judged on.

First-Contact Resolution (FCR)The percentage of issues you fix on the very first interaction with a user, without needing to pass it on or follow up later.You take a call about a password reset, fix it there and then, and the user confirms it's sorted before you hang up. That's an FCR.> 70%
Average Handle Time (AHT) for Tier 1 IssuesThe average amount of time you spend on a ticket, from when you open it to when you close it, specifically for those simpler, routine problems.A user calls about a printer not working. You spend 15 minutes troubleshooting, reinstalling drivers, and testing, then close the ticket. That's within target.< 20 minutes
Customer Satisfaction (CSAT) ScoreThis is how happy our users are with the support you've provided, based on a quick survey they get after their ticket is closed.You help a user with a tricky software installation, they leave a 5-star rating and a comment saying 'really helpful and patient!'> 4.5 out of 5.0
Ticket Documentation QualityHow well you've logged the problem, what you did to fix it, and any relevant notes in the ticketing system. This helps everyone later.A Senior Analyst reviews your tickets and finds that 98% of them clearly state the issue, steps taken, and resolution, following our internal guidelines.95% adherence to template

These are this job's own measures, with its own targets. Nothing is marked evidenced, because nobody has started this yet. Yours would fill in from the work you bring.

Your passport

This isn't a certificate you file away. It's a passport to the life you're designing.

Every credit you earn and every fluency you build adds up: evidence where it counts, carried with you. Zavmo keeps the map: where you are, where you're heading, and the next step, at your pace, around your life. From Help Desk Technician I to Help Desk Technician II (Mid-Level), and whatever you decide comes after.

Level 2 · in progressAI Fluency→ Help Desk Technician II (Mid-Level)→ your design

Where this takes you

Your journey here starts with helping people, but where it goes is really up to you. We'll give you the tools, the training, and the opportunities to explore different paths within IT. The most important thing is your willingness to learn and your drive to make things better for our users.

See Your Progress GrowIllustration

Help Desk Technician I

ITIL Framework (Basic Incident Management)
Knowledge-Centered Service (KCS) Principles
Basic Root Cause Analysis (RCA)
SLA/SLO Awareness
Security Incident First Response

This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

14The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Help Desk Technician I is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

Help Desk Technician II (Mid-Level)
2-3 years in current role
Level 2 (Mid)
- Intermediate Scripting: Writing simple scripts to automate routine tasks.
- Advanced Troubleshooting: Diagnosing complex software and network issues.
- Knowledge Base Contribution: Creating and editing new articles following KCS principles.
- Basic System Administration: Managing user accounts, group policies, and application deployments.
Junior IT Systems Administrator / Junior Network Engineer
3-4 years in current role (or 1-2 years as Technician II)
Level 2-3 (Mid to Senior)
- Server Administration (basic): Managing virtual machines, file shares.
- Network Configuration (basic): Understanding router/switch configurations.
- Cloud Fundamentals: Working with Azure or AWS services.
- Security Operations (basic): Monitoring security alerts, incident response.

Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, some parts of help desk work can be a bit of a grind. But what if you could offload the repetitive stuff and focus on the interesting problems? That's where AI comes in. We're not talking about robots taking over your job; we're talking about smart tools that make your life easier, helping you get to solutions faster and communicate more clearly.

In Technical_roles, especially at the help desk, AI isn't some far-off concept. It's already here, helping us sort tickets, find answers, and even draft communications. As a Help Desk Technician I, you'll be using these tools daily, making your work more efficient and giving you more time to learn and grow. Think of it as having an incredibly smart, tireless assistant.

Ticket Triage & Routing Automation

Imagine incoming tickets automatically categorised, prioritised, and sent to the right specialist before you even see them. AI reads the ticket, understands what the user needs (is it a hardware issue? A software bug? An access problem?), and routes it correctly. This means less time spent manually sorting and more time actually solving problems. You'll get tickets that are already pre-digested and ready for action.

Instant Knowledge Base Suggestions

As you type in a ticket or chat with a user, an AI assistant pops up with relevant knowledge base articles, troubleshooting checklists, and even suggested canned responses right there in your ticketing system. No more endless searching; the answers come to you. This cuts down on your average handle time and ensures you're always giving consistent, accurate advice.

Automated User Communication Drafts

When there's a planned outage or a major incident is resolved, AI can draft clear, jargon-free communications for end-users based on the technical resolution notes. This means less time for you (or your Senior Analyst) to 'translate' complex tech into simple language. You'll be able to send out updates quickly, keeping everyone informed without the manual effort.

Proactive Problem Detection

While you won't be building this, you'll benefit from it. AI analyses system logs and ticket trends, spotting unusual spikes (like lots of 'slow login' tickets from one specific office). It can even auto-generate a 'problem' ticket before it becomes a major outage. This means fewer 'ticket swarms' for you to deal with, as issues are caught and addressed earlier.

Common questions

How do you become a Help Desk Technician I?

Common routes in include Customer Service Representative to Help Desk (6-18 months), IT Apprenticeship / College Leaver (0-6 months) and Self-Taught Enthusiast (Varies (often 1-3 years of dedicated self-study)). Times vary with prior experience.

Where can a Help Desk Technician I progress to?

This role can lead on to Help Desk Technician II (Mid-Level) (2-3 years in current role) and Junior IT Systems Administrator / Junior Network Engineer (3-4 years in current role (or 1-2 years as Technician II)), depending on the skills you build.

What level is a Help Desk Technician I in the UK?

This role aligns to RQF Level 2 on the UK framework, a guide to the depth of qualification it maps to, not a hard entry bar.

What new skills matter most for a Help Desk Technician I?

Increasingly, Prompt Engineering for Support Tools. These are the areas where the higher-paid, future-proof work is heading.

The honest bit

You’ve started things before

Most of them were built for a room full of people who aren’t you. A cohort moves on whether or not your week allowed it, and by the third week the thing you’re behind on becomes the reason you stop opening it.

There’s no cohort here, and no timetable to fall behind. Before anything starts, Zavmo asks when you’re sharpest and how long you can realistically sit down for, then builds the sessions around those answers. A bad fortnight changes your pace. It doesn’t put you behind.

And you only pay once you start learning. Searching and planning are free, and you can cancel any time — so the cost of finding out is an afternoon, not a year.

What it costs

Less than one coaching session. Every month.

A single career-coaching hour costs more than a month of this, and it ends when the hour does. Zavmo doesn't. It's £70 a month, about £2.30 a day, for a companion that knows a Help Desk Technician I, works on the job you actually do, and keeps going at your pace rather than a timetable's.

Searching and planning stay free. You only pay when you start learning.
Your credits are yours. Regulated, and they don't vanish when a subscription ends.
Cancel any time and billing stops. No notice period, no minimum term.

Your path, personalised

You have the map. Walking it is the part we do together.

This route runs to 12 national skill standards. That is a real journey.

Zavmo shapes a learning experience as unique as you are. It fits how you learn, your pace and the work you already do. Every step stays benchmarked to recognised national standards. That’s the plan for becoming a Help Desk Technician I: personal to you, and it still counts. The first steps are free.

Independent research finds well-designed intelligent tutoring performs nearly as well as one-to-one human tutoring: VanLehn (2011), Educational Psychologist.

A private tutor in the UK averages £35–40 an hour . Zavmo is £70/month.

A Zavmo curriculum screen: a three-month plan built for a customer support lead, five Ofqual-regulated units and a hundred and ninety-six credits. — A real plan on learn.zavmo.ai: Ofqual-regulated units, credits, and a three-month run at your own pace.

Start free No commitment. See your first steps free.

15Where to go from here

Other roles at Level 2

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

Other roles in Technical roles

Stay in the field you know and move sideways rather than up.

If you leave this industry

The skills you gain in Help Desk Support are incredibly transferable. You could move into dedicated IT Security, Cloud Operations, or even IT Project Management. Every company needs IT support, so your skills are always in demand, regardless of the industry.

Not sure this is the right direction?

Work out what you actually want from work first, then come back and see which roles fit it. Takes about ten minutes.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Build my plan, free Here's the first ten minutes: a 2-minute confidence check → your personalised roadmap → meet the tutors matched to you. No card, cancel any time. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.

Help Desk Technician I

What's rising in its place

Prompt Engineering for Support Tools

Skills this role draws on

Technical

How you actually get there, here

Customer Service Representative to Help Desk

IT Apprenticeship / College Leaver

Self-Taught Enthusiast

The credential is what you can do today. These are what keep you valuable.

Roles this leads to

No two people are taught the same way. This is one-to-one, not one-to-many.

A conversation, not a course

No two people run this the same way

This isn't a certificate you file away. It's a passport to the life you're designing.

Your journey here starts with helping people, but where it goes is really up to you. We'll give you the tools, the training, and the opportunities to explore different paths within IT. The most important thing is your willingness to learn and your drive to make things better for our users.

Everything else the record holds

The career path, and where it branches