Calculating Next Reply After First Reply Time

1 Commentaires

  • Gab
    Zendesk Customer Advocate

    Hi Matthew,

    That's right. There's no function or any native options within Explore that could exactly pull up the date or timestamp of agent reply that came after the first response. But, the workaround that you have in mind – events where the status was changed from open to pending – might be a possible solution. In your workflow, are first agent responses sent out when the ticket is in the New status? This way, the first reply can be distinguished from the subsequent replies when the status is changed from Open to Pending. Under the Ticket updates dataset, you can create a custom attribute to get the timestamp of the first reply by using the earliest date function for agent public comment. This technically should be the first reply timestamp. You can then calculate the duration from ticket creation to first reply (from the custom date attribute) using DATE_DIFF. This will the First reply time in your Ticket updates dataset.

    You can create another custom attribute that will get the timestamps of events where the status was changed from Open to Pending. You may check out this thread for some guidance on how to use Changes - Field name and - Previous/New value in an attribute formula. Use the date_diff function again in another custom metric to calculate for the duration between ticket creation and these timestamps. If your report is sliced by ticket ID, you can use the aggregator MIN to get the minimum value.

    The difference between the custom First reply time custom, and the other custom metric should give you the duration between first agent response  and the next agent reply.

    Sorry if Explore does not have native functions for this, and if we're not able to provide exact recipes for this custom report. But, this might be worth exploring, and I hope this would work for you. Thanks Matthew!


Vous devez vous connecter pour laisser un commentaire.

Réalisé par Zendesk