Question
In my Explore report, I am using the metrics First reply time and First resolution time. The First reply time is higher than the First resolution time. What causes the agent reply time to be higher than the ticket resolution time?
Answer
A common cause for a lower average First resolution time occurs when a ticket is created in Solved ticket status or solved without an agent reply shortly after it is created.
If you have a business rule or process that automatically Solves certain tickets, those tickets will have a low or First resolution time and a null First reply time value. These tickets count towards the First resolution time average, but they do not count towards the First reply time average because there is no agent reply for these tickets.
If you wish to adjust for these types of tickets, this will require a custom metric in Explore or a report to filter for only tickets that received an agent reply.
For more information, see the articles:
1 comment
Basyl Durnan
For any one else who finds this page and the above doesn't seem to be their problem, we realized that it was due to "resolution" not including unsolved tickets. Once we filtered for only solved or closed tickets on both "resolution" and "first reply", then our numbers made more sense.
1
Sign in to leave a comment.