Question
How can I automatically assign a follow-up ticket to the agent that was assigned when the ticket closed?
Answer
By default, you can not assign a follow-up ticket to the assignee of the ticket at the moment they closed. As a workaround, create a workflow through the use of triggers and tags for each agent to achieve this goal.
To set up this workflow you need to create three triggers:
Adding agent tags to tickets
The first trigger you need to set up adds agent tags to tickets automatically.
To add agent tags to a ticket with a trigger
- Create a new trigger.
- Add the following conditions under Meet ALL of the following conditions:
- Ticket | Is | Updated
- Assignee | Changed to | (agent name)
- Add the following actions under Actions: Add tags | (agent name)
Find below an example of what your trigger looks like.
Auto-assigning a follow-up ticket
Create a trigger that auto-assigns any follow-up ticket to the desired agent. This trigger utilizes the tag that your first trigger applies to indicate who the ticket should be assigned to.
To auto-assign a follow-up ticket with a trigger
- Create a new trigger.
- Add the following conditions under Meet ALL of the following conditions:
- Ticket | Is | Created
- Channel | Is | Closed ticket
- Tags | Contains at least one of the following | (agent name)
- Add the following action under Actions:
- Assignee | (agent name)
Find below an example of what the trigger looks like.
Removing a tag from an agent
The last trigger is designed to remove an agent tag, in the event that the ticket gets reassigned to a different agent.
To remove a tag from an agent using a trigger
- Create a new trigger.
- Add the following conditions under Meet ALL of the following conditions:
- Ticket | Is | Updated
- Assignee | Changed from | (agent name)
- Add the following action under Actions:
- Remove tags | (agent name)
Below is an example of what your trigger could look like:
13 Comments
Do you have to create this set of triggers for each agent?
Or is there a way to dynamically add/remove a tag that I am missing?
Welcome to the community! Unfortunately, you'd have to do this separately for each agent.
Hello Brandon, you may be able to do part of this using (our) Agent Activity Tags app. This will add tags for every agent updating the ticket, and you would need modify this behaviour by perhaps removing all agent tags when the ticket is reassigned or something. Might help - just an idea.
Hi Zendesk Team,
Are there any plans to implement assignee retention on follow up tickets in 2022? For companies of scale who pass tickets between agents frequently, setting up tags and nullifiers for each individual agent seems unnecessarily inefficient.
No plans that I'm aware of, but this product feedback thread is the best place to follow when we do have information: Preserve Group and Assignee for user-generated follow-up tickets
There should be a more straightforward and seamless solution to a basic problem. Having to tag a ticket with the original agent's name seems a little silly.
Currently, it seems like the best way to go about this is to create a webhook to update the ticket.
How can i assign to the same group ? every time i tried this it changes to any other group that my agents are into
If your agents are assigned to multiple groups, unfortunately, at this time there's no native Trigger action that would allow retaining the same group in follow-up tickets. However, I found a suggestion posted by another user on this thread that you can utilize for now.
I highly suggest that you also upvote this feature request and leave a comment on the thread with your use case. Although it's been a while since this post was created, our Product Managers continue to monitor our feedback threads, and conversations with high user engagement ultimately get flagged by the team for roadmap planning.
Thank you.
My workaround to this issue with Zendesk is that I created 2 hidden fields:
Then, I used a webhook with JSON to auto-set these two fields with the group id and assignee user id to these fields, and then when a follow-up is created, I have a single trigger that sets the follow-up ticket's group and assignee to these saved values in the hidden fields.
I reported an issue back in June that when a requester replies via email to a closed ticket, the follow-up ticket loses the HTML formatting, so the text is all "jumbled" together - no paragraph separations. If you click "View original email," the email itself is fine. The agent acknowledged this as a known issue. I have now raised a new ticket on behalf of a second organization with this same issue.
I checked in with the agent a few times over the last 4 months, and there is no update. Could you please share the timeline for resolving this issue?
Our workarounds:
I hope someone will have an update to share.
We updated the ticket you raised with our support team related to this issue. Kindly check your email for more information. Thanks!
As a workaround, I used Zapier to reassign the ticket back to the last assignee based on a tag. Here's a Zapier template that you can reference: https://zapier.com/shared/f287afe7e341425fe5fcf7a92fb02f7e6ff3a641
The logic works as follows:
Please sign in to leave a comment.