← Technician · Master
Lesson 2 of 48 min

What a great ticket looks like

Replication steps, evidence, resolution, time entries. Future you reads this ticket.

Person triaging tickets on a laptop with sticky notes
Photo by Yan Krukau on Pexels

A great ticket reads like a short forensic report: what the user reported, what you observed, what you ruled out, what fixed it, why.

Time entries matter — clients are billed in 15-minute increments and dispatchers schedule based on accurate estimates.

Diagram · Priority = Impact × Urgency
IMPACT →URGENCY →P2 HighFix same dayP1 CriticalDrop everythingP4 LowWhen possibleP3 StandardScheduled

Close with a customer-friendly summary the user can understand.

Key takeaways

Next: Just-enough PowerShell →