Auto-solving Zendesk tickets created from Zopim chats | Community
Skip to main content

Auto-solving Zendesk tickets created from Zopim chats

  • July 4, 2016
  • 10 replies
  • 0 views

Jacob20

This setup is our way of minimizing the administrative handling of tickets by Zopim agents, but I'm not completely happy with it, would love it if someone had better ideas or suggestions for improvements.

Motivation

The amount of tickets we get from chat that need a follow up from Zendesk is about 7-8 %, so most of the time tickets just need to be solved after chat has ended.

Instead of agents switching between Zopim and Zendesk to handle the solving process, I have set up an automation in Zendesk to solve chat tickets unless they have a particular tag.

Since tags are transferred from chat sessions to tickets, the agents can apply the tag during, or when ending a chat session and the ticket will get solved by the automation.

Setup

Our agents are instructed to apply the tag keep_alive whenever they need to follow up on the chat from Zendesk (using a shortcut for convenience).

An automation runs an hour after ticket creation to solve chat tickets without this tag that are not already solved. 

Now you could use a trigger to achieve the same, but I kept getting problems with updates coming in and disrupting - I forget what exactly, some time has passed since I set it up.

Conclusion

The setup works as intended, but every now and then an agent forgets to apply the tag and tickets are inadvertently solved.

The one hour delay from end of chat to ticket solve also skews reporting on Full resolution times. 

So if anyone has something clever working for them, I would love to hear about it!

10 replies

  • December 13, 2016

Hi Jacob,

We had a very similar situation and it was taking an age to close all the tickets each day.

I set it up using 3 triggers, one for missed chats or contacts that arrived out of hours . These were prioritised so that agents could contact customers faster.

2nd trigger allocated chats that required a follow up

3rd trigger is like yours and set to solve the ticket. However it does give us an issue; for emails we force the agent to categorise the enquiry type before they can solve the ticket. it is proving challenging to do the same for chats. We have 12 categories so I am think that would mean 12 triggers  

 


  • December 13, 2016

Hi Jacob,

We had a very similar situation and it was taking an age to close all the tickets each day.

I set it up using 3 triggers, one for missed chats or contacts that arrived out of hours . These were prioritised so that agents could contact customers faster.

2nd trigger allocated chats that required a follow up

3rd trigger is like yours and set to solve the ticket. However it does give us an issue; for emails we force the agent to categorise the enquiry type before they can solve the ticket. it is proving challenging to do the same for chats. We have 12 categories so I am think that would mean 12 triggers  

 


Jacob20
  • Author
  • December 14, 2016

Hi Jennifer,

Nice!

We also have the categorization issue - for now we have agents apply tags (cat_categoryNameExample) to their chats manually when chatting, and when the ticket gets updated a trigger sets the category value based on the category tag. One trigger per category.

Not at all perfect, and more often than not the tagging is missed by the agent leaving the ticket un-categorized.

Thanks for sharing your setup!


  • January 29, 2017

HI, Did anyone find a solution for the categorization issue.  For our purposes, I could have the agent mark the ticket as solved, using a tag, and apply a category - so solved_install for instance as the tag.  But I don't see how to make this trigger a category on the ticket. 


Jacob20
  • Author
  • February 21, 2017

Hi Cheryl,

Sorry I missed your comment. I believe I did a write up on exactly that a while ago, but cannot find it at the moment.

Basically what you would do is create a trigger in Zendesk for each categorization tag you would like to set from a chat conversation.

Criteria:

  • Ticket is Updated
  • Channel = Chat
  • Ticket: Tags Contains at least one of the following 'your-category-tag'

Actions:

  • * Ticket: 'Your categorization field' 'categorization field value

*I'm assuming you already have a categorization field on your ticket form.

See example below - hope that helps.


Jennifer16
  • February 21, 2017

Thanks for helping out, Jacob. And welcome back!  :)


  • July 17, 2018

Howdy, I’m perplexed why a chat only agent is still unable to set to solved at chat completion. This should be a role settting permission at least. Is there some legacy technical issue that is keeping this feature request from being implemented? Thanks for the above trigger route examples guys!


  • July 18, 2018

Hi Stephen!

What you're seeing is expected behavior, because Chat-only agents don't occupy a Support agent license. Because Chat-only agents aren't actually Support agents, they won't have the ability to change any ticket properties, including changing the ticket status.


  • January 29, 2020

Hi all,

Has anyone found a new solution for this? We need a way to mark the ticket as solved right from the ongoing chat? Is there a way to do that?


Devan
  • February 5, 2020

Hello @Armen Saghatelian,

As our current base product stands, there is no way to accomplish this currently. I would recommend posting on our product feedback forum so our developers can consider this change for future product updates.

Best regards.