Module 2 · The tools and the writing Lesson 4 of 15
Ticketing systems: states, owners and handoffs
Every ticket has a state, an owner and a history. A handoff that repeats the history rather than pointing at it is what makes a customer explain their problem for the fourth time.
Worked example
A handoff note with the reproduction steps, what you already ruled out and what you need next lets the next person act without contacting the customer. That habit is the difference between a queue that moves and one that loops.
Your practice task
Write a handoff note for a problem you could not solve, naming what you already checked and why.
Do this before moving on. Reading a solution teaches the shape of it; typing it teaches you.
Key takeaway
Every ticket has a state, an owner and a history. A handoff that repeats the history rather than pointing at it is what makes a customer explain their problem for the fourth time.
Keep your place in this course
A free account saves which lessons you have finished and unlocks the certificate. The lesson itself stays free to read.
Create free account or sign inCourse complete
You finished every lesson.
Your certificate is ready, and the projects you built are the proof to attach to an application.
Almost there
15 lessons left of 15
Finish every lesson to unlock the certificate. Each one ends in a practice task — do them and the final project brief writes itself.