Available reports
What each Elion ITSM report measures, what each column counts and how to read it to make decisions about your desks.
On this page
This page explains what each report counts and how to read its columns. To choose the range, the desk and the grouping, see View a report.
Rules that apply to all of them:
They only count tickets in the service desks you can see: incidents, requests, problems and changes. Private desks only count if you're a member.
The range is counted in full days, in your company's time zone.
Agent is the ticket's current assignee and Group is its current resolver group. If a ticket changed hands, it counts for whoever has it now.
Volume
How much work comes in and how much goes out in the period.
Column | What it counts |
|---|---|
Opened | Tickets created within the range. |
Resolved | Tickets resolved within the range, even if they were created earlier. |
How to read it: if Opened exceeds Resolved period after period, the queue is growing. Group by Week to see the trend, or by Category or Service to find where most of the demand comes from. By default it's grouped by Type.
SLA compliance
How the deadlines of tickets created in the period were met. Each ticket has two clocks, and the report shows one row for each in the Metric column: First response and Resolution.
Column | What it counts |
|---|---|
Met | Clocks that stopped within the target. |
Breached | Clocks that passed their target, whether the ticket is still open or not. |
Running | Clocks still running or paused that haven't breached yet. |
Compliance | Percentage of Met over Met plus Breached. |
How to read it: Compliance only considers clocks that have already finished or breached. Those Running can still be met or breached, so for a recent period the percentage may change over the following days. Cancelled clocks aren't counted. By default it's grouped by Desk; group by Group or Agent to see where breaches concentrate.
Each clock's targets and pauses follow the desk's SLA rules and calendars. See Read a ticket's SLA.
Response times
How long it takes to handle the tickets created in the period.
Column | What it counts |
|---|---|
Tickets | Tickets created within the range. |
First response (average) and (median) | Time from when the ticket was created to the first response. |
Resolution (average) and (median) | Time from when the ticket was created to when it was resolved. |
How to read it:
Times are elapsed: they count all 24 hours of the day, including nights and weekends. That's why they can be longer than SLA targets, which follow the desk's business calendar. To know whether targets were met, use SLA compliance.
The average moves a lot with a few very slow tickets. The median is the time of the ticket in the middle: half were handled faster and the other half slower. If the average is much higher than the median, a few tickets took too long.
Tickets that don't yet have a first response or aren't resolved don't enter those averages.
The chart shows the number of Tickets; the times are in the Data table.
By default it's grouped by Type. This report has no Total row.
By agent and By group
The performance of each assignee (By agent) or of each resolver group (By group). There's always one row per agent or per group, sorted from most to fewest resolved tickets. Tickets with no assignee appear under Unassigned and those with no group, under No group.
Column | What it counts |
|---|---|
Opened in the period | Their tickets created within the range. |
Resolved | Their tickets resolved within the range. |
Resolution (average) | Average resolution time of those resolved tickets, in elapsed time. |
Reopened | Of those resolved in the range, how many were ever reopened. |
Average CSAT | Average score of the surveys answered within the range, from 1 to 5. |
How to read it: compare Resolved with Reopened: many reopens can point to rushed resolutions. An Average CSAT with a dash – means there were no answered surveys. In the Total row, the counts are added up; averages appear with a dash –.
Reopens
How many tickets resolved in the period had to be reopened.
Column | What it counts |
|---|---|
Resolved | Tickets resolved within the range. |
Reopened | Of those, how many were reopened at least once. |
Reopens | Total number of times they were reopened. A ticket reopened twice adds 2. |
Reopen rate | Percentage of Reopened over Resolved. |
How to read it: a high rate means tickets are considered resolved too early or the solution doesn't last. By default it's grouped by Group; group by Category or Service to see which topics come back. If you group by Day, Week or Month, each ticket counts on the date it was resolved.
A ticket is reopened when the requester reopens it from the portal or when an agent opens it again. See Resolve and close a ticket.
Satisfaction (CSAT)
What requesters answered in the satisfaction survey they get when their ticket is resolved. The survey has five faces, equivalent to scores from 1 to 5.
Column | What it counts |
|---|---|
Surveys | Surveys sent within the range. |
Answered | How many of them were answered. |
Response rate | Percentage of Answered over Surveys. |
Average score | Average of the scores, from 1 to 5. |
Satisfied (4-5) | Percentage of answers with a score of 4 or 5. |
How to read it: with few answers, the Average score changes a lot from one period to another; check the Response rate first. Satisfied (4-5) is the usual CSAT indicator. By default it's grouped by Agent.
There's only data for desks that request the survey. The desk lead turns it on in Settings, General tab, with Send a satisfaction survey (CSAT) on resolve. See Reopen, cancel and rate a request for what the requester sees.
Knowledge deflection
How many portal questions were resolved with a help article, without anyone having to open a ticket.
Column | What it counts |
|---|---|
Resolved with an article | Times a requester said an article solved their problem. |
Portal tickets | Tickets created from the portal within the range. |
Deflection | Percentage of Resolved with an article over the sum of the two previous columns. |
A question counts as resolved with an article when the requester:
When reporting a problem in the portal, presses Yes, that solved it on a suggested article. See Report a problem.
Reaches an article from a search in the help and presses Yes, it helped. See Search help.
How to read it: a rising Deflection means the knowledge base is saving the desks work. This report is grouped only by Day, Week or Month (by default, Week).
Questions resolved with an article don't belong to a desk, because the portal searches all of the company's help. If you choose a desk in Desk, only the Portal tickets change.
Most used articles
The knowledge articles that helped most in the period: those used in tickets and those that avoided a ticket. It shows up to 50 articles, from most to least used, and doesn't include drafts.
Column | What it counts |
|---|---|
Article | Article number. |
Title and Space | The article title and the knowledge space where it is. |
Uses in tickets | Times it was linked to a ticket within the range: used to resolve it, suggested and accepted, or created from the ticket. |
Tickets avoided | Times it resolved a portal question without a ticket within the range. |
Views (total) | Article views since it was created, not just in the range. |
Helpful | Percentage of positive votes over the article's total helpfulness votes, since it was created. Votes come from the portal question Was this article helpful?; in Knowledge you see them in Helpful?. |
How to read it: an article with many uses and a low Helpful percentage is a good candidate for improvement. You'll only see articles from the knowledge spaces you can see. See Knowledge.
If you choose a desk in Desk, only the Uses in tickets change. Tickets avoided counts the questions from the whole portal.