# Time to First Agent Reply not Correctly Calculated **URL:** \ **Category:** HubSpot Ideas\ **Tags:** help-desk\ **Created:** [February 6, 2019, 2:09pm UTC](https://community.hubspot.com/t/time-to-first-agent-reply-not-correctly-calculated/12813 "2019-02-06T14:09:51Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![basil](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/basil/32/22307_2.png) [@basil](https://community.hubspot.com/u/basil)\ **Post date:** [February 6, 2019, 2:09pm UTC](https://community.hubspot.com/t/time-to-first-agent-reply-not-correctly-calculated/12813/1 "2019-02-06T14:09:51Z")
We switched from Zendesk to Hubspot. Unfortunately, it seems that Hubspot does not handle the calculation of “Time to first agent reply” correctly which messes up our KPIs. Our workflow is: 1. Customers write to a hubspot conversation inbox. 2. Agents then qualify messages individually and create a ticket where needed. When an agent now creates a ticket for a conversation, the reply time is calculated based on the ticket create time instead of the first message time. This can make a huge difference whenever the ticket is created after the first message. ![screenshot (1).png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/f/9/f9693d73cffbc9884a9dee1bb5c7f6cd8dd52c7f.png) Basically in the example above, the actual time between the first message associated with the ticket and the first reply of the agent is 14 hours. However, the time between creating the ticket and the reply is 4 minutes. So our KPI in the dashboard thinks we replied within 4 Minutes. I understand that the current definition of the Time to First Agent Reply is _defined_ as time between create time to first reply time. However, I would argue, that there is no scenario where the following definition would not make more sense: Time to first agent reply = Min(Ticket Create Time OR Time of First Message Associated with Ticket) - Time of first reply whereas Min means “whichever was earlier”. For all the companies who create tickets automatically from messages, the property would remain unchanged. The others would in my opinion prefer to know the true reply time. Also I don’t think custom properties are a good solution since all the default graphs use the property “time to first agent reply” and they should also work with a workflow that does not automatically create tickets. Hope that makes sense ---
**Author:** ![juliansurber](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/juliansurber/32/99782_2.png) [@juliansurber](https://community.hubspot.com/u/juliansurber)\ **Post date:** [February 6, 2019, 3:09pm UTC](https://community.hubspot.com/t/time-to-first-agent-reply-not-correctly-calculated/12813/2 "2019-02-06T15:09:04Z")
+1 Completely agree with basil. ---
**Author:** ![SarahCame](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sarahcame/32/44503_2.png) [@SarahCame](https://community.hubspot.com/u/SarahCame)\ **Post date:** [September 26, 2019, 2:27pm UTC](https://community.hubspot.com/t/time-to-first-agent-reply-not-correctly-calculated/12813/3 "2019-09-26T14:27:46Z")
The same goes for first chat reply if its unassigned when it first comes in, we need to know how long it’s taking our support team to get the chat assigned to the right person and replied to. ---
**Author:** ![liangsj](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/liangsj/32/20452_2.png) [@liangsj](https://community.hubspot.com/u/liangsj)\ **Post date:** [July 12, 2021, 11:12pm UTC](https://community.hubspot.com/t/time-to-first-agent-reply-not-correctly-calculated/12813/4 "2021-07-12T23:12:56Z")
Submitting on behalf of customer +1 ---
**Author:** ![Yupvoted](https://avatars.discourse-cdn.com/v4/letter/y/e36b37/32.png) [@Yupvoted](https://community.hubspot.com/u/Yupvoted)\ **Post date:** [April 25, 2022, 5:39am UTC](https://community.hubspot.com/t/time-to-first-agent-reply-not-correctly-calculated/12813/5 "2022-04-25T05:39:43Z")
This method of calculation needs to be in the software as the customers are looking to track their average response time since their tickets are not assigned automatically but picked by their users, they all have 0 response time here which is not valuable information for the customer. ---
**Author:** ![GSebton](https://avatars.discourse-cdn.com/v4/letter/g/919ad9/32.png) [@GSebton](https://community.hubspot.com/u/GSebton)\ **Post date:** [September 13, 2022, 6:07pm UTC](https://community.hubspot.com/t/time-to-first-agent-reply-not-correctly-calculated/12813/6 "2022-09-13T18:07:13Z")
Is it possible for first agent email reply to re-calculate if we update the create date to match the customer’s first remail? ---
**Author:** ![Anonymous\_de24fb92ae94c255a8e1959e046394cc](https://avatars.discourse-cdn.com/v4/letter/a/ecae2f/32.png) [@Anonymous\_de24fb92ae94c255a8e1959e046394cc](https://community.hubspot.com/u/Anonymous_de24fb92ae94c255a8e1959e046394cc)\ **Post date:** [July 10, 2023, 6:05am UTC](https://community.hubspot.com/t/time-to-first-agent-reply-not-correctly-calculated/12813/7 "2023-07-10T06:05:07Z")
ぜひ、（値なし）は対象外にしていただけると、大変助かります。ぜひ、ご検討宜しくお願い致します。