Desktop Support Scope: What L1 and L2 Desktop Support Should Cover

The short version: Desktop support looks after the devices and software your staff use every day: laptops, desktops, printers, accounts, Microsoft 365 and the apps on them. L1 fixes routine problems from a script or knowledge-base article. L2 takes anything that needs deeper troubleshooting, admin rights or a visit. Write the boundary down as a list, because "desktop support" without a list means different things to different people.

This guide is for the person who has to buy, write or check a desktop support scope: an office manager, a finance lead, or the one person who is also "the IT person". After reading it you can mark each task as L1, L2 or out of scope, and use the checklist at the end in a contract or a service description.

What does L1 desktop support cover?

L1 is the first contact. It handles problems that have a known fix.

• Accounts and access: password resets, account unlocks, MFA re-registration, adding a user to a standard group.
• Microsoft 365 how-to and basic faults: Outlook profile problems, Teams sign-in, OneDrive sync errors, mailbox full.
• Printing: adding a printer, clearing a stuck queue, driver reinstall.
• Standard software: installing or removing approved applications.
• Basic connectivity checks: Wi-Fi, VPN client, "is it me or everyone".
• Peripherals: monitors, docking stations, headsets, keyboards.
• Logging and triage: every contact becomes a ticket with a priority; known outages are linked to one parent ticket.

What does L2 desktop support cover?

L2 takes what L1 cannot close, and does planned device work.

• Deeper troubleshooting: slow or crashing devices, profile corruption, application faults, blue screens, failed updates.
• Device lifecycle: build or re-image a laptop, enrol it in device management, hand it to a new starter, collect it from a leaver.
• Policy and permissions: group membership beyond the standard set, shared mailbox and folder permissions, device policies.
• Hardware faults: diagnose, arrange warranty claims, swap parts where the contract allows.
• On-site work: a visit when remote fixes fail, or for physical tasks. See onsite vs remote IT support.
• Patterns: raising a problem record when the same fault keeps coming back, and updating the knowledge base.

For the tier model behind this split, read L1, L2 and L3 support levels.

What is often left out of desktop support?

These are the items that cause disputes. Decide each one in advance and write it down.

• Business applications (finance, ERP, line-of-business software): usually vendor-supported; desktop support only checks the device side.
• Personal or BYOD devices: often "best effort" or excluded. Name who approves exceptions, for example the IT owner or a manager.
• Servers, firewalls and network design: a separate scope.
• Hardware purchase and disposal: procurement and secure disposal are usually separate services.
• Out-of-hours work: depends on the service window you contract.
• Training: one-off how-to is L1; formal training is a separate item.

Which common tickets belong where?

The levels below are examples. Your own scope list decides.

• Forgot password / locked account: L1.
• Outlook will not open or keeps asking for a password: L1 first, L2 if the profile or sign-in token is damaged.
• New starter laptop and accounts: service request, L2.
• Laptop very slow: L1 checks the basics; L2 investigates disk, memory, startup items and updates.
• Printer offline for one user: L1. Printer offline for everyone: L2, possibly network or print server.
• Software install request: L1 if the app is on the approved list; otherwise approval first.
• Shared mailbox or folder access: L2, with the data owner's approval.
• Lost or stolen device: treat as a security incident and escalate straight away.

What do example handling times look like?

The numbers below are an example only, to show the shape of a time table. They are not Brocent data and not a market standard. Your contract and the SLA page set the real targets.

• Example, P1 (many users down or a security risk): first response within 15 minutes, update every 30 minutes until restored.
• Example, P2 (one team blocked): first response within an hour, update every 2 hours.
• Example, P3 (one user blocked, workaround exists): first response within 4 business hours, resolve in 1 to 2 business days.
• Example, P4 (question or minor issue): first response the same business day, resolve within 5 business days.
• Example, service request (new starter): agreed lead time, for example 3 business days from a complete request.

To understand the priority labels, see P1 to P4 priority levels in an IT support SLA.

What should a desktop support scope checklist contain?

Copy this list into your contract or service description and fill every line.

1. Supported devices: Windows, macOS, mobile; company-owned only or BYOD too.
2. Supported software: the approved application list, and who adds to it.
3. Service window: days and hours for L1 and for L2.
4. Channels: phone, email, portal, chat; which are monitored when.
5. Priority table: definitions, first-response and resolution targets, replace the example numbers with agreed ones.
6. On-site visits: when they are included, how they are booked, and travel limits.
7. Hardware handling: who diagnoses, who claims warranty, who holds spares.
8. Starter and leaver steps: lead time and a named approver.
9. Escalation path: who is called when a target is about to be missed. See the IT escalation matrix template.
10. Reports: tickets by type, first-contact resolution, reopened tickets, monthly.

Common mistakes

• Writing "all IT support" instead of a list. Then every disagreement is a scope argument.
• Forgetting starters and leavers. They create the most predictable work and are often unscoped.
• No approval rule for access requests. Support should not grant access on a user's word alone.
• Counting remote-only as full desktop support. Say clearly when a visit is included.
• Measuring only speed. Also track reopened tickets and first-contact resolution.

How to check it worked

1. Take the last 20 tickets you raised. For each, check that the checklist tells you who should have handled it.
2. Count how many were "not covered" or unclear. More than a couple means the scope needs another pass.
3. Review the monthly report: reopened tickets and repeat tickets from the same user or device point to a gap in L2 or the knowledge base.
4. Ask three staff what they would do first when something breaks. If they say "ask a colleague", the entry route is not clear enough.

FAQ

What does a desktop support engineer do?

They set up, maintain and fix staff devices and the software on them. They take tickets, troubleshoot, build and enrol laptops, manage accounts and permissions, and hand harder problems up.

What is desktop support?

It is the service that keeps users' computers, printers, accounts and standard software working. It is usually split into L1 for routine fixes and L2 for deeper or hands-on work.

Do you need a certification for desktop support?

There is no single required certification. Employers differ: some ask for vendor certificates in Windows, Microsoft 365 or networking, others value experience. Check the job or contract requirements.

What qualifications do you need for IT desktop support?

Practical knowledge of Windows and macOS, Microsoft 365 administration basics, networking basics, troubleshooting method and clear written communication. Qualifications vary by employer.

Next step

If you want the scope above delivered as a service, see Brocent's IT support service.

Brocent publishes its managed IT support plans with per-user monthly prices for Hong Kong, Singapore, mainland China and the United States, so you can compare before you talk to anyone: see the plans and pricing.