1.3User support & ticket management (Tier 1)
The essentials in 30 seconds
- Tier 1 is the first line: it qualifies quickly, resolves simple cases and escalates the rest to Tier 2/3.
- A ticket always follows the same cycle: receipt, qualification and priority, diagnosis, resolution (or escalation), closure with follow-up.
- Priority = impact × urgency, not "first come, first served".
Rolling mini-case — Sofiane prioritises a busy support morning
At 9 a.m., three requests land on the support desk of the SME distributor in Algiers. Sofiane applies the cycle: he receives and qualifies each request in the ITSM tool (GLPI), then assigns a priority according to impact and urgency. First request: a manager blocked because she forgot her password — one person blocked, so urgent. Second: the accounting share is inaccessible for the whole team — high impact, maximum priority. Third: "can you install a piece of software for me someday?" — schedulable. Sofiane handles A and B right away, schedules C for later, and only closes a ticket after confirmation from the user. He keeps in mind: priority = impact × urgency, not order of arrival.
Standalone case for this section: it returns in the course, the diagram, the script and the 48h challenge of section 1.3.
1. Tier 1 support, the first line
Tier 1 support is the user's first contact: resets, access, small software issues, usage questions. Its role is not to solve everything but to qualify quickly and resolve simple cases; anything beyond that is escalated to Tier 2/3. Sofiane saves time by qualifying before acting, rather than struggling on his own.
2. The life cycle of a ticket
A ticket always follows the same steps: receipt, qualification (what is it about, what impact?), assignment of a priority, diagnosis, resolution (or escalation), then closure with follow-up. The tool that tracks all this is the ITSM (for example GLPI). Without traceability, the same problem is handled ten times over — the trace also serves the team and the knowledge base.
3. Priority = impact × urgency
Not all requests are equal. Priority is derived from the impact (how many people, what criticality) and the urgency (can it wait?). An accounting share inaccessible to a team comes before a software request "for later". Sofiane never closes without checking with the user that it is indeed resolved.
🔎 Concrete example — 🔎 Concrete example — Prioritising three tickets that arrived at the same time
Three requests land on Sofiane's desk at 9 a.m.:
A · "I forgot my password" (1 person, blocked) → priority
B · "The accounting share is inaccessible" (team) → priority++
C · "Can you install software for me someday?" → scheduledReading: B touches a whole team (high impact) → maximum priority; A blocks one person (urgent); C can wait.
Lesson: priority = impact × urgency, not "first come, first served".
Section vocabulary
- Tier 1 support
- First line of assistance: qualifies, resolves simple cases, escalates the rest.
Simple example: Sofiane resets a password and escalates what is beyond him.
What it is not: a tier that would handle only complex cases.
Reflex: first line → qualify and resolve the simple.
- Ticket
- A record of a request or incident, tracked through to its closure.
Simple example: Sofiane opens a ticket for each request received from the department.
What it is not: a forgotten request, with no trace or follow-up.
Reflex: every request → a traced ticket.
- ITSM
- IT service management tool that traces and drives tickets (e.g. GLPI).
Simple example: Sofiane tracks the progress of his tickets in GLPI.
What it is not: a paper notebook not shared with the team.
Reflex: trace tickets → ITSM.
- Escalation
- Passing a ticket to a higher tier (Tier 2/3) when it goes beyond Tier 1.
Simple example: Sofiane escalates to Tier 2 a network incident that touches a server.
What it is not: struggling alone on a case outside your scope.
Reflex: out of scope → escalate, qualified.
- Priority
- Order of handling derived from impact and urgency.
Simple example: Sofiane puts the accounting share at the head of his queue.
What it is not: handling requests in order of arrival.
Reflex: priority = impact × urgency.
In practice — In practice — Qualifying a ticket
- For a given request, rephrase the problem in one clear sentence.
- Estimate the impact (number of people, criticality) and the urgency.
- Assign a priority and decide: resolve at Tier 1 or escalate.
- On closure, note the solution and check with the user that it is fixed.
Step-by-step script — qualify and prioritise like Sofiane (5 min)
1) Rephrase the request in one sentence: what is it really about? 2) Estimate the impact (how many people, what criticality) and the urgency (can it wait?). 3) Assign a priority = impact × urgency. 4) Decide: resolve at Tier 1 or escalate to Tier 2/3 with the useful details. 5) On closure, note the solution and have the user confirm.
A well-qualified escalation saves time; struggling alone blocks the user for longer.
Copy-paste template — my qualification sheet
Request rephrased: ___
Impact (no. of people / criticality): ___
Urgency (can it wait?): ___
Priority = impact × urgency: ___
Decision: resolve at Tier 1 / escalate to Tier 2
Solution applied: ___
User confirmation before closure: yes / noSimple case at Tier 1
Sofiane resets a password and closes after confirmation from the user.
High impact
Sofiane puts the accounting share inaccessible to a whole team at the head of the queue.
Escalation
Sofiane escalates to Tier 2 an incident that touches a server, with all the information gathered.
Schedulable request
Sofiane schedules for later the installation of software that can wait.
✓ Best practices
- Qualify before acting: what is it really about?
- Prioritise by impact × urgency.
- Close only after confirmation from the user.
✗ Common pitfalls
- Handling "first come, first served".
- Escalating without having qualified.
- Closing without checking that it is resolved.
Key takeaways
- Tier 1 qualifies, resolves simple cases, escalates the rest.
- A ticket always follows: receipt → qualification → diagnosis → resolution → closure.
- Priority = impact × urgency.
- ITSM (GLPI…) traces everything and avoids handling the same cases again.
48h challenge — apply it tomorrow
Take three recent requests and fill in Sofiane's qualification sheet: impact, urgency, priority = impact × urgency, decision (Tier 1 or escalation). In one sentence, write why order of arrival is not a good criterion.
- I can qualify a ticket and assign it a priority.
- I know when to resolve at Tier 1 and when to escalate.
- I close only after confirmation from the user.
Frequently asked questions
When should you escalate rather than insist?
As soon as a ticket goes beyond your scope or a reasonable time, or touches sensitive infrastructure. A well-qualified escalation saves time; struggling alone blocks the user for longer.
Why trace tickets if you know the solution?
Because the trace serves the team: statistics, recurring problems, knowledge base, continuity if you are away. An untraced incident recurs and is re-diagnosed from scratch.
How is the priority of a support ticket determined?