01
IT Support Maturity Model · Tier 01

Level 1 — Basic Support

Frontline / Help Desk. The critical filter and foundation of the IT support ecosystem — built on strict process adherence, excellent communication, and disciplined knowledge management.

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

Core Philosophy — Symptom vs. Underlying Problem

Symptom

What the user says is wrong

“My internet is broken.” · “My computer is slow.” · “I can’t save my file.”

Underlying Problem

The actual root cause

Whatever is genuinely preventing the user from achieving their goal.

The L1 approach: instead of immediately troubleshooting the symptom (e.g., restarting the router), ask “What are you trying to accomplish right now?” If the answer is “I’m trying to print a document,” shift focus to the printer — checking if it’s offline or out of paper — rather than the network. This prevents wasted time and resolves the issue faster.

2

The Level 1 Support Workflow

  1. 1

    Ingestion & Greeting

    The request arrives via phone, email, chat, or portal. Greet the user professionally and verify their identity (security protocol).

  2. 2

    Information Gathering

    Ask targeted, open-ended questions to understand the goal, the symptoms, and the environment — “Are you on Wi-Fi or Ethernet?” · “What error message do you see?”

  3. 3

    Triage & Categorization

    Log the issue in the ITSM tool, tag it with the correct category (e.g., “Hardware > Printer”), and assign a priority based on business impact.

  4. 4

    Diagnosis & Resolution

    Consult the Knowledge Base (KB) or standard operating procedures (SOPs) and apply a known fix.

  5. 5

    Verification

    Ask the user to confirm the issue — and their original goal — is met.

  6. 6

    Closure or Escalation

    If resolved, close the ticket with detailed notes. If not, escalate to Level 2 with a complete audit trail.

3

Typical Use Cases

Level 1 handles high-volume, low-complexity, highly repetitive tasks.

Identity & Access

Password resets, MFA token resets, unlocking accounts, and guiding users through self-service password portals.

Hardware & Peripherals

“No power” troubleshooting (cables/outlets), connecting Bluetooth devices, mapping network printers.

Software Support

Installing approved pre-packaged software (Microsoft Office, Adobe Reader), clearing browser caches, guiding users through application menus.

Account Lifecycle

Provisioning new hires (email accounts, license assignment) and deprovisioning departing employees (revoking access).

4

Deep Dive into Key Responsibilities

Triage & Categorization

Accuracy is vital. Mis-categorizing a ticket (e.g., labeling a network outage as a “single user password issue”) delays response and skews business metrics.

First-Contact Resolution (FCR)

The ultimate L1 goal. Technicians are empowered to resolve issues on the first interaction using scripts, checklists, and the internal Knowledge Base.

Expectation Management

If an issue can’t be solved immediately, clearly communicate what happens next, who will handle it, and when to expect an update — reducing anxiety and “chaser” tickets.

Structured Escalation

Escalation is not “dumping” a ticket. A proper L1 escalation includes user contact info and environment details, exact error messages or screenshots, and a detailed list of troubleshooting steps already attempted.

5

Required Skills & Competencies

Technical depth matters less than breadth and process adherence.

Soft Skills — the differentiator

  • Active listening & empathy: de-escalating frustrated users by validating their concerns.
  • Translation: explaining technical concepts in plain, non-technical language.
  • Patience: guiding non-technical users step by step without sounding condescending.

Technical Skills

  • Basic navigation and troubleshooting of Windows 10/11 and macOS.
  • Familiarity with SaaS platforms — Microsoft 365, Google Workspace, Zoom, Teams.
  • Understanding of the OSI Model’s Physical Layer (cables, power, basic connectivity).
  • Ability to follow documented SOPs precisely.
6

Essential Tools of the Trade

ITSM / Ticketing Platforms

ServiceNow, Jira Service Management, Zendesk, Freshservice — logging, tracking, and routing tickets.

Knowledge Base Systems

Confluence, SharePoint, or integrated ITSM wikis — the L1 technician’s primary source of truth.

Remote Support Viewers

TeamViewer, AnyDesk, BeyondTrust — used for observation or basic mouse/keyboard control rather than deep backend access.

Active Directory / IdP

Basic access to reset passwords or unlock accounts, often via simplified, restricted admin portals.

7

Key Performance Indicators

70–80%

First-Contact Resolution Rate

Percentage of tickets resolved on the first interaction.

AHT

Average Handle Time

Average time actively working a ticket from open to close.

FRT

First Response Time

How quickly the technician acknowledges the user’s request.

Escalations

Escalation Rate

Percentage of tickets passed to L2. Too high signals a need for better L1 training or updated KB articles.

CSAT

Customer Satisfaction

Post-ticket surveys rating the user’s experience with the L1 technician.

8

Strategic Business Value

Level 1 is not just a “call center” — it is a strategic business asset.

Cost Efficiency

L1 technicians are the most cost-effective resource. Resolving 80% of issues at this tier prevents expensive L2/L3 engineers from burning billable hours on password resets.

Brand & Experience Ambassador

For most users, the L1 technician is the IT department. A positive, empathetic, fast interaction builds trust in the entire IT organization — a poor one damages it permanently.

Data Gathering & Continuous Improvement

L1 is the “canary in the coal mine.” Tracking L1 ticket trends reveals systemic issues (“50 password resets today”) and enables proactive fixes (“roll out self-service password reset”).

Level 1 · Basic Support (Frontline — Help Desk)