◫Learn · Ticketing
Manage Priorities in Ticketing
Deep Understanding
Imagine your business is like a bustling city, filled with traffic, pedestrians, and a multitude of activities happening simultaneously. In such a vibrant environment, chaos can easily ensue without a well-defined traffic system. This is where the concept of managing priorities within the Ticketing module comes into play. Just as traffic lights and road signs help direct vehicles and pedestrians, prioritizing tickets ensures that the most urgent issues are addressed promptly while less critical ones are managed with due diligence.
The Ticketing module serves as a central hub for handling customer inquiries, technical issues, and other requests that require attention. Within this module, priorities act as the guiding principles that help teams determine which tickets need immediate action and which can wait a little longer. Understanding this concept is key to maintaining an efficient workflow and ensuring customer satisfaction.
A ticket marked as critical priority is akin to a fire alarm ringing in a crowded building. It requires immediate attention and action, as it could potentially impact not only one customer but many others. For example, if a core feature of your software is down, customers are facing disruptions that could lead to significant losses for your business.
Normal priority tickets are like routine maintenance checks on vehicles. They need attention to ensure everything runs smoothly, but they don’t pose an immediate threat to the functioning of the system. For instance, a request for a minor feature enhancement or a small bug fix would fall under this category.
Low priority tickets are comparable to a leisurely stroll through the park. They can wait and don’t require immediate action. These may include feature requests that are not urgent or feedback that can be addressed in future updates.
Urgent priority tickets serve as a siren on an ambulance rushing through traffic. They require swift attention but don’t necessarily have the same level of impact as critical tickets. An example might be a significant bug affecting a subset of users that needs to be resolved quickly to prevent escalation.
Where to Find It in Ilora
To navigate to the Priorities management feature within the Ticketing module of Ilora, follow these straightforward steps:
- Access your Ilora dashboard upon logging in.
- On the left-hand navigation panel, locate the Ticketing module and click on it.
- From the dropdown menu, select Manage Priorities to reach the priorities section.
The Feature in Action
Now let’s visualize how managing priorities looks in action. Below is a mockup of the interface you would see when you access the priorities section:
Current Ticket Priorities
In this example, you can see that the ticket #12345, labeled as a critical priority due to a system outage, is currently being addressed. This is the type of urgency that requires immediate focus from the support team. On the other hand, ticket #12346 is a low priority feature request, indicating that while it is valuable, it can be addressed later without causing disruption.
Next, let’s take a look at how you can add or update priorities for existing tickets through the following form interface:
Update Ticket Priority
In this form, you can update the priority of an existing ticket simply by entering the ticket ID and selecting the new priority level from the dropdown. Once you click on the Update Priority button, the changes will be saved in the system, ensuring that the ticket's urgency level is accurately reflected.
In addition to manually managing priorities, Ilora also helps automate this process to enhance efficiency and ensure a consistent approach across the board. Let me explain how this works:
Automation & Intelligence
Ilora’s automation capabilities allow the system to adjust ticket priorities based on predefined criteria, ensuring that no urgent issue is overlooked. Here’s how the automation chain works:
- When a ticket is created, it is automatically assessed based on keywords and customer impact.
- If the ticket describes a major system failure, it is instantly marked as Critical.
- For tickets mentioning time-sensitive requests, they are flagged as Urgent.
- Normal and low priority tickets are categorized based on historical patterns and customer feedback.
This automated approach means that support teams can focus their efforts on tackling the most pressing issues without manually sifting through every ticket. By managing priorities effectively, Ilora enables your business to maintain high levels of customer satisfaction and operational efficiency.