<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/26de7cf0-a82d-4819-8611-e66a46f11de2/back.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/26de7cf0-a82d-4819-8611-e66a46f11de2/back.png" width="40px" /> Back
</aside>
<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/1862178a-bd6c-4cf7-ade5-cd40971ec5d6/fetch.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/1862178a-bd6c-4cf7-ade5-cd40971ec5d6/fetch.png" width="40px" /> Back to the app
</aside>
<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/78011eb5-84a7-4879-a35a-107365db12a5/web.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/78011eb5-84a7-4879-a35a-107365db12a5/web.png" width="40px" /> Fetch Website
</aside>
<aside> π‘ Purpose
This is a detailed description of a ticket management dashboard. It provides users with various statistics on their recovery efforts and staff performance. From here you can also see the open tickets, average resolution time, and Tickets pending action. With this you can find certain sections that needs immediate attention really easily!
</aside>
<aside> π Navigation
In the menu simply go to Ticket Management. Then from the top, click the Statistics tab.

</aside>
We are automatically calculating statistics on your recovery efforts and staff performance directly inside the ticket management dashboard. This is broken down into 5 different tabs: overall, team, resolution, shift, and cost.
Overall Statistics

Ticket Overview: a quick overview ofβ¦ β How many tickets are currently open. β The average age of all open tickets. β How many open tickets have 0 action taken on them. β Departments or staff currently in highest demand.
Team Statistics β’ Staff Engagement: track which staff are engaging most with the system, and what type of actions they prefer to take. β’ Department Insights: see which departments are being tagged most often, and how long it takes them to close their tickets. o Their speed is automatically compared to your overall resolution speed. If red, that means itβs slower than average. If green, that means itβs faster than average. β’ *You can filter by the preset date ranges.
Shift Statistics β Ticket volume: An annual view of your number of tickets in any given month or week. β Incident volume: breaking down what times of the day cases most often occur. β Shift volume: sorting ticket volume into the three common shifts (morning, afternoon, and night). β Shift resolution speed: tracking the average resolution speed per week by shift
β Average resolution time: you overall average plus a graph displaying your weekly averages. β Fastest/slowest: your fastest and slowest closes of the month, with a date stamp on each. β Touchpoints: what your average resolution looks like in terms of number of touchpoints and what they are. β Average time to respond: how long it takes to first act on a ticket, plus a graph of responses times per week.
<aside> βΉοΈ Source: the frequency of each type of ticket displayed in ascending order.
</aside>
Resolution Statistics
β’ Resolution Analytics: Monitor the average time it takes for staff to resolve tickets. You can view the fastest ticket closures and their corresponding closure times. Additionally, observe the average number of touchpoints required for resolution and the average response time to tickets.

β’ Tickets by source: Here, you'll find a bar graph illustrating the primary sources of incoming tickets.
