Navigating tickets in Spiceworks

Spiceworks landing page

Developing Practical Service Desk Skills Through Hands-On Ticket Management

As part of my building a Microsoft 365 identity management from scratch lab, I used Spiceworks to explore the full lifecycle of an IT support ticket.

This includes logging tickets to resolution and closure. By simulating real user issues, I was able to create tickets and practice categorising them accurately based on the nature and urgency of the problem.

TOOLS

• Spiceworks Help Desk — ticket creation, categorisation, prioritisation, and user communication
• Microsoft 365 Admin Centre — investigating and resolving user account access issues
• IT Service Management (ITSM) Practices — incident documentation, escalation, and ticket lifecycle management

Logging and Prioritising the Ticket

Here is an example of a ticket I was assigned.

Figure 1: The ticket view where a new ticket comes in

When a user reported they were unable to sign in to Microsoft services, I created a ticket in Spiceworks and assigned the correct category and priority level. Proper ticket classification helps ensure incidents are handled efficiently and routed to the appropriate support staff.

Figure 2: The ticket view where priority was changed and category set

Investigating the Issue in Microsoft 365

Basics of troubleshooting — Problem Identification.

After reviewing the ticket, I checked the user’s account in the Microsoft 365 Admin Centre. The investigation showed that the user’s sign-in access had been blocked. I resolved the issue by enabling the account again, allowing the user to regain access to Microsoft services.

Figure 3: Microsoft 365 “Unblock sign-in” screen

Updating the Ticket and Communicating with the User

Once the issue was resolved, I updated the ticket with my troubleshooting notes and informed the user that their account had been re-enabled. Clear documentation ensures that the resolution is recorded and provides helpful reference information if a similar issue occurs again

Figure 4: ticket update / response to the user

The issue was resolved by restoring the user’s account access, and the ticket was updated with both user communication and internal documentation to maintain clear service desk records.

Internal Note:

“Investigated in Microsoft 365 Admin Centre. User account found with sign-in blocked. Access restored by removing block. User advised to attempt login again and contact service desk if issue continues”

Using Spiceworks gave me a clear understanding of how incidents move through a support environment. I documented troubleshooting steps, added progress notes to keep users informed, and escalated issues when they required higher-level support. This process reinforced how important clear communication and transparency are for maintaining user trust during incident resolution.

Working within the ticket queue also helped me develop key service desk skills, including prioritising tasks, managing multiple requests simultaneously, and maintaining organised documentation. The structure of the platform reflects common IT service management practices, helping me become familiar with workflows that align with ITIL framework for incident management.

Overall, this project strengthened my understanding of how a service desk operates and highlighted the importance of structured processes, clear communication, and efficient ticket handling in delivering effective IT support.