02
IT Support Maturity Model · Tier 02

Level 2 — Intermediate Support

Desktop & Network Support. Where support transitions from following instructions to solving puzzles — the critical linchpin of a scalable, multi-tiered IT support model.

L1 · Basic Support L2 · Intermediate L3 · Advanced L4 · Beyond Break/Fix
1

Core Philosophy — Deep Dive & No Repeat

Level 2 is the analytical engine of the support structure. While Level 1 relies on scripts and known solutions, Level 2 relies on diagnostic reasoning.

Rule One

The “No Repeat” Rule

The most critical first step is to thoroughly review the L1 work order: what symptoms were reported, what troubleshooting steps L1 already attempted, and how much time the user has already spent on the issue.

Rule Two

Trust but Verify

L2 does not blindly accept L1’s conclusions. They verify the validity of the problem and the accuracy of prior troubleshooting — preventing the frustrating “Yes, I already restarted it three times” experience and ensuring efficient prioritization.

2

The Level 2 Support Workflow

  1. 1

    Intake & Review

    Read the entire ticket history — noting L1’s actions, user environment details, and time elapsed.

  2. 2

    Validation

    Contact the user (if necessary) to validate the current state of the issue and confirm no new variables have been introduced since the L1 interaction.

  3. 3

    Advanced Diagnostics

    Move beyond basic checklists — use system logs, network traces, and diagnostic utilities to isolate the root cause.

  4. 4

    Intervention

    Apply a targeted fix. This may involve remote control of the machine, modifying Group Policy Objects (GPOs), or dispatching for physical hardware replacement.

  5. 5

    Verification & Documentation

    Confirm with the user that the system is fully functional — then document the exact root cause and resolution steps.

  6. 6

    Resolution or Escalation

    If resolved, close the ticket. If it is a novel bug, requires code-level changes, or indicates systemic infrastructure failure, escalate to Level 3 with a comprehensive diagnostic report.

3

Typical Use Cases — The “Messy Middle”

Issues too complex for a script, but not requiring enterprise architecture redesign.

Network & Connectivity

Intermittent VPN drops, Wi-Fi authentication failures (802.1x), IP conflicts, and localized switch port issues.

Endpoint & OS Management

Repairing corrupted Windows/macOS user profiles, fixing broken Windows Update cycles, and resolving complex Outlook .OST/.PST corruption.

Hardware Lifecycle

Diagnosing failing components (bad RAM, failing SSDs), performing onsite replacements, and coordinating advanced RMA processes with vendors.

Application & Licensing

Troubleshooting software licensing conflicts, resolving application crashes via event log analysis, and fixing permission issues on network drives.

4

Deep Dive into Key Responsibilities

Advanced Diagnostics

L2 moves from “guessing” to “knowing” — analyzing Event Viewer logs, running network traces, and interpreting error codes to pinpoint the exact failure point.

Remote & Onsite Support

L2 holds the elevated permissions required for hands-on troubleshooting, and is often the “boots on the ground” for physical interventions — replacing a broken laptop or troubleshooting a localized network closet.

Knowledge Management

L2 is responsible for “shifting left.” When a new or complex issue is solved, L2 writes or updates the KB article so L1 can handle it independently next time.

Collaboration & Mentorship

L2 acts as a bridge — mentoring L1 on emerging issues and collaborating with L3 to identify whether a cluster of L2 tickets points to a larger systemic infrastructure problem.

L2 solves it NEW / COMPLEX ISSUE
L2 documents it KB ARTICLE CREATED
L1 owns it SHIFT LEFT
5

Required Skills & Competencies

A significant step up in both technical breadth and analytical depth compared to Level 1.

Technical Skills

  • Working knowledge of TCP/IP, DNS, and DHCP.
  • Proficiency in Active Directory — managing user/group policies and security groups.
  • Experience with MDM platforms for enforcing endpoint compliance.
  • Strong OS-level diagnostics for Windows, macOS, and basic Linux.

Soft Skills

  • Analytical & critical thinking — connecting disparate symptoms to a single root cause.
  • Ability to work independently with minimal supervision.
  • Structured methodologies — e.g., CompTIA: identify the problem, establish a theory, test it, form a plan, verify, document.
6

Essential Tools of the Trade

Advanced Remote Support

BeyondTrust, TeamViewer, AnyDesk — operated with elevated administrative privileges.

Network Diagnostics

Ping, Traceroute, NSLookup, and packet analyzers like Wireshark for deep network troubleshooting.

Endpoint Management

Microsoft Intune, Jamf Pro, SCCM — pushing configurations, scripts, or software repairs remotely.

System Diagnostic Utilities

Sysinternals Suite (Process Monitor, Autoruns), Windows Event Viewer, macOS Console, CrystalDiskInfo.

Wireshark Sysinternals Intune Jamf Pro SCCM BeyondTrust NSLookup Event Viewer
7

Key Performance Indicators

L3 Rate

Escalation Rate to L3

A healthy L2 team resolves the vast majority of escalated tickets. A high rate signals a need for better L2 training or tools.

MTTR

Mean Time to Resolve

Average time to fully resolve an L2 ticket — the core measure of diagnostic efficiency.

FTF

First-Time Fix Rate

Percentage of L2 tickets resolved without multiple user contacts or further escalation.

KB

Knowledge Base Contributions

Number of new or updated KB articles created by L2 technicians to empower L1.

8

Strategic Business Value

Level 2 is the backbone of operational continuity and cost control.

Protects High-Cost Resources

By effectively filtering and resolving complex-but-known issues, L2 ensures highly paid L3 engineers and developers are not distracted by routine endpoint or network problems.

Minimizes Business Downtime

Rapid, advanced diagnostics plus onsite/remote interventions directly reduce the amount of time employees are unable to work — protecting productivity.

Drives Long-Term Efficiency

Through rigorous documentation and KB updates, L2 continuously trains the L1 tier — organically raising overall First-Contact Resolution and lowering the total cost of support.

The linchpin effect: L2 sits between script and architecture. Every documented fix pushes knowledge downward, every unresolved pattern pushes insight upward.

Level 2 · Intermediate Support (Desktop — Network Support)