English (US)
  1. Zendesk help
  2. Support
  3. Support advice and troubleshooting
  4. General questions and issues about tickets

后续如何保留票,票吗signee?

Zendesk Team
  • Edited

Question

How can I automatically assign afollow-up ticketto 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 aworkflow through the use oftriggersandtagsfor 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

  1. Create a newtrigger.
  2. Add the following conditions underMeet ALL of the following conditions:
  • Ticket | Is | Updated
  • Assignee | Changed to |(agent name)
  • Add the following actions underActions:
  • Add tags | (agent name)

Find below an example of what your trigger looks like.

Note:Tags can also be added touser profiles. User tags also tag tickets in the same manner as the trigger described above.

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

  1. Create a newtrigger.
  2. Add the following conditions underMeet 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 underActions:
  • 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

  1. Create a newtrigger.
  2. Add the following conditions underMeet ALL of the following conditions:
  • Ticket | Is | Updated
  • Assignee | Changed from |(agent name)
  • Add the following action underActions:
  • Remove tags |(agent name)

Below is an example of what your trigger could look like:

Note:If an end user responds to aproactive text, the ticket that is created from the response is treated as a brand new ticket. In this case, tags are not transferred from the proactive ticket to the ticket that is created from the end-user's response.
For more information about follow-up tickets, see the article:How can I reset drop-down field values for follow-up tickets?.
    Return to top

    13 Comments

    • Brandon Martus

      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?

      1
    • Dave Dyson
      • Edited
      HI Brandon,

      Welcome to the community! Unfortunately, you'd have to do this separately for each agent.
      0
    • Andrew J
      Community Moderator

      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.

      0
    • Adam Glover

      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.

      1
    • Dave Dyson
      Hi Adam –

      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
      1
    • Allen Lai | Head of CX, Otter.ai

      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.

      1
    • Walter

      Currently, it seems like the best way to go about this is to create a webhook to update the ticket.

      0
    • Zerviz Admin

      How can i assign to the same group ? every time i tried this it changes to any other group that my agents are into

      0
    • Christine Felicia
      Zendesk Engineering
      Hi Pablo,

      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 thisthreadthat you can utilize for now.

      Follow-up tickets inherittags. We can use this to assign them to the group the original ticket was assigned to. For this, I add a unique tag per group on every ticket created.

      Assignment trigger:

      1. Ticket is created, assign togroup1
      2. Add tagtag_group1

      Remove tag trigger:

      If the ticket is updated and assigned to a different group (e.g.,group2), remove tag_group1, add a new tag of the newly assigned group (e.g.,tag_group2).This helps avoid assigning a follow-up ticket to the wrong group.

      Follow-up group assignment trigger:

      Conditions:

      Actions:Assign to the group.


      I highly suggest that you also upvote thisfeature requestand 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.
      1
    • Jamie Noell

      My workaround to this issue with Zendesk is that I created 2 hidden fields:

      • Saved Group
      • Saved Assignee

      然后,我使用一个webhook aut的JSONo-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.

      1
    • Jamie Noell
      • Edited

      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:

      • ClickView the original email- to read the message, but notifications with the ticket comment history sent when agent replies include the "jumbled" text that the client had sent. This does not look very professional.
      • Delay auto-closing the tickets, but this has reporting ramifications.

      I hope someone will have an update to share.

      0
    • Christine Felicia
      Zendesk Engineering
      Hi Jamie,

      We updated the ticket you raised with our support team related to this issue. Kindly check your email for more information. Thanks!
      0
    • Allen Lai | Head of CX, Otter.ai
      • Edited

      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:

      1. Zapier sees that a new ticket is created based on a previously closed ticket.
      2. [Filter] Only continue if the ticket contains a tag of "reassign_orig_assignee".
      3. Find the original ticket.
      4. Update the new ticket with the last assignee, last group, and add a private comment.
      0

    Pleasesign into leave a comment.

    Powered by Zendesk