NETWORKDAYS/nb_of_business_days function on Explore



Posted Apr 08, 2025

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. 

I would like to be able to use the NETWORKDAYS function, such as in Excel, in Zendesk Explore. At the moment, the lack of this function is affecting the ability to count how many business days (excluding Saturday, Sunday and Holidays) a ticket is unsolved in the Support dataset.

 

What problem do you see this solving?

Be able to know how many business days a ticket is unsolved, excluding weekends and holidays, with a calculated metric. Currently there is only the “Unsolved tickets age (days)” metric, which counts calendar days.

 

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business?

This problem occurs weekly during the follow-up of each team's unresolved tickets. This is fundamental to our business, because we have a routine for monitoring SLAs and sending scheduled reports Explore dashboards to each team.

 

Are you currently using a workaround to solve this problem? (If yes, please explain)

Yes, I manually download the report and use Excel to apply the NETWORKDAYS function to get the difference in business days between the creation date and the current date. 

 

What would be your ideal solution to this problem? How would it work or function?

With a NETWORKDAYS function or “nb_of_business_days” attribute in the DATE_DIFF function, to get the count of business days from [Ticket created - Timestamp] to NOW or [Ticket solved- Timestamp]. 

An example would be: DATE_DIFF(NOW(), [Ticket created - Timestamp], “nb_of_business_days”)


0

1

1 comment

Hey Leonardo,
 
Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!

1


Sign in to leave a comment.

Didn't find what you're looking for?

New post