Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Web Help Desk (WHD) > Web Help Desk (WHD) Training > Free SolarWinds Training Videos - WHD > Configuring Ticket Priority Levels - Video

Configuring Ticket Priority Levels - Video

Updated May 25th, 2016


In this video (3:51), we're going to talk about Ticket Priorities, where to configure them and how to configure email alerts based on those priorities. You can find them in Setup, under Tickets, Priority Types and Alerts.



  • Web Help Desk

Related Resources

Video Transcription

There are four Priority Types that are defined by default in Web Help Desk ® , all with different Due Times.

They are:

  • Urgent
  • High
  • Medium
  • And Low


You can add your own priority if you like or change the due time setting in accordance with to your organization’s Service Level Agreement. In this example you can see that I've created a Critical priority type.


Let’s create a new Priority to give you an idea of what it looks like. I'll click New to get started.


In the Name Field, I’ll name this priority Very Low. I want this type to be the lowest ticket priority level, so I’ll accept the default Display Order of six. If I was creating a critical priority, I would change the display order to one so it appears first in the list.


I'd like to use this new priority for software upgrade requests. This task requires different individuals and teams to complete different tasks. I'll need approval from the IT director to order the software, approval from the Finance team to purchase the software, and approval from the IT Software team to test the software for bugs before it's installed on the client's server or workstation. This will take some time, so I’ll set the Due Time to 2 weeks. The Due Time is the amount of time tickets with this priority will be due. You can override the Due Time for an individual ticket in the Ticket Detail page.


When you're done, click Save.


Notice that after clicking Save, we can now configure alerts for this priority. You can send reminders to your techs and clients when a ticket is not processed in a certain amount of time. This is where alerts come in handy. Alerts are a great way to keep everyone involved on track so the ticket Service Level Agreements are met.


As you can see, Web Help Desk includes three Alert levels, with level 3 as the highest severity.


The Not Completed condition is considered more important than Not Updated, which is more important than Not Assigned. When all alert conditions are met, Web Help Desk uses the highest severity condition and triggers an alert matching that severity.


I'm sure that one alert level is sufficient for many organizations. However, the additional levels are designed to accommodate organizations with very complex Service Level Agreements. This allows you to alert more and more people if the ticket is not assigned, updated, or completed within a certain amount of time.


Some Service Level Agreements require a response from your team within a certain amount of time. If you also have a requirement that the issue must be resolved within, say 48 hours, you can set up a level 2 that addressees the "completed" parameter. If your requirements are not that complex, and you just want to be alerted if a ticket sits too long, one level is usually enough.


Alerts are linked to the status of a ticket, so to complete the alerts setup we need to enable alerts on a given status type. To set up this configuration, we’ll go up here to Status Types in the menu. We only want alerts enabled for tickets in the “Open Status”, so click “Open," ensure “Alerts Enabled” is selected, and click Save.

To demonstrate what this would look like in action, let's go back to Priority Types & Alerts and select Urgent. On Alert Level 3, ensure Not Completed is set to 0 Hours After Creation. Set Alert Repeat Interval to 1 Business Day and Save my changes.


Now, navigate over to Tickets across the top and create a new ticket with an URGENT priority. Set the Due Date to today at 1:00AM so we can immediately see the alert in action.


When you save the ticket, you'll have an alert display across the top.



Last modified