Can a ticket have multiple assignees at one time? Follow

Comments

9 comments

  • Avatar
    Gary Tam

    This is not a good solution because a ticket can have many permutations of different technicians working on a ticket.  For a company with 20 techs, it is not a reasonable solution to create an agent group every time multiple different techs work on a ticket.  

  • Avatar
    Jessie Schutz

    Hey Gary,

    Is there a reason that you can't just have one group with all your techs in it and assign your tickets to that group? This would be the easiest way to handle your use case as I understand it.

  • Avatar
    Susan Maher

    There are different reasons why we may need more than a person responsible for the ticket.  For example if the ticket gets worked by Customer Care and Development.  In this case we need an Owner (always in Customer Care) and an assignee (person actually working on the ticket). 

  • Avatar
    Rox Wong

    It would be great if this can be possible.  There are times when we have a request that involves multiple tasks, but can only be action by more than one individuals based on their skills.

    For example:

    A request (e.g. - add new library database) comes in that requires the following to be action:

    • One person to add a new database on proxy server
    • One person to publish the new databases on the library website
    • Once the above tasks have been completed and tested, one person to send out the communication to the community and organisation about the new database

    The above involves at least 3 different people working on the one request.

    At the moment, we are using the split ticket options and as per the above, we had to split at least twice (3 tickets in total) to complete the one request.  The reason for this is capture the time spent on tickets per assignee for management statistics purposes. The only way to do this is to split the ticket and assign it to each individual.  The cons about this splitting method is there might be some importation information that are on the child ticket that other assignees may not be aware of.

    If someone could provide some feedback or tips on how to better handle our process, it would be greatly appreciated.  If it helps, we are currently on the Team edition.

    Thanks!

     

  • Avatar
    Jessie Schutz

    Hi Susan!

    Can you tell me the difference between the ticket owner and the person actually working on the ticket? Why do you need to make that distinction?

    I ask because I'm hoping to understand your use case a little bit better. :)

  • Avatar
    Jessie Schutz

    Hi Rox!

    Is there a reason why you can't have an agent re-assign the ticket to the next team once they've completed their task?

  • Avatar
    Jonathan March

    We have a custom dropdown field for secondary attention by a single other agent. You could alternatively make this a multi-select field. It takes some extra triggers to have them notified when desired, and you won't get the Insights reporting that you might want, but at least it keeps the record clear and the notifications in order.

  • Avatar
    Rox Wong

    Hi Jessie,

    All agents in Zendesk are basically the same team but without different skillsets.

    The main reason is that we need to be able to record statistics for each agent.  If we re-assign the ticket to another agent, then the previous agents who have done work on it will not receive the credit.  Ideally, we would like to be able to record all work managed by agents.  My preference is not to use the split ticket option, but to be able to re-assign the one ticket to other agents, but to be able to have my work recorded in the system to be able to report to management. Unfortunately, this is not the case at the moment.

    Thanks,

    Rox

  • Avatar
    Rox Wong

    Hi Jonathan,

    Appreciate your feedback.  Unfortunately, like I mentioned in my last comment, all work needs to be tracked on Zendesk.  This is to allow management to know if our team require more resources to assist us or to ensure future workloads are considered carefully without overloading all agents.

    Thanks,

    Rox

Please sign in to leave a comment.

Powered by Zendesk