I threw this out as a ticket, but wanted to see if anyone has asked similar questions, get more thoughts. Thanks!
I need to know precisely what events start and stop the clock used to calculate the "AVERAGE FIRST RESPONSE TIME (IN HRS)" metric.
For example, the "Group at a glance" report includes the metric "AVERAGE FIRST RESPONSE TIME (IN HRS)."
I need to know, exactly and specifically, which events trigger that timer and end it.
I could assume that the response time is calculated by the difference in the ticket's creation time until the first response is made.
However - I don't know if the system is smart enough to account for business hours.
Our business hours are 830am-530pm EST.
If a ticket is created at 0001, and responded to at 0832, is that a 1 minute response time, because the system is accounting for business hours?
OR - is that an 8 hour and 31 minute response time, because business hours are not accounted for?
Does the first response clock stop when:
a reply is sent?
What about a Forward?
What about a note (private)?
What about a note (public)?
I know that the first response clock doesn't stop when a private note or forward is added to the ticket. I've only seen it stop when a reply is sent or a public note is added.
From what I understand, the FR timer is triggered when the ticket is created, but only runs during normal business hours. So that means if you responded at 0832 (in your example above), that would be a 2 minute response time (since the timer started at 0830). The devs can correct me if I'm wrong, but I believe this is how it works.
I agree that this is not clear. I don't want to turn my staff into robot's just responding for the sake of responding, that is the opposite of good customer support. That said, I do want them to review every ticket that comes in and make sure that it's prioritized correctly and in the right place ASAP. I'm trying to use the FR timer as an indication of that activity, so a private note, or metadata update should be able to be considered first response if that's how our system works.
This seems like a configuration item that different shops would treat in different ways depending on their needs.