Case Analytics

From AgileApps Support Wiki
Revision as of 20:22, 30 January 2014 by imported>Aeric (→‎Case Analytics Object)

Case Analytics is a special feature of the ServiceDesk application. It consists of the Case Analytics dashboard, and the Case Analytics object. This article explains what you can do with them, and how they work.

Case Analytics Dashboard

The image below shows the initial dashboard displayed in the ServiceDesk application. In the table, aggregate number of cases is shown for each agent, each day, for each of the priority levels.

To modify the display:

  1. Click [Add a Filter]
  2. Choose the agent, priority, and date range to display.
    The graph changes to show the selected data.
HomePage.png

Case Analytics Object

The Case Analytics dashboard displays data recorded in the Case Analytic object--a specialized object that records statistical data in the ServiceDesk application. In that object, one record is created for each agent, each day, for all cases at a given priority. (That strategy keeps data storage to a minimum, and speeds up reporting.)

The Case Analytics object can also be used for reporting.

Tips
  • Customers who create cases directly are known collectively as the "Portal User" agent. That value can be used to filter out customer data from a report.
  • The Satisfaction Rating is an aggregate value taken from all cases (for a given agent, on a given day, at a given priority) for which a survey was completed.
§ Filter by agent &/or date range &/or priority in a report
--stores data for each agent, for a given date
--times stored in minutes (the business calendar is not taken into account)
--show code to convert to hours and days
--only types=problem or incident are recorded
--customer_satisfaction_case_record_count is the number of cases that have a customer_satisfaction rating. Use it to calculate average for the day.
--Time to Resolve is total time for all cases resolved
Divide by Resolved Cases to get an average
--Agent Interactions (msgs from an agent) & Customer Interactions (msgs from a customer)
--when the "agent" is "portal user", agent interactions is always zero,
and customer_interactions is the total number of messages sent by customers