Service Analytics and Reporting
Reports that survive scrutiny
Service reporting is mostly about time: time to first response, time to resolution, time in each status, and milestone compliance. Standard case reports give current state; Case History gives field-change history; Case Milestones give the entitlement clock. Design reports by asking which object holds the timestamp you need - many "why is this number wrong" questions are really "you reported on the wrong object."
Mechanics to name: report types and their relationships, filters and cross-filters, summary vs matrix formats, dashboards with a running user (dynamic dashboards render as the viewer), reporting snapshots for point-in-time trends, and scheduled subscriptions. For high-volume or predictive needs, CRM Analytics and AI-driven analytics extend beyond standard reporting.
Traps: field history tracking has a small per-object field limit and a retention window, so it is not an audit log; dashboards show the running user's sharing, so a supervisor's numbers can look "wrong" to an agent; snapshots capture the past but cannot be edited backward; timezone settings silently shift date filters.
Rule of thumb: one dashboard per audience. Executives want trend and SLA compliance; supervisors want backlog and agent workload; agents want their own queue. Same data, different grain.
Worked example: A milestone report shows 98% compliance while customers complain. The targets were built on a 24x7 business-hours calendar while the team works 9–5. Correct the calendar and the metric becomes honest.