Turn “it’s not working”
into a clear next step.

What Tier 1 actually is, the core vocabulary (ticket, SLA, escalation, remote session), ticket anatomy, IP/DNS/DHCP/VPN fundamentals, isolate-the-variable, remote-session security, and knowing exactly when to escalate.

• Tier 1 vs. Tier 2/3, and the shape of the work
• The core vocabulary of the job
• Why process beats "just knowing the fix"
• Full walkthrough: "I can't log into my email"
• Intake and verification, done right
• Asking the right diagnostic questions
• Setting the right timeline expectation
• Closing a ticket the right way
• Basic networking concepts, explained simply
• The isolate-the-variable mindset
• What "the internet is down" actually means
• Full walkthrough: "Can't connect to VPN"
• Using a remote-access tool professionally and securely
• MFA basics and common reset scenarios
• Knowing exactly when to escalate
• Practice: categorizing 10 real tickets

Hands-on with Zendesk, Freshdesk, and ServiceNow: queue management, tagging, SLA tracking, and the specific click paths behind the concepts from Week 1.

• Recognizing the Environment Before Giving Instructions
• Translating Common Settings and Controls Across Operating Systems
• Safe Tier-1 Checks for Frozen Apps, Startup Trouble, and Storage Pressure
• Mixed-Device Desk Scenario: Choose the Right Path Without Guessing
• Turn ‘The Website Is Broken’ into a Reproducible Symptom
• Cache, Cookies, and the Cost of Clearing Too Much
• Isolate Extensions, Profiles, Browsers, Devices, and Site-Wide Failure
• Browser Case Walkthrough: An Intermittent Checkout Failure
• Read the Failure Before Retrying the Installer
• Permissions, Capacity, Compatibility, Prerequisites, and Security Controls
• Update Conflicts, Restarts, Locked Files, and Rollback Boundaries
• Installation Queue: Resolve, Defer, or Escalate
• Intake, Initial Evidence, and Prioritization
• Build and Test a Timeline of What Changed
• Handle the Complication, Act Within Scope, and Escalate
• Verify Recovery, Debrief the Case, and Transfer the Method

The high-volume categories that make up most of a real queue: account access, software installs, printer and peripheral connectivity, and application errors: with real runbooks.

• Separate the Password-Reset Request from Proof of Identity
• Perform the Reset Without Exposing or Choosing the Password
• Match the Reset Path to Account Risk and Request Context
• Resolve the Reset Without Bypassing Identity Controls
• Distinguish Lockout, Expiration, and Administrative Disablement
• Find the Source of Repeated Bad Credentials
• Restore Access and Prevent an Immediate Relock
• Resolve a Multi-Device Lockout Without Losing the Timeline
• Diagnose Missing File Access Without Granting It
• Separate Authentication from Authorization
• Trace SSO and MFA Failures at Practical Tier-1 Depth
• Resolve a Successful Login with a Missing Folder
• Intake and Preserve a Suspicious Message Safely
• Distinguish Exposure, Interaction, Credential Entry, and Execution
• Contain Within Policy and Escalate Through the Incident Path
• Verify the Handoff, Recovery, and Reporter Guidance

Working across the three employer types: a single-product SaaS desk, a multi-client MSP rotation, and overnight internal IT coverage: each with its own quirks and expectations.

• Use a Plain-Language DNS and DHCP Ticket Model
• Read Address and Name-Resolution Clues from the Symptom
• Run Safe Client-Side Checks and Interpret the Results
• Resolve a Case Where the Address Works but the Hostname Fails
• Establish the Physical and Logical Connection Path
• Compare Wi-Fi and Wired Evidence Without Premature Conclusions
• Identify Device, Local Network, Upstream, and Service Layers
• Separate a Dock Ethernet Failure from Wi-Fi Instability
• Recognize Credential, Network, Client, and Service-Side VPN Signatures
• Run a Fast Isolation Sequence Before Reinstalling the VPN Client
• Handle Certificates, Client Versions, Policy, and Split-Tunnel Clues
• Resolve a VPN Connection That Cannot Reach One Internal Application
• Convert ‘Slow’ into Time, Scope, Destination, and Behavior
• Compare Local, Wi-Fi, ISP, VPN, and Application Evidence
• Respond to Fluctuating Results and a Second Affected User
• Document Measurements, Verify Improvement, and Escalate Cleanly

Recognizing and responding to a real suspected compromise under time pressure, plus de-escalating a genuinely angry, non-technical user without ever sounding dismissive or scripted.

• Trace a No-Power Report from Outlet to Device
• Separate Heat, Airflow, Workload, and Shutdown Symptoms
• Assess Battery Health, Charging Paths, and Swelling Safely
• Resolve an Intermittent Power Case After a Hot Commute
• Establish Printer and Scanner Physical Readiness
• Verify Connection and Device Selection Before Changing Software
• Inspect Queue, Spooler, Driver, and Application Scope
• Resolve a Shared-Device Case Across Print and Scan Paths
• Determine Account, App, Device, and Service Scope
• Diagnose Sync Direction, Timing, and Stale Authentication
• Explain Enrollment and Policy Without Overstepping MDM Authority
• Resolve a Mobile Case with Working Mail and Stale Calendar
• Intake and Prioritize Monitor, Dock, Webcam, and Microphone Tickets
• Test Ports, Cables, Power, Permissions, and Application Selection
• Manage a Meeting-Critical Complication and Hardware Boundary
• Verify Each Outcome and Write Queue-Ready Notes

Writing closing notes and escalations a manager or a future agent can read cold, reading your own performance metrics, and using tagging and reporting to spot recurring patterns.

• Preserve What the Permanent Support Record Needs
• Replace Vague Notes with Observations, Actions, and Results
• Record Uncertainty, User Impact, and Pending Ownership
• Repair Four Flawed Tickets into Durable Records
• Search by Symptom, Error, Environment, and Product Language
• Check Scope, Version, Prerequisites, and Article Freshness
• Decide When an Undocumented Solution Deserves a New Article
• Turn a Solved Ticket into a Concise Draft Knowledge Article
• Separate Response and Resolution Commitments
• Read Clocks, Priorities, Pauses, and Ownership Correctly
• Communicate Before a Miss and Escalate Operational Risk
• Manage Competing Tickets, a Silent Dependency, and an Approaching Breach
• Interpret Backlog, Age, Reopenings, and Closure Patterns
• Investigate Suspiciously Fast Closures Without Assuming Misconduct
• Trace a Growing Unresolved Backlog to Operational Causes
• Produce a Manager-Ready Queue Assessment and Action Plan

Sustaining a realistic shift's ticket-and-chat volume at once, remote-work discipline, and working a queue end to end under real time pressure.

• Acknowledge Real Impact Without Promising Recovery
• Stabilize the Conversation and Gather Usable Facts
• Present Recovery Options, Boundaries, and Updates
• Carry a Loss-of-Work Case from First Reply to Documented Handoff
• Preserve the Technical Process While Raising Coordination Quality
• Communicate Tightly Under Visibility and Time Pressure
• Coordinate Assistants, Managers, Security, and Technical Owners Safely
• Resolve a Presentation Failure Minutes Before a Board Call
• Recognize Shared Timing, Symptoms, Services, and Dependencies
• Correlate Reports Without Declaring an Outage Prematurely
• Open the Incident Path and Keep Individual Reporters Informed
• Incident Case: Six Partial Reports Become One Service Event
• Triage a Mixed Queue Under a Visible Time Budget
• Work Account and Network Tickets as Evidence Changes
• Handle Hardware and Security Complications Without Losing Ownership
• Submit Final Dispositions, Notes, Escalations, and Debrief

Written exam, three graded mock tickets across chat and remote session, and a practical escalation-writing task: pass all three to certify.

• Exam Section A: Process, Operating Systems, and Software
• Exam Section B: Accounts, Access, and Security
• Exam Section C: Networking, Hardware, and Peripherals
• Exam Section D: Documentation, SLAs, Incidents, and Difficult Users
• Ticket 1 Chat: Source Transcript, Intake Response, and Grading Criteria
• Ticket 1 Chat: Diagnosis, Resolution, Notes, and Debrief
• Ticket 2 Remote Session: Preparation, Consent, and Evidence Plan
• Ticket 2 Remote Session: Controlled Actions, Verification, and Grading
• Mixed-Channel Case Intake and Prioritization
• Remote-Session Diagnosis with Changing Evidence
• Security Complication, Containment, and Escalation Decision
• Final Artifact Package and Rubric-Based Debrief
• Read the Raw Case and Identify the Escalation Trigger
• Build the Evidence, Attempted-Actions, and Impact Record
• Write and Grade the Practical Escalation Artifact
• Interpret Results, Plan Next Steps, and Close the Certification

Three timed shifts on Harborline Helpdesk, a fictional company with a real ticket queue. Items arrive the way they do in a real shift; every action is graded against the rules of the job.

Three more shifts including a downtime drill, a peer review of another student's work, and a tutor-marked final. Passing needs zero critical errors.