The Reports tab in Service Desk answers the questions support managers get asked: are we keeping up, how fast do we reply, are we hitting our promises, who is carrying the load. Nothing needs setting up; the reports read the tickets you already have. Reports that depend on SLA policies stay empty until you create some.
| Report | Question it answers |
|---|---|
| Created vs Resolved | Are we keeping up? Tickets Created against Resolved over time, with the running Backlog. |
| First Response Time | How long does a customer wait for a first public reply? Median, P90, and Average, in hours. |
| Time to Resolution | How long from arrival to resolution? Same three statistics. |
| SLA Attainment | What share of SLA-covered tickets met their promise? |
| Agent Activity | Who is doing the work: Replies sent and Tickets resolved per agent. |
| First Contact Resolution | How often is a ticket resolved without a second round trip? Shown against an industry benchmark of 70–80%. |
The toolbar above the reports applies to all six:
| Control | What it does |
|---|---|
| Day / Week / Month | How time series are bucketed. Day for a busy week, Month for a year in review. |
| From / To | The date range. |
| Group by | Split into series: None, Channel, Company, Work Type, Priority, or Agent. |
| SLA-policied only | Restrict to tickets covered by an SLA policy. |
Grouping is where the reports earn their keep: First Response Time grouped by Company shows which customers wait longest; grouped by Channel it shows whether email requests get slower answers than portal ones. If a report shows No data for the selected period, widen the range or clear the grouping.
Click Export CSV and pick the report. DevStride confirms "Export queued — find the CSV in the analytics exports list." The export runs as a background job with the filters you have applied, and you collect the file from the analytics exports list in the Reports module. The button appears only if you can reach that list (the Access Reports permission).
The tab needs the Read report throughput permission, which the Service desk agent role template includes. For a custom role, grant that permission to add the tab, and Access Reports to export. See Permissions.
Two ticket fields record what the customer considers urgent, separately from your internal priority: Importance (Critical, Important, Nice to have) and Customer Rank (the customer's own ordering). Both are sortable columns and filters; see Finding & Filtering Tickets and Working a Ticket.
Time-Based Ticket Automations
Act on tickets based on how long something has taken: auto-close solved tickets, escalate one nobody has answered, nudge a quiet customer, measured against business hours. Plus the other Service Desk automation triggers and the Send Customer Reply action.
How email replies find their ticket
The exact order of checks DevStride runs on every inbound email to decide whether it belongs on an existing ticket or opens a new one: the reply address, email headers, the subject tag, staff forwards, and what each one requires.