Theodore Wolf

Thanks @...!

 

I've tried using this setup in the past, but after spot checking a few tickets, it would still include some that had the tag. Did you do any custom metrics on this query?

Thanks @...!

Essentially we want to just show the level 3, as its the "meat and potatoes" of our reporting. 

Im curious if you'd know, could we modify the initial metric to just show solved tickets and exclude the "closed_by_merge" tag?

We want to use this as a way to track agents solved tickets, and I think a hybrid of this post and this one would do a great job. 

Thanks!

Hey Team,

@...

Is there anyways we could report on just the level 3? Or would you recommend just hiding those lower levels in the chart configuration?

And could I potentially layer this with: https://support.zendesk.com/hc/en-us/articles/360052540974-Explore-recipe-Excluding-tickets-closed-by-merge 

Thanks!

 

Hi Nicole,

That is very exciting to hear! This is definitely something our team is looking to leverage.

+1

Would love to use the proactive trigger if we can get some details up front.

Hi there,

 

We've run into this issue as well. +1 

Hey team,

I would love to see audit logs on queries!

Our team has a group of people who contribute to a bi weekly reporting dashboard. Sometime we have to adjust quires, and this can get quite hectic when multiple people are editing things. I know the dashboard locks others out when one person is editing, but when it comes to individual quires, seeing what has been added or changed, could be quite helpful, while developing reporting standards as a team. 

Thanks!

+1 we'd love this feature too. 

 

Case: export data filled out into form directly to internal note or side convo (using liquid) so we can initiate requests quicker. 

Hey Team,

Is there anyway to integrate this the opposite way? We'd like to push form fields to google sheets using a webhook or target maybe? 

Cheers!

+1 for this idea!

We currently coordinate with our B.A.'s an internal article that only employee's see, then convert that to an external article that customers will see. It would be nice to have both an external and internal article exist on the same page! 

That way, when logged in agents view the article, they could see extra troubleshooting steps (or info) that the customer doesn't necessarily need to see.