Recent searches


No recent searches

Add View Option for Tickets Without First Reply



Posted Jul 27, 2016

It would be good to have an option to create a view to display tickets without the agent first reply.

I have had an issue with spikes in first response time in Zendesk and it's been very difficult to pin down the offending tickets. It would be very helpful to have an option to create a view to display these tickets without a first response (as per Zendesk's FRT system).


14

23

23 comments

For more context surrounding this, please see my Q&A thread (created before I was advised to make this thread). I have done my best to weed out all offending tickets, but the issue still seems present. Having access to this view would make the task much easier!

 

https://support.zendesk.com/hc/en-us/community/posts/212051088-Show-Tickets-Without-First-Response?page=1#community_comment_219893187

0


Is there an update on this request?  We have an automation that force assigns unassigned tickets that are aging beyond our max SLA, and doing so of course changes the status from New to Open, losing any ability we have to easily determine whether or not an IR has been made for those tickets.  This is also problematic for creating an agent view that groups/sorts by non-IR'd tickets.

1


Rob Baker: There was never any movement in regards to having a view for this.

I was contacted by a Zendesk employee with some information on how to structure a search to achieve the same thing - though I'm not sure how that would apply in your case.

Maybe if you get in touch as well, and link back to this thread, it might prompt this to be implemented in the future.

0


Hi all,

I would love to have this as a feature - it surprises me it is not a feature already. It is basically a loophole in the Zendesk system as it assumes that all unassigned tickets will get answered as soon as they are assigned when our team does not work that way.

Our team generally goes through the tickets and assigns them to themselves before answering them so this feature is vital for admins to see exactly which tickets still need replying to.

At the moment it is incredibly hard to locate tickets without a first reply, short of going through every single ticket manually. In my opinion this is a massive oversight as it means agents can sit on or solve tickets and reduce the number of unassigned, unanswered tickets artificially simply by assigning them to themselves and leaving them open without actually replying.

Please fix this soon Zendesk!

0


Is there any update on this feature request?

0


I can share with others how we worked around this limitation.

We simply amended the notify requester of comment update trigger to add a tag called ir_completed .  Then we created a corresponding view for all tickets < solved w/o that tag grouped by status ordered by ticket created date in reverse chronological order. 

The trigger criteria looks like the following:

and the view criteria just needs to look at all tickets that do not have that tag.

2


Thanks a lot for the workaround.

I send a +1 to have this criteria in the views. It would be very helpful to identify ticket with : 

- 0 response -> To trigger alert to admin/supervisor about a ticket that has not been answered by an agent

- X responses -> sometimes a ticket with too much response means the problem is difficult to solve, so it would be good to define alert based on that criteria too.

1


We would also find this really useful!

0


+1 for this kind of feature. 

0


The system should give us the option to differentiate between different SLAs. For example, I would like to create a view of tickets without First Response only.

0


image avatar

Nicole Saunders

Zendesk Community Manager

Thanks for adding your comment, Jiri!

0


This is something that we are also trying to achive, would be great to be able to have a visibility over tickets that are lacking first response.

0


Is this still not something you can do easily in views?

0


image avatar

Mike DR

Zendesk Customer Care

Hi Sakina,

I'll work with you on the ticket :)

Cheers,
Mike dela Rosa | Customer Advocate

NEW - Zendesk offers free, on-demand training for all of our products. Set up your account and start learning today at training.zendesk.com

0


Any updates or directions from Zendesk on this one?

0


Hi, I am trying to create this view but I think the above work around may now be out of date.

Could someone confirm the step by step please.

Thanks

Joe

0


image avatar

Cheeny Aban

Zendesk Customer Care

Hi Joe, 

If you already created a view and having an issue with the conditions, we'll be glad to check it for you. You may initiate a conversation with us anytime!

0


Is this something that Zendesk can offer as out of the box functionality (via view condition) without needing to do extra step to create trigger etc.

0


image avatar

Salvador Vazquez

Zendesk Product Manager

Hello and thank you for this great feedback. We are going to be making improvements to the conditions of Views next year, 2024. This will be included in the list of conditions to add to views. I understand views is sometimes used to keep track of tickets that may go unseen to stay on top of metrics. I have one question, are you all interested more in tickets that have no response or just the count of tickets with no first response or both?

1


Good to see some progress here.    Not sure I understand the question, as a ticket with a first response would satisfy the condition, so that it would no longer be a ticket with no response.   Tickets that have no response would also be tickets that have no first response.

It would be interesting to get a histogram of # or responses per ticket, so you can see how many responses are typical to close out a ticket.

0


Salvador Vazquez - What I'm reading from the thread is that people are interested in specific tickets without a first response, presented in a view.  A count doesn't really help to know which tickets need responses most quickly. 

A view or column in a view would be the desired outcome.  For example:

A triage queue would be build around tickets missing desired attributes; lets say Priority, Type and No First Response.  Tickets missing any one of those 3 attributes would be used as the first tickets to view for a support team. Once all 3 of those criteria are met, it would drop from this view

Meaning that the ticket would be properly configured to trigger Completion SLA tracking and other configured business logic.  More importantly, it would help to ensure that customers have been communicated with in a timely fashion to help boost their experience and increase their overall satisfaction.  

Hope this helps!  And like everyone else, very curious as to when these improvements may be launched

0


Hi just to add some insight. CX teams will use views to see which tickets still need a response (sometimes they use the assignee condition as a proxy for first response. no assignee and new likely = ticket has no response). But when you look at tickets that are assigned to an agent, there is  no way of identifying whether a ticket has a response yet or not. 

Being able to use a condition that adds/removes tickets from a view based on whether a ticket has a frist reply is extremely useful because we it represents the customer's experience (have a reply vs no reply). 

Most teams goal themselves  heavily on first reply SLA, so this is a practical way to see which tickets still need a first reply and manage those tickets. 

Count of tickets does not really achieve this  becuase you're not seeing the actual tickets that still need a response. 

 

 

0


image avatar

Shawna James

Community Product Feedback Specialist

Thank you for your continued feedback here Andrew! We appreciate you taking the time to share your insights with us. 

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post