What should an IT support technician's cover letter actually say?

Where this letter gets read, and where it doesn't

It depends heavily on the size and shape of the employer, more than in most occupations.

At a small managed service provider or an in-house IT team of a handful of people, the person hiring is often the lead engineer or the IT manager themselves, and they are reading every application because there aren't many. In that setting the letter genuinely gets read, because it's the only writing sample they have of how you'd sound on a call with a client or an angry end user.

At a large service desk — a corporate first-line team, an outsourced call centre, an NHS trust or a local authority running hundreds of tickets a day — applications usually go through a recruiter or an applicant tracking system first. That system, and the human triaging behind it, is built to filter on the CV: named tools, years of experience, certifications. The cover letter attachment often isn't opened at that stage, and some ATS setups don't parse it at all. If you're applying to a role like that, assume the CV does the filtering and the letter, if it's read, comes later.

There's no reliable way to tell which situation you're in from the advert alone, but a rough signal: if the advert names a specific site, a specific number of users, or was clearly written by someone technical rather than HR, a human is probably closer to the process.

The two things it actually has to answer

Most of the advice about cover letters is generic enough to apply to any job. For IT support specifically, a hiring manager reading one is checking for two things, and not much else.

Can you talk to someone who isn't technical without patronising them or losing them in jargon. This is the actual job, more than the troubleshooting. A CV bullet point that says "resolved 40+ tickets daily" tells them nothing about how you handled the call. One short example does: a user who couldn't print, was already frustrated, and what you said to get from "it's broken" to a diagnosis without making them feel stupid. That's worth more than any adjective.

Does your technical scope match what they run. Not "strong troubleshooting skills" — which environment, which tools. First-line or second-line. Remote-only or on-site with a hardware element. Windows-only estate or mixed with macOS. If the advert names ServiceNow, Freshservice, Zendesk or Jira Service Management, say which one you've used and how, because those tools differ enough in how they queue and escalate work that "ticketing system experience" alone tells a hiring manager nothing.

If your letter answers both of those in the first two paragraphs, it's done its job. Everything else is decoration.

Naming the stack, not just claiming competence

This is the section people skip because it feels like restating the CV, but it's the part that actually differentiates one applicant from another in this field. Compare:

"I have excellent troubleshooting skills and a strong customer focus."

against

"I've worked first-line tickets in ServiceNow against a four-hour SLA for P2 incidents, handled AD account lockouts and password resets, and imaged and deployed laptops through Intune for a 300-user estate."

The second sentence is checkable and specific to this job. The first would survive being pasted into a cover letter for a retail assistant role with almost no edits, which is exactly the test a hiring manager applies without thinking about it — does this paragraph belong to this job, or any job.

If you hold CompTIA A+ or Network+, Microsoft's MD-100/MD-101, or an ITIL Foundation certificate, and the advert mentions any of ITIL process, change management or a formal SLA structure, say so by name. If the advert doesn't mention ITIL, don't lead with it — it signals you're pattern-matching your letter rather than reading their advert.

Where the letter carries little weight — and where the real decision gets made

For high-volume first-line roles, the actual filter is usually a phone screen or a practical exercise: a mock ticket, a remote take-control demonstration, sometimes a typing or ticket-logging speed check. The letter doesn't predict any of that, and hiring managers running high-volume desks generally know it. Some don't request one at all.

For roles that are explicitly client-facing — MSP engineers who go on-site, education IT technicians dealing with staff and students, roles in smaller organisations where you're the only technical person most people ever speak to — the letter carries more genuine weight, because the writing itself is a small sample of the communication skill the job needs.

Worth being honest about the limit either way: a well-written letter will not get you an interview if the CV doesn't show the right tools and environment, because in most processes the CV is screened first and the letter is only read once you've already passed that filter. Put the effort into making sure the advert's specific stack — the OS, the ticketing system, the scale of the estate — appears clearly on the CV before you polish the letter around it.

What to put in it, in order

Keep it to three short paragraphs, half a page at most.

First: the role, where you saw it, and one line on why this employer specifically — their device fleet, their sector, their number of sites, something that shows you read the advert rather than mail-merging it.

Second: the technical match, named precisely, plus the one example of handling a difficult or non-technical user well. This paragraph does the actual work described above.

Third: anything procedural the role needs — a DBS check if it's a school or NHS trust, right to work if relevant, availability for shift patterns if the desk runs extended hours, willingness to travel between sites if it's a field-based MSP role. This is administrative, not persuasive, and it belongs at the end.

What not to bother with

Don't restate the CV chronologically — the reader has the CV. Don't open with "I am a hardworking team player with excellent communication skills"; every line of that sentence is a claim the rest of the letter should be proving with specifics, not asserting up front. Don't explain what ITIL or Active Directory are — the reader already knows, and explaining it reads as padding. And don't apologise for gaps in your stack; if the advert asks for macOS support and you've only worked Windows, say what you have worked and let the rest of the letter carry the case, rather than drawing attention to the gap in the opening line.

What to do next

Pull the advert apart before you write anything: list every named tool, OS, ticketing system and certification it mentions. Match each one against what you've actually used, and write the technical paragraph from that list, not from memory of what you usually say. Then write the one example of a difficult call or ticket, in two or three sentences, no more. Send it as a PDF if you're emailing it directly, since plain text pasted into an email body loses formatting and sometimes gets flagged by spam filters as unusual. jobmarket.pro reads the advert for the specific tools, systems and environment it names and drafts the letter from your existing profile without inventing tools or certifications you don't actually hold.