Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Open investigation] Understanding Zendesk agent replies metric edge cases #104

Open
fivetran-avinash opened this issue Jul 12, 2023 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@fivetran-avinash
Copy link
Contributor

We are looking for input on the Zendesk agent replies metric. Currently we believe that our model accounts for agent replies in most situations (see our latest PR).

But we did find discrepancies between the Zendesk Explore numbers and ticket reply numbers on our data occasionally. Here were two edge cases we encountered:

  • If an agent creates a ticket with an internal comment, and then replies to that ticket, is that internal comment the ticket being created and the external reply logged as a legitimate reply? We were seeing an undercount of replies by 1 in our own modelling compared to the number of replies in a ticket in the Zendesk Explore.

  • How replies are logged to tickets that are follow up to tickets. Does a new ticket log a reply from an old ticket as a reply, or the first comment created? We were seeing an overcount of replies by 1 in our own modelling in the Zendesk explore, because our model can bring in those agent comments from merged tickets.

Have you encountered these issues as well? If you have, or have seen any differences between the Zendesk replies on your internal data vs our own, please let us know in the comments!

@fivetran-avinash fivetran-avinash added the help wanted Extra attention is needed label Jul 12, 2023
@fivetran-jamie
Copy link
Contributor

also if an employee leaves the company and their role might in zenedsk. we specifically look at the role (agent or admin) for calculating reply time metrics, but these former employees might now be end-user. we may want to introduce a variable where people can input the company's email domain or some other criteria for determining former employees

@jackiexsun
Copy link
Collaborator

also if an employee leaves the company and their role might in zenedsk. we specifically look at the role (agent or admin) for calculating reply time metrics, but these former employees might now be end-user. we may want to introduce a variable where people can input the company's email domain or some other criteria for determining former employees

I created #120 related to this!

@fivetran-avinash
Copy link
Contributor Author

@jackiexsun @fivetran-jamie There appears to be an audit log for tracking changes, perhaps this is where we can find information on whether users used to be admin?

https://developer.zendesk.com/api-reference/ticketing/account-configuration/audit_logs/

Looks like this audit_log model is also present in our internal data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants