I want to duplicate tickets
RespondidaSo, our organization uses Zendesk for several groups. We route those to the groups based on the email address of the requester.
There are some times that we need the ticket to go multiple groups. For example, when we get a ticket from HR about a employee being terminated, we need the group that handles the employee directory to be notified as well as the group that handles software permissions.
Is there a way for a trigger to create TWO tickets based on ONE email?
Thanks,
Tim
-
Tim Hardin, maybe the Collaboration Add-on can help you with that. You can create tickets for other groups when they meet some criteria.
-
Unfortunately, no you can't create 2 tickets from 1 email unfortunately.
In the use case you're describing, just thought I'd share that in the past, I've set up a system where the ticket goes from group to group to get things taken care of (assuming no info is included that can't be shared). I put in a series of checkboxes for each step in offboarding on the Offboarding form and we trained the teams to check off when they've done their part of the ticket and just hit submit (not submit as solved) and I had a series of Triggers that would automatically reassign the ticket to the next group in line needed to do their task on the ticket.
When all checkboxes were checked, I autosolved the ticket.
The drawback to this method is you can't really measure who's spending time on the ticket based on # of solved tickets. You'd have to use a time tracking tool of some sort if you need that. Or just assume a certain % of the team's time is allocated to onboarding/offboarding.
The other option is Julio's suggestion above. I'm not a big fan of side conversations, because it feels scattered/unruly to me. Just my personal opinion though.
Hope something here helps!
-
An automatic way of of notifying the second department would be a trigger. You could send a notification to another group- but it is not really using a new ticket. You could add a follower to a ticket, but that would be a named agent and not a group.
I agree that side conversations can be a little messy but it keeps all actions in Support. You cannot initiate a side conversation from a trigger but you can with a macro.
Iniciar sesión para dejar un comentario.
3 Comentarios