Efficiently managing support requests is the backbone of any successful service desk. In our recent discussion, we delved into how Jira Service Management (JSM) facilitates this through a structured ticket lifecycle, starting from the moment a user reaches out for help.
1. Entry Points: Diverse Channels for Raising Tickets
A ticket's journey begins through various "channels". While users can submit requests via email, chat, or widgets, the Jira Service Management portal remains the most effective method. The portal is the most recommended and well-defined way for customers to select specific help categories, such as password resets or reporting broken equipment, ensuring the request is well-defined from the start.
Alternatively, channels like email are popular because they use a standard company domain (e.g., support@company.com). However, email has the disadvantage of being difficult to categorize because users often omit necessary details. Forms and widgets, such as a "Contact Us" form on a company website, offer better redirection capabilities to specific users or queues.
2. Organization: Standard Workflows and Queues
Once a request enters the system, it follows a workflow defined by the Jira administrator. For organizations starting their journey, JSM offers built-in templates based on Information Technology Service Management (ITSM) standards, providing a functional foundation for incident management or service requests. These templates provide a functional starting point that users can later modify or customize to fit specific organizational requirements.
To handle the high volume of incoming tickets, agents use "Queues." These function as "buckets" or powerful filters that allow service management teams to categorize and organize tickets based on specific criteria. Examples of queue views include "all open tickets," "incidents," or "service requests". Queues can also be personalized to show only tickets assigned to a specific agent, ensuring that the team can manage large volumes of requests effectively.
3. Prioritization: Service Level Agreements (SLAs)
To maintain high service standards, JSM implements Service Level Agreements (SLAs), which function as internal countdown clocks that track the time from when a ticket is raised until it is resolved. These agreements serve as a "guiding force" for support teams to ensure issues are resolved quickly.
SLAs are crucial for prioritizing tasks within limited timeframes. Priority is often based on the severity of the issue; for instance, a high-priority ticket might have a 12-hour resolution agreement, whereas a low-priority ticket might allow for two days. By monitoring these countdowns, agents use the impending "breach" deadlines to decide which tickets require immediate attention.
