IT Service & Support Excellence
Run IT Like a Product
Deliver IT support people love, ticket triage trees, SLA thermometers, knowledge-base flywheels and shift-left strategies that cut ticket volume while raising satisfaction.
Who it is for: IT support leads, service desk managers, sysadmins moving into service roles, and MSP professionals.
Created by
ZLearning Faculty
Instructor
ZLearning Faculty
Not ready to buy? Try it first.
one-time · ≈ $3.13 per course day
- All 15 days, fully interactive
- Copy-paste prompt vaults in every day
- Auto-saved workbooks + download kits (PDF, Word)
- Knowledge quests with instant feedback
- Official certificate of completion
Secure checkout via Stripe · instant access · no subscription
Digital product, non-refundable once delivered, unless the course differs from this page. Refund policy
- Duration
- 15 days
- Learn
- 90 min/day
- Total time
- 23 hours
- Price
- $47 one-time
- Level
- All levels · Technical background helpful
- Access
- Lifetime + certificate
Start free. Upgrade when you are convinced.
Try the complete first day with any account, then decide. No card, no trial timer, no pressure.
Free Introduction
The complete Day 1 experience, the same lesson paying students get, in your portal.
- Full Day 1, every section, interactive
- Real prompt vault + hands-on mission
- Workbook + knowledge quest with instant feedback
- Progress saved in your own portal
- Signup only, no payment details
Instant portal access after signup
Full Course
Every day of the 15-day journey, plus your official certificate.
- All 15 days, fully interactive
- Copy-paste prompt vaults in every day
- Auto-saved workbooks + download kits (PDF, Word)
- Official certificate of completion
- Lifetime access, one-time payment
Secure Stripe checkout · one-time · lifetime access
What You Will Learn
Concrete, job-ready outcomes, hover (or tap) any point to see exactly where and how it is practiced inside the course.
- Route any ticket in seconds with the Ticket Triage Tree
Day 1, The Service Desk Baseline
The first spine framework: first response, resolution time, repeat-ticket rate and CSAT, computed from your own ticketing tool with formulas, healthy ranges, and a six-habit audit scored on evidence (not vibes) that finds the leak quietly burning user trust and engineer hours.
ChatGPTClaude - Run the SLA Thermometer: green/amber/red with early warnings, no heroics
Day 2, The Ticket Triage Tree
The second spine framework: impact x urgency, the known-error check and the P1-P4 priority matrix, a decision tree that makes routing consistent across the whole desk, drilled with ten real re-routed tickets until the matrix card runs without you in the room.
ChatGPTClaude - Write first responses that buy patience and cut ping-pong
Days 3-4, First Responses & the SLA Thermometer
The buying-patience first response, acknowledge, commit, bound, with a twelve-template library keyed to your Triage Tree, then the third spine framework: green/amber/red thresholds as clock percentages, pre-decided amber interventions, and the wall-clock shadow that keeps paused clocks honest.
ChatGPTClaude - Shift left: kill repeat tickets with the Knowledge-Base Flywheel
Days 5-7, Root Cause & the Knowledge-Base Flywheel
The bounded root-cause loop: the 3-strike rule, a 5-Why with a stop rule, and the three-line cause note with a live prevention number, then shift-left: the flywheel intake rule (article / update / feed on every close), user-words titles, and the fifteen-minute article method that cuts queue volume while you sleep.
ChatGPTClaude - De-escalate angry users and run clean handoffs every time
Days 8-9, De-escalation & Clean Handoffs
Acknowledge-align-act: the arc that reads the two real emotions under IT anger, the ten-line phrase library and the five banned fire-starters, the triple-filer forensics, then the four-line handoff note, the forty-minute rule, spoken acceptance and the custody rule so users never re-explain themselves again.
ClaudeChatGPT - Command the Major Incident Loop: declare, cadence, bridge, review
Days 10-11, Major Incidents & Change Discipline
Declare-bridge-cadence-review: the impact-based declaration test, three bridge roles with named fallbacks, the 30-minute three-line update clock, and the blameless review that ships two fixes, then change management without chaos: the two-minute risk triage, the rollback-first rule, freeze windows and the fast path that kills shadow change.
ChatGPTNotion AI - Prove IT value in business language: CSAT, FCR and the Service Scoreboard
Days 12-14, Automation, Metrics & Proactive Service
Self-service with codified approval rules, the five-part runbook and the boring-repeatable-reversible automation triage, then CSAT done right (two questions, 48 hours, response-rate pairing), the eight-number Service Scoreboard, and the proactive rhythm: synthetic user-path checks, early-warning thresholds and the weekly rounds sheet.
ChatGPTGoogle Sheets - Automate the boring: self-service, runbooks and proactive maintenance
Day 15, The Capstone: Your Service Improvement Plan
The Day 1 audit re-run with fresh evidence, direction with proof, vibes forbidden, then the artifact inventory with named owners, the 90-day three chosen by cost-to-trust, the fifteen-minutes-a-week operating rhythm, and the leadership briefing that makes the plan a commitment with witnesses.
Notion AIClaude
Inside the Course
The engine behind every single day, hover (or tap) any card to see exactly what is included.
15 Days × 90 Min
A complete guided journey, one focused session a day, fully interactive, zero fluff.
Copy-Paste Prompt Vault
A professional prompt vault in every day, copy, paste, get results. Prompts become your assets.
Fully Engaging Workbooks
Interactive in-app workbooks with auto-save, plus fillable PDF, Word and printable versions.
Real-World Missions
Every exercise uses your actual job context, not toy examples. Practice while you learn.
Progress That Shows Everything
A living dashboard tracks every section, quiz and workbook field, and flags what is missing.
Certificate of Completion
Finish the journey and graduate with an official ZLearning certificate for your resume and LinkedIn.
Day-by-Day: Key Highlights
Exactly what happens on each day of your 15-day journey, hover (or tap) any day to see the full detail. Each day blends interactive lessons, a prompt vault, hands-on missions on your real work, a workbook and a knowledge quest, days unlock in sequence.
Service Mindset: IT as a Product
Day 1 · 90 min · 8 sections
- Read the four numbers
- Do the service math
Hover or tap for details
Service Mindset: IT as a Product
- Read the four numbers, Meet first response time, resolution time, CSAT and repeat-ticket rate, the Service Scoreboard that decides whether a desk compounds or drifts, and that every later day of this course will move.
- Do the service math, Compute each number from reports your ticketing tool already prints, no dashboard buildout required, and learn the healthy ranges for a desk your size so you know what good looks like before you judge your own operation.
- Audit your own desk, Score your desk on the four numbers plus the four habits that move them, with evidence, not vibes. Find the one leak that quietly burns user trust and engineer hours every single week.
- Map the 15-day journey, Preview the full system, triage, SLAs, root cause, shift-left, de-escalation, major incidents, change control, automation, metrics, and see how today's baseline feeds your Day 15 Service Improvement Plan.
The Ticket Triage Tree
Day 2 · 90 min · 8 sections
- Learn the four questions
- Separate impact from urgency
Hover or tap for details
The Ticket Triage Tree
- Learn the four questions, Impact, urgency, category, known-error, the exact order of the Triage Tree and why each question must be answered before the next one is asked.
- Separate impact from urgency, The single most common triage failure is merging these two. Master the difference: how many are blocked (impact) versus how fast it is getting worse (urgency).
- Build your priority matrix, Turn the four questions into a written matrix, P1 to P4 with names your team and your users actually agree on, so triage survives vacations and bad weeks.
- Make it consistent, Run the tree on your own queue: re-prioritize ten real tickets with the matrix and see exactly where mood-based triage has been silently distorting your SLAs.
First Responses & Queue Rhythm
Day 3 · 90 min · 8 sections
- Buy patience on purpose
- Build the response library
Hover or tap for details
First Responses & Queue Rhythm
- Buy patience on purpose, Write first responses that do three jobs in ninety seconds, acknowledge, commit, set expectations, and learn why autoresponders never do.
- Build the response library, Create twelve reusable first-response templates keyed to priority and situation, so quality stops depending on which engineer touched the ticket first.
- Install the queue sweep, Replace cherry-picking with a timed sweep cadence that touches every ticket at least twice a day, and keeps P3s from dying of neglect.
- Measure the first hour, Track median first response by priority and by engineer, not averages, and learn what the Monday collapse in your data is really telling you.
The SLA Thermometer
Day 4 · 90 min · 8 sections
- Build the thermometer
- Set amber triggers
Hover or tap for details
The SLA Thermometer
- Build the thermometer, Convert each SLA into three bands, green, amber, red, with percentage-of-clock thresholds that work for any SLA length.
- Set amber triggers, Define the specific intervention that fires at amber, reassignment, escalation, or a user update, so amber always means action, never mood.
- See the real clock, Learn business-hours math, pause clocks and the vendor-hidden time that makes naive SLA reports lie to you.
- Report without heroics, Publish a weekly thermometer board where the story is amber interventions, not red heroics, and where green is boring on purpose.
Root Cause Without the Rabbit Hole
Day 5 · 90 min · 8 sections
- Spot the class, not the ticket
- Run the bounded loop
Hover or tap for details
Root Cause Without the Rabbit Hole
- Spot the class, not the ticket, Use the 3-strike rule, three similar tickets inside a week is a class, and classes deserve one investigation, not three patches.
- Run the bounded loop, Learn the 5-Why discipline with a stop rule, so root cause work takes one hour, not one afternoon of rabbit holes.
- Write the cause note, Produce a three-line cause note, symptom, cause, systemic fix, that survives handoffs and feeds the KB Flywheel on Day 6.
- Prove the prevention, Count the prevented tickets: the number that turns root-cause work from a hobby into the desk's highest-leverage hour.
Shift-Left & The Knowledge-Base Flywheel
Day 6 · 90 min · 8 sections
- Understand shift-left
- Build the Flywheel
Hover or tap for details
Shift-Left & The Knowledge-Base Flywheel
- Understand shift-left, Learn the four shift-left levels, self-service, deflection, assisted-first-contact, prevention, and why level one is where the leverage lives.
- Build the Flywheel, Install the intake rule, every closed ticket answers one question: article, update, or feed, so the KB grows from real demand, not guesswork.
- Fix findability first, Learn why users do not read your KB (they cannot find it, or it does not match their search words) and the two fixes that move the needle.
- Measure deflection honestly, Track article-assisted resolutions and the deflection rate per top-10 article, and refuse the vanity metric that counts views.
Writing KB Articles That Work
Day 7 · 90 min · 8 sections
- Master the working template
- Interview the fix out of engineers
Hover or tap for details
Writing KB Articles That Work
- Master the working template, Learn the five-part article, title, symptom, steps, variants, escape hatch, and why each part exists for a scanning, frustrated reader.
- Interview the fix out of engineers, Use the three questions that turn a shrugging expert into a written procedure, in five minutes, without a writing project.
- Run the AI drafting loop, Draft with AI, verify against the real fix, cut the corporate padding, the loop that makes fifteen-minute articles real.
- Edit for the scanner, Apply the scanner's edit pass: front-load, number the clicks, kill the hedges, so the article works at a glance.
Difficult Users & De-escalation
Day 8 · 90 min · 8 sections
- Read what anger actually is
- Run the arc
Hover or tap for details
Difficult Users & De-escalation
- Read what anger actually is, Learn the two real emotions under most IT rage, fear of looking incompetent and loss of control, and why fixes do not land without handling them.
- Run the arc, Master acknowledge-align-act: name the impact, restate the problem in their words, commit to one next step with a time.
- Write de-escalating lines, Build the phrase library, the ten sentences that lower temperature, and the five that quietly start fires.
- Close the loop on repeat cases, Handle the triple-filer differently: their history is your data, and their third ticket is a system flaw wearing a complaint.
Escalations & Clean Handoffs
Day 9 · 90 min · 8 sections
- Decide when to escalate
- Write the 4-line handoff
Hover or tap for details
Escalations & Clean Handoffs
- Decide when to escalate, Learn the four legitimate escalation triggers, authority, specialization, workload, risk, and spot the fake trigger (nobody wants it).
- Write the 4-line handoff, Master the note format that carries context, attempts, constraints and the next step, so the receiver starts at minute one, not zero.
- Keep custody through the move, Run the custody rule: the sender stays the user's contact until the receiver has spoken, no orphaned tickets, ever.
- Close the loop back down, Learn the return path: what the escalated fix owes the first line, so the KB grows and next week's twin never escalates.
The Major Incident Loop
Day 10 · 90 min · 8 sections
- Declare early, honestly
- Bridge without bloat
Hover or tap for details
The Major Incident Loop
- Declare early, honestly, Learn the declaration test, impact over cause, and why a six-minute early declaration buys hours of trust.
- Bridge without bloat, Master the incident bridge: three roles only (incident lead, comms lead, work lead) and the discipline of keeping everyone else working.
- Run the cadence, Set the update clock, every 30 minutes, three lines, even with no news, and learn why silence is the only real incident crime.
- Review without blame, Run the blameless post-incident review: timeline, contributing causes, and the two fixes that make the next incident shorter.
Change Management Without Chaos
Day 11 · 90 min · 8 sections
- Triage risk in two minutes
- Run the change calendar
Hover or tap for details
Change Management Without Chaos
- Triage risk in two minutes, Learn the three questions, blast radius, reversibility, timing, that sort changes into standard, normal and risky without a committee.
- Run the change calendar, Install a visible change window system with freeze rules, so 'who changed WHAT on Tuesday?' never happens again.
- Make rollback the plan, Master the rollback-first rule: no change is approved until its undo is written, timed and tested, the discipline that makes risk boring.
- Kill the shadow change, Understand why engineers bypass change processes, and design a lightweight path they will actually choose over sneaking.
Self-Service & Automation
Day 12 · 90 min · 8 sections
- Build real self-service
- Write the working runbook
Hover or tap for details
Self-Service & Automation
- Build real self-service, Learn the two request types that belong in self-service forms, access with pre-approval rules, and status with live answers, and what never belongs there.
- Write the working runbook, Master the runbook format: trigger, preconditions, exact steps, verification, rollback, so any engineer produces the same result at 2 AM.
- Automate the boring three, Apply the automation triage, boring, repeatable, reversible, and pick the first three manual checks that deserve a script or a schedule.
- Keep humans on judgment, Learn the two automation red lines, no automated judgment about people, no unobservable automation, and the failure stories behind them.
Metrics That Matter: CSAT & the Service Scoreboard
Day 13 · 90 min · 8 sections
- Fix the CSAT survey
- Mine the comments
Hover or tap for details
Metrics That Matter: CSAT & the Service Scoreboard
- Fix the CSAT survey, Learn the two-question survey, the 48-hour window, and the response-rate rule that makes a 4.6 mean something.
- Mine the comments, Turn free-text CSAT comments into themes with owners, the cheapest voice-of-customer program any desk can run.
- Build the Service Scoreboard, Assemble the eight numbers that matter, the Day 1 four plus volume, deflection, prevention and backlog age, with one line of business context each.
- Tell the value story, Master the monthly one-pager: three wins, three risks, one ask, written so a CFO repeats it in a meeting you are not in.
Proactive Service: Maintenance & the NOC
Day 14 · 90 min · 8 sections
- Install the maintenance rhythm
- Monitor what users feel
Hover or tap for details
Proactive Service: Maintenance & the NOC
- Install the maintenance rhythm, Learn the cadence tiers, daily health, weekly rounds, monthly deep checks, and what belongs in each without drowning the team.
- Monitor what users feel, Shift monitoring from 'server is up' to 'user can work', the synthetic checks and user-path probes that catch green-dashboard outages.
- Read the early warnings, Use capacity and trend data, disk growth, license burn, device age, to schedule work before it schedules you.
- Close the proactive loop, Feed findings into the root-cause ledger and the change calendar, proactive work only counts when it ships as a change.
Capstone: Your Service Improvement Plan
Day 15 · 90 min · 8 sections
- Restate the baseline
- Inventory the artifacts
Hover or tap for details
Capstone: Your Service Improvement Plan
- Restate the baseline, Re-run the Day 1 audit with evidence and see the movement, the before-and-after that proves the fifteen days were not a mood.
- Inventory the artifacts, Catalog everything you built, triage tree, templates, thermometer, articles, runbooks, card, calendar, sheet, into one owned list.
- Choose the 90-day three, Pick the three improvements with the best cost-to-trust ratio and write each as a change with an owner and a measure.
- Install the operating rhythm, Assemble the weekly, monthly and quarterly cadence that keeps every framework alive, the plan is the rhythm, not the document.
Frequently Asked Questions
Tools you will master
ZLearning Faculty
ZLearning faculty, every journey is built on real corporate workflows: reports, pipelines, decks and decisions, not theory.
Verified certificate · signed by the Director
Start your 15-day transformation today
Join the learners turning AI into daily, measurable output. One payment, every prompt, workbook, download kit and your certificate included.
Secure checkout via Stripe · lifetime access · Digital product, non-refundable once delivered unless the course differs from this page · Refund policy