Spawn new ticket from reply

Planned

Comments

226 comments

  • Official comment
    Avatar
    Max McCal

    Hey, everyone - 

    We understand there's a need here, and I do wish I had an answer that would resolve all of this for everyone, but unfortunately in the seven months since my last answer on this thread, we haven't had any changes. We still want to take on this feature, and we do plan to take it on, but at this time we aren't working on it. We have so many competing priorities and channels for customer feedback about our feature set. It's painful to make these decisions, and every day we're faced with hard choices. I feel the frustration from all of you here, and we will make our way back to this at some point. 

  • Avatar
    Renee

    I agree that this would be very useful.  We have a lot of users that send "oh one more thing" questions that are totally related to the initial incident and simply reply to the original ticket email.  Closing tickets after a certain period certainly helps reduce the number of these, but if someone replies promptly, the ticket will be re-opened.  We don't want to change our "close tickets marked solved after x days" automation to close tickets sooner.

  • Avatar
    Renee

    Sorry for the double post...I meant *totally unrelated*.

  • Avatar
    Joel Remigio

    I couldn't be more pleased with Zendesk. At first, the tricky part has been getting users to send help requests to a specific email address to auto-generate a ticket. But now that they are doing it, they are stacking multiple questions and help requests within a single message. Frankly, I'm just happy they are using the new address instead of personal addresses that force us to manually create tickets. So this feature would be helpful to us.

  • Avatar
    Morten Seifert

    I love Zendesk. Being able to split tickets would make me love it even more... and I agree with the point, that once you have convinced your users that it is much better to use Zendek and not personal e-mail, I don't want to nag them with "Please create a new ticket for your latest comment" og having to create the ticket manually.

    For the personal e-mail I have started forwarding them to the support mailbox and changing the originator, so atleast they get into the system.

  • Avatar
    Paul Keck

    +1 vote.

    Users rarely understand what should and should not be put in a single ticket. But why would they? They are the customer or client and it should be easy for them to tell me something is wrong. I spend a lot of time managing tickets, and this feature would be fantastic. The two biggest problems with the manual split is keeping the old ticket open and on track (because the last post was off topic), and adding attachments to the newly created ticket (download from old ticket, upload to new one).

    thanks in advance!

  • Avatar
    BrandonCaplan

    +1

    I have some users who find it easier to reply to the last email they receive from me, rather than start a new one (amending an unrelated ticket). This would be a useful addition in these situations.

  • Avatar
    Alan Wilson

    +1

  • Avatar
    Paul Alexander

    +1

  • Avatar
    Miles Muri

    +1 for me too.

    Miles

  • Avatar
    Jake Holman

    Paul Keck touched on an extremely good point. Splitting a Ticket is all very well, but then the End-User will invariably get confused about which Ticket to respond to if the conversation is still streaming in both Tickets (trust me, I've been there!).

    This would complicate things, perhaps more than simplifying things. In order to stop End-Users replying to old tickets, the aim should always be to Solve, and Close, Tickets as soon as possible.

    I welcome more discussion on this topic though.

    _Jake Holman
    _Zendesk Support

  • Avatar
    PaulAlexander

    After using Zen for a while I'd have to agree. Since closing the ticket generally forces the user to open a new ticket/new conversation it works pretty well. However there are a number of times when a user is in their "I'm pushing every button" mode sending emails for every little thing resulting in a muddled conversation. It would be nice to have some ability to split a ticket into different conversations. This is one of those cases where the technology can't solve the problem directly, but having the right tools can significantly enable the support people in doing their jobs.

  • Avatar
    BrandonCaplan

    I agree with Paul. As I mentioned further up, this would be most useful to me for those people who just reply to the last email you sent them to start a new conversation. This unfortunately tends to happen before the ticket goes from solved to closed.

    I alse agree with Jake's point that this could potentially confuse if used in the wrong scenario, but most of the time I am in need of this is when dealing with users who only interact with the helpdesk via email.

  • Avatar
    NickC

    Count me in too. My sales guys don't like to create fresh emails and keep reusing old emails so this would help.

  • Avatar
    Alan Conroy

    For us sometimes some one will have an open issue, like a bug to be sorted and then reply to the open ticket with a different query.

    We cut & paste the new query into a new ticket so that they have 2 open tickets however I'd like to be able to say that this response needs to be moved to a different ticket and leave the original ticket unaffected

  • Avatar
    Kathy Waller

    Yes please, change requests and bugs often come in together. +!

  • Avatar
    Dominic St-Jacques

    +1 for me too.

  • Avatar
    Alan Conroy

    I was thinking something like a tick box beside the response and then an additional option in the drop down menu, Move response to new ticket

  • Avatar
    Jason Wood

    +2

    I think this feature is already within the system - You have the option to "Create New Ticket" from a suspended ticket. Have this same functionality with all other tickets. This will give us to split a job (one part might be quick and another might take longer, so it will not muddy the data for the SLA's) or gives you the ability to split one part of the ticket off to one agent and the other part to another agent.

  • Avatar
    Bill Sapp

    I am very interested in seeing this as well.  Any confusion that would be caused is a small price to pay for the benefit; besides, that issue should be mitigatable by setting some general guidelines for your end users, even if you have to remind them every so often.

  • Avatar
    Stan Kutzko

    +1

  • Avatar
    Chris Wood

    +1

  • Avatar
    Ben Jones

    I'm into it. +1!

  • Avatar
    Will Sharp

    This topic came up today in our staff meeting. It seems like there would be 2 use cases (for our purposes):

    1) Ability to split the ticket with the last comment from the original tx being the 'description' in the new tx. New ticket would be created with the last comment being inserted into the new tx, all the fields and tags and requester being set the same as the original, new tx not submitted yet so that you could edit the comment, tags, fields, etc.

    2) Ability to create a new ticket from the last comment and reset the original ticket back to its state before the last comment was added. New ticket would be created with the last comment being inserted into the new tx, all the fields and tags and requester being set the same as the original, new tx not submitted yet so that you could edit the comment, tags, fields, etc.

    This functionality would be very handy.

  • Avatar
    Ed Wiancko

    We would like this feature also.  We do this manually now and would benefit from this feature a lot - especially if the any attachments to the new comment could be brought to the new ticket automatically.  (Currently we have to download each one to a local spot, then upload each one.  Pain!)

    Yes, occasionally we will have a client that gets confused and replies to the wrong thread, but that doesn't happen often.  Clients are usually very good at replying to the right string in my experience.

  • Avatar
    Lynda Mota

    Our requests sometimes include two elements that need to be performed by different people. Currently we ask people to create two separate tickets so that there is a separate job ticket for each of the tasks, but sometimes they don't realize they're separate tasks. It would be great if either the Admin or the Requester could duplicate the original request when they create it, OR as Will suggested that when one part is closed a new ticket could be created and reassigned to another person.

  • Avatar
    Sherry Levy

    I have a question about duplicating /splitting a ticket? Let's say "John" sends in a ticket to the system and it comes to me and it reads I need the (Brown) website to be updated by 3: 00 pm today with new graphics, and two new fields that need to be programmed in addition I need to do Search Engine optimization.

    Would I be able to duplicate/split ticket the ticket "with the exact information and attachments" (the original ticket info from John) and then send it off to Bob the Programmer, Paul the Graphic Designer and Jane the Search Engine Optimizer? Essentially creating three new tickets in the system.

    Thank you,

  • Avatar
    Chris Kittinger

    This would be a great feature to add.  Clients often reply to existing tickets when asking about a new request or topic.

  • Avatar
    JoeBrenner

    +1

    Had a need for this (again) today. User replied to a previous thread, which was actually Solved but not Closed, with a totally unrelated topic.

    Creating the new ticket manually was awkward and I actually had to do this twice because, the first time, Zendesk failed to recognize the Requester Name I entered (it offered no suggestions) and assigned me as the Requester instead. So I had to delete that ticket and try again.

    Luckily, the user forgot a file they wanted to attach to the request. Otherwise I'd have to download it and then upload it again to the new ticket (twice!).

    What I want, as others have commented above, is an option, in the usual drop-down, to "Create new ticket from last comment". This would copy the description, tags and attachments to the new ticket, and assign the correct requester. The new ticket should be left open so I can add a suitable Subject.

    Ideally, when the new ticket is submitted, and the requester is informed, the rogue comment in the original thread should be deleted, but I realize this might be tricky and cause 'data integrity' issues so it would be okay to leave it there and simply ignore it. Alternatively, a private comment could automatically be added to indicate that the last comment was moved to a new ticket and include the ticket link.

    Thanks, Joe

  • Avatar
    JoeBrenner

    Wow, what happened to all the separate paragraphs in my last comment? And why did I end up in a weird place afterwards? I see there's been some Zendesk tweaks since I last commented...

Please sign in to leave a comment.

Powered by Zendesk