Service Desk Performance Dashboard
Drop in a ticket export and get SLA compliance, backlog trend, resolution times, ticket ageing and busy hours in seconds, with plain-language findings on what to fix first.
- Runs in your browser
- Results in seconds
- ServiceNow, Jira, Freshservice
Export tickets as CSV from ServiceNow, Jira or Freshservice and the dashboard shows resolution SLA compliance by priority, median time to resolve, backlog trend, ticket ageing and problem candidates, without uploading anything. With no SLA column, each ticket is measured against its priority's target in business hours: on the Saudi Sunday–Thursday preset, a P2 with the default 8-hour target logged Thursday 14:00 is due Sunday 13:00.
Drop in a ticket export
CSV from ServiceNow, Jira Service Management, Freshservice, ManageEngine or any ITSM tool. Include the created and resolved dates, and priority, category and SLA if you have them.
Your file never leaves this browser and nothing is uploaded. Only its name and its top 12 categories with yearly volumes are kept here, for the shift-left calculator.
How to export your tickets
- ServiceNow: open the Incident list, add opened_at, resolved_at, priority, category and made_sla as columns, then right-click a column header → Export → CSV.
- Jira Service Management: search issues with JQL for your project and date range, show Created, Resolved, Priority and Request Type, then Export → CSV (current fields).
- Freshservice: Tickets → filter by date → Export, and tick Created Time, Resolved Time, Priority, Category and Resolution Status.
- Anything else: the first row must hold column names. Dates can be 2026-09-15 14:30, 15/09/2026 14:30 or 15/Sep/26 2:30 PM.
Your dashboard appears here: SLA compliance, backlog trend, resolution times by priority, top categories, ticket ageing, a busy-hours heatmap and plain-language findings.
Resolution targets per priority
What the data says
Where tickets get stuck
Add a reassignment count column (reassignment_count in ServiceNow) to your export to see hand-offs and reopens.
Where tickets change hands
Tickets per final assignment group, and how many arrived after a reassignment. High hand-off and reopen rates point to routing rules or missing knowledge.
| Assignment group | Tickets | Handed off | Avg hops | Reopened | Most handed-off categories |
|---|
Problem candidates: repeat incidents worth a problem record
Grouped by category, configuration item and similar short descriptions. Ranked by volume, priority and how fast they are rising. Candidates, not verdicts.
Breach early warning: open tickets due to breach soon
| Ticket | Pri | Group | Due in |
|---|
Performance
Category breakdown
The 15 largest categories. Slow, high-volume rows are where improvement pays back fastest.
| Category | Tickets | Share | Median resolve | SLA met |
|---|
Service desk review
Your organisation IT service desk
Three things to act on
Problem candidates
| Pattern | Service | Incidents | Trend |
|---|
Method.
Generated with ITSM Compass Lab · itsmcompass.com/tools/service-desk-dashboard/
Reading your service desk dashboard
- Look at SLA by priority, not just the total. A 96% overall figure can hide a P1 result of 70%, because P3 and P4 tickets outnumber P1s a hundred to one.
- Watch the gap between logged and resolved. A few weeks of logged running above resolved is an early warning, well before SLAs start to breach.
- Medians beat averages. One ticket left open for 90 days wrecks an average resolution time. The median shows the typical experience.
- Aged tickets are hidden risk. Anything open for more than 30 days is usually waiting on a supplier, a change or a decision. Review them weekly.
- Volume by category is your improvement backlog. The top three categories are where knowledge articles, self-service and problem management remove the most demand.
Method & ownership
SLA compliance comes from the SLA column in your export when there is one; otherwise each resolved ticket is compared with its priority's resolution target, measured in business hours on the chosen GCC calendar (weekends, Ramadan hours and public holidays excluded) or in calendar hours if you pick that clock. Problem candidates group similar incidents and are suggestions for review, not confirmed problems. Backlog and ticket ageing count every ticket still open at the latest date in the file. The page lists how dates and priorities were read so you can check them.
The formulas used here are standard, published methods. The implementation, interface, wording, findings logic and benchmark figures are original work by ITSM Compass. Results are estimates, not professional advice. See the terms of use.
© 2026 ITSM Compass. All rights reserved.
Questions
Is my ticket data uploaded anywhere?
No. The file is read by your browser and analysed on your own device. Nothing is sent to ITSM Compass or any other server. Close the tab and the file is gone; this browser keeps only its name and the top 12 categories with yearly volumes, for the shift-left calculator.
Which ITSM tools does the dashboard work with?
Any tool that exports tickets to CSV, including ServiceNow, Jira Service Management, Freshservice, ManageEngine ServiceDesk Plus, Zendesk and Ivanti. It looks for common column names such as opened_at, Created, Resolved, Priority, Category and made_sla.
How is SLA compliance calculated?
If your export includes an SLA column, such as made_sla in ServiceNow or an SLA breached flag, the dashboard uses it. If not, it compares each ticket's resolution time with the targets you set per priority, measured in business hours on the chosen GCC calendar, or in calendar hours if you pick that clock.
What does the backlog chart show?
The number of tickets still open at the end of each week or month: tickets logged before that point and not yet resolved. A rising line means demand is outpacing the team's capacity to resolve.
Which service desk metrics matter most?
Start with resolution SLA compliance by priority, median time to resolve, backlog trend and the age of open tickets. Then look at volume by category, which shows where self-service, knowledge articles or problem management will remove the most demand.
Want a second pair of eyes on the numbers?
An ITSM health check turns these charts into a prioritised improvement plan for your service desk.