Ticket analytics
Read the Analytics page: how many tickets came in, how fast customers heard back, and how fast tickets closed, compared with the period before.
Read the Analytics page: how many tickets came in, how fast customers heard back, and how fast tickets closed, compared with the period before.
Read the Analytics page: how many tickets came in, how fast customers heard back, and how fast tickets closed, compared with the period before.
Analytics answers three questions in order: how much came in, how fast customers heard back, and how fast tickets closed. Every number is compared with the period right before it.
Open Analytics in the left sidebar. Anyone on your team can see it.
Use the Reporting period tabs: 7 days, 30 days, 90 days, or 12 months. The default is 30 days. You can't pick custom dates from the page.
Each tab compares with the period of the same length that comes right before it. For 30 days, that's the 30 days before those. Next to each number you see the change, and a note says whether it's better or worse. If the earlier period can't be loaded, the page says the comparison is unavailable and shows current values only.
The chart groups tickets by day for 7 and 30 days, by week for 90 days, and by month for 12 months.
All numbers count tickets by the date they were created. Spam isn't counted. You only see tickets from inboxes you have access to.
| Number | How it's calculated |
|---|---|
| Received | Tickets created in the period. |
| Resolved | Of the tickets created in the period, how many are now closed. Any close counts: resolved, invalid, or other. A ticket created in the period and closed later still counts. |
| Backlog change | Received minus Resolved. A plus sign means more tickets came in than were closed. |
| First response | Time from when a ticket was created to the first message from someone on your team. It uses the clock, not your business hours. |
| Time to resolve | Time from when a ticket was created to when it was closed. |
Because Resolved follows the creation date, tickets you closed this week that were created before the period don't count toward it.
First response and Time to resolve don't show averages. One ticket that waited three days would distort an average and describe a wait nobody had. Each card shows percentiles instead:
| Label | What it means |
|---|---|
| Median | Half of the tickets were handled faster than this. |
| 90th | Nine in ten were handled within this time. |
| 95th | Nineteen in twenty were handled within this time. |
| 99th | Ninety-nine in a hundred were handled within this time. |
Under each chart a sentence sums it up, such as "Half of customers heard back within 2 hours". When the slowest tenth waits much longer than the median, it adds how many times longer, for example "6× longer". A big gap means most customers are fine and a few wait a long time.
The badge on each card counts the tickets measured, for example "12 replies" or "9 tickets resolved".
The reporting index didn't answer. Your tickets and conversations are fine. Only this report is missing. Select Try again, or reload the page.