Creating a follow-up for a closed ticket Follow


Creating a follow-up for a closed ticket

Once a ticket is closed, it cannot be altered or reopened. However, both the requester and you can create a follow-up request. This creates a new ticket that references the closed ticket and also pulls all of the original ticket data into the new ticket.

The channel for follow-up tickets is Closed ticket.

To create a follow-up for a closed ticket

  1. Locate the closed ticket that you want to create a follow-up for. You can do this by locating the requester first and then selecting one of their closed tickets, by searching for the ticket number, or by creating a view for closed tickets and locating the ticket there.
  2. When you view a closed ticket, you'll see the option to create a follow-up ticket.

  3. Click Create follow-up.

    A new ticket is created that contains the same data as the original ticket.

  4. Update the ticket data as needed and then click Submit to save the new ticket. The requester will receive an email notification for the new ticket. The new ticket is marked as a follow-up, as shown here:

Have more questions? Submit a request


  • 0

    Hi Zendesk.

    If i create a follow-up to a ticket, does that mean that the closed ticket - that is used in some custom statistics - will be overruled by the follow-up?
    Eg. i have added a "serial number" field since this ticket was closed. I want to follow up, add serial number and solve. But i don't want both the follow-up and the original ticket that i now closed, to appear in my statistics since they are the same case. :)

  • 0

    Hello - if I have all end users of an organization set up to view each other's tickets, can an organization end user create a follow-up of another end user's ticket?

    If RequesterA creates the original ticket, can RequesterB create a follow-up?

  • 0

    Hi Sebastian!

    I wouldn't say "overruled". Once a ticket has been Closed, it can't be modified in anyway, so when a follow-up ticket is created it's a completely new ticket. The ticket field information is brought over from the original ticket, but it will count as a second ticket.

    For the use case you're describing, you'll either need to just add the serial number to your tickets going forward, or create follow-up tickets and exclude the original tickets from your reporting.

  • 0

    Thanks for the clarification.
    So how would you omit the original ticket from the reporting, and only have the follow-up data included?

  • 0

    Btw. It would be so much easier to give the option to Re-open the old ticket from the Closed state.
    I understand why you close them, i've read somewhere else it's due performance of the platform, but still - allowing your teams to reopen a case would be great, as a follow-up is something different.

  • 0

    Hey Sebastian!

    The first thing to bear in mind is that if you're doing any time-based reporting (ie: last seven days, etc), creating follow-up tickets to add the serial number may throw off your numbers, since those tickets were created after the original ticket.

    If you're using a single line custom text field, you can just create or modify a report to include tickets that have information in that custom field. Once the custom field has been created and tickets exist that have information in that field, and your Insights project has had time to sync up, you'll see that custom field listed as an option when you edit/build the report.

    Another option would be to just exclude all closed tickets from the report.

    Hope that helps!

  • 0

    Is there any way to create a trigger which will email the assignee of the original ticket when a follow-up is created? I can't think of a way this could be achieved, but perhaps someone here has ideas.

  • 0

    @Kathryn. If you only have a few agents, perhaps 20 at most, then you could use triggers to add tags to the tickets as they are assigned to agents (removing any previous related tags at the same time). When a follow on ticket is created that tag would still be in place so you can use that to reassign the ticket.

  • 0

    @Colin Thanks for the suggestion!

  • 0

    Hi Heather!

    Thank you for your patience! We did some testing here to see if we could have
    Requester A create the original ticket, and then have Requester B create a follow-up. It does not appear that this is possible. Requester B can request to create a follow-up, but it will actually create a new ticket instead.

    I'm sorry I do not have better news for you on this one! If you have further questions, please don't hesitate to reach out to us!

  • 0



    Is it possible to send me what was sent to Nina re: preserving all ticket fields on the follow-up ticket from the original?



  • 0

    Hi Abbey!

    I checked Nina's ticket, and the advocate confirmed that it's not possible to preserve all ticket fields when a follow-up ticket is created. We do have a conversation about this in our Product Feedback forum, which you can find here: Follow up tickets should have inheritance from the original ticket's custom fields.

    There hasn't been any recent activity, but I'd encourage you to add your vote and use case to the conversation. Our Product Managers see each comment on those posts, and we take customer feedback into consideration as we work to improve Zendesk.

    Please let me know if you have any other questions!

  • 3


    Is there a way that you can amend a ticket so that it isn't a follow-up??  We have multiple users that raise tickets as a 'follow-up' when in fact they are not.  They have been advised on how to raise tickets but yet they come through as 'follow-up' tickets.

    Hope you can help.



  • 0

    We have the same issue as Sharon - I have no idea why people do this, but anyway, we want all customer-initiated follow-ups to start afresh like regular tickets. 


    Any way to do this?

  • 0

    We have found the same issue as Sharon and though many users will follow our directions to delete ticket-specific emails or suggested contacts in their email client, we still get a few users that just don't "get it". 

    I would love a workaround for those handful of users that continue to open unrelated followups, which hopefully will remain a low percentage.

  • 0

    Hi James and Heather

    I raised my request as a support ticket as Zendesk haven't updated the above thread since April 2016..

    Although, their response doesn't help me I thought it may help you:

    "While it's not possible to completely disable follow-up tickets, you can send a message to the requester when they reply to a closed ticket  by creating a trigger.

    You could let the customer know for future reference to raise a brand new ticket if it's a separate issue. I've also taken a look in our Product Feedback discussions but was unable to find an existing discussion about disabling follow-up tickets. Since that forum is the primary channel used by our Product Management team and other Zendesk users to discuss possible new features and suggest workarounds, I highly encourage you to post your request there. I also recommend subscribing to the article so you'll be updated of any further comments. We truly value customer feedback and your voice and votes in the forums help influence future Zendesk functionality."

    I've raised a request here:

    Hope that helps  ;o)

  • 0

    I have a concern with how ZenDesk is looking at emails and considering it as a "follow-up" to a closed ticket. This creates potential privacy issue where internal staff communication are being shown to the customer. 

    When a customer sends a support request we get a copy in our Outlook but our agents respond from the Zendesk panel. Now, one of the agents took the ticket and forwarded to other department, from inside Outlook, and he had changed the email subject line and removed ALL recipients then added the new recipients. Today, one of the recipients mentioned this is a serious privacy concern because recipients response actually triggered Zendesk to create a "follow-up" ticket which means original requester received a copy as well, even though the email subject is different and original requester nor the unique ticket identifier are on the TO/CC line.

    Is there an invisible tag that is stuck to a ticket once issued? If our agents need to communicate with other departments who aren't on zendesk are they to do that by attaching the zendesk ticket as an attachment rather than forward? 

    Thanks in advance.

  • 0

    Hi Andy!

    There's content inside the email header that helps determine whether an email should be made into a follow-up ticket in Zendesk.

    I'd like some clarification on your workflow here. Why are your agents forwarding that email from Outlook after the ticket has been Solved and moved to Closed status? There could be another solution that will work better for your purposes here.

  • 0

    @Jessie Schutz

    We have integrated zendesk for some time now but many of our customers are still sending emails to personal email rather than our "" address hence sometimes there is a need to forward. 

    In the case I had mentioned before, the ticket itself had been resolved but one of our agents took an outlook copy of the ticket and removed all TO/CC leaving just the new recipient then forwarded it to our sales team to follow up on a sales opportunity but when the sales team responds back it somehow triggered an update to the ticket hence our customer received a copy of the email that could have had confidential information.  Is the header information a hidden property of an email?

Please sign in to leave a comment.

Powered by Zendesk