Priority Reports for Support Teams
One of the greatest frustrations of customers and help desk associates alike is when a help case must be escalated outside of the help desk. These are the requests that fall into a black hole. The customer calls up regularly to inquire about the status. The help desk contacts the support technician assigned to the case for a status. The customer is frustrated because the delay is affecting her work. The technician is frustrated because there are so many support, project, and operational tasks assigned to him. The help desk is caught in between these two and is usually powerless to help either.
This is one of the most important areas for help desk leaders to address. Implementing processes and tools that prioritize support tasks will benefit the support technicians, the help desk analysts, and even the customers. This month's tool is a prioritization matrix that the help desk publishes and distributes to the support teams and internally to the service desk.
The support priority matrix works on the assumptions that: 1) everyone is busy; 2) there's too much work to get done; and 3) customers are frustrated by not knowing when their help cases will be resolved. By publishing a matrix to the level 2 or level 3 support teams that sets the priority for each case and tracks progress with a service level objective or agreement, everyone can see how there doing in providing support services to your customers.
This matrix should be published and distributed daily to support:
- elimination of zombie cases (requests that have been sitting so long that even the customer has forgotten)
- reduction of average resolution time
- customer inquiries about their help case status
- relief for support staff, who can work on requests in order rather than being overwhelmed with all of them
- proper staff support resource assignment by managers
- objective communication of service level performance
- healthy competition among teams to minimize queue sizes or red lights
Informational Columns
- Case number
- Case type/category
- Case description
- Customer name
- Status
- Last modification date
- Date created
- Age of request (today's date minus the date created)
- Service level expectations (based on type of request)
- Priority (automatically calculated using the age of request, the SLA, and any other factors that are important)
- Red, Yellow, or Green light (where red has exceeded SLA, yellow is approaching SLA, and green has comfortable margin)
The requests listed in these columns should be grouped by the support team to which each case is assigned. The support team may be displayed as a header for each section of the report.
To enhance this report, include a bar chart that shows each support team's queue with separate sub-bars for red, yellow, and green cases. This will allow a quick comparison of workload and service level performance by team and will motivate teams to look good on the report.
Help cases come in fast, and priorities may change rapidly, so it is essential that you generate this report daily. As with any help desk report, automate it right away. If you can't automate it, you will probably stop reporting on it within three weeks.
Supplement your report with a daily review meeting. This will allow support team managers to communicate any delays or issues with high priority cases. Peer exposure will also motivate them to keep up with their cases.
Manage priorities well, and you'll please everyone who interacts with your help desk.
Labels: Tools
