Helpdesk Agent Training Manual

Welcome to the Helpdesk Team

As a helpdesk agent, you are the face of IT for every employee in the organisation. Your job is not just to fix technical issues — it is to provide a great support experience that makes people feel heard, respected, and helped. This manual covers everything you need to know in your first 30 days.

Day 1: Tools & Access

You will be granted access to: the helpdesk system (agents view), the asset registry (read-write), the knowledge base (read-write), your email and calendar, Slack or Teams for team communication, and a shared documentation repository. Set up your helpdesk profile with your name, photo, and contact information. Agents with complete profiles receive higher satisfaction ratings.

The Ticket Lifecycle

1. Receipt: Tickets arrive via email, portal, phone, or walk-in. Every ticket gets a unique ID. Your first action: acknowledge receipt within the SLA response time, even if you don't have a solution yet.

2. Triage: Read the ticket, determine the category (hardware, software, network, access, facilities), priority level (P1-P4 based on impact), and assign it to yourself if you have the skills to handle it.

3. Investigation: Gather information — ask clarifying questions, check the knowledge base for known solutions, review the user's asset record for relevant history, and perform remote diagnostics if applicable.

4. Resolution: Apply the fix. If you cannot resolve within your skill level, escalate to Level 2 with a clear summary of what you have tried and what you suspect the issue might be.

5. Closure: Confirm with the user that the issue is resolved. Ask: "Is there anything else I can help you with?" before closing the ticket. Add resolution notes for future reference.

Communication Guidelines

• Always acknowledge a ticket within the SLA, even if you need more time to investigate.
• Use plain language — avoid jargon. Instead of "I have reset the TCP/IP stack," say "I have refreshed your network settings."
• Set expectations: "I am investigating this and will update you within 2 hours." Then actually update within 2 hours.
• Never blame the user or another team. Focus on the solution, not the cause.
• Every interaction is recorded. Write notes as if your manager and the user will read them — because they might.

Escalation Rules

Escalate P1 tickets immediately — do not attempt resolution beyond your skill level. Escalate P2 tickets if you have spent 2 hours without progress. Escalate P3 tickets after 4 hours without resolution. Always escalate with context: what you tried, what you found, and what you recommend.