Recent searches
No recent searches
Disable / Un-check 'Create follow-up' option
Posted Feb 02, 2017
Hi
Is there a way that you can amend a ticket so that it isn't a follow-up?? For example, is there an option so that we can disable follow-up or select un-follow? We have multiple users that raise tickets as a 'follow-up' when in fact they are not related to their original ticket at all.
Our customers have been advised on how to raise tickets but yet they come through as 'follow-up' tickets. As I couldn't find any responses on the Forums - I raised a ticket however Zendesk support have suggested adding my query here. Hope you can help!
Thanks,
Sharon
65
78
78 comments
Dave Dyson
0
Luis Pagan
Morten's workaround technically works, so thank you Morten for that - I have used your recommendation. However, it is not a great customer experience. It causes a lot of customer confusion, because a new ticket is still created and then closed automatically via the workaround. So the initial reply a customer still receives is that a new ticket number was created, then moments later they will receive the message about creating a new ticket instead. It can cause a confusing loop for the customer. Especially if they are not constantly monitoring their email and have 100s of emails they sift through daily. 95% of customers will get it, but 5% will see this as a pain.
Zendesk the best solution will be a feature that sends them a message automatically informing them about the new ticket rejection without a new ticket generating all together..
0
John Meyer
I recently realized that I accidentally eliminated this problem when I connected an external address as the primary email address on this page: https://COMPANY.zendesk.com/admin/channels/talk_and_email/email
When I previously forwarded emails from support@company.com to support@company.zendesk.com, tickets would generate an email address like support+123456@company.zendesk.com. Employees would use the autofill in Outlook and email a specific ticket instead of support@company.com, causing this issue.
Now that I have connected the address, all email from Zendesk comes from support@company.com and the ticket is tracked via code in the ticket itself. So now the only email that hits autofill is the correct support@company.com, and this problem has vanished for us over time.
The only time I ever see this issue is if someone finds an old email and hits reply to report a new issue, but that is rare. I have left the trigger in place that auto-closes tickets that I previously posted (just about the same as Morten's) for employees that have very old autofill data.
0
Luis Pagan
Thanks John for that note. I believe we would still encounter an issue if a customer creates a ticket via web widget, and saves the reply support+12345 email address. If they email support+12345 after a ticket has been closed a follow up would be created in that situation.
0
John Meyer
I just created a ticket via web widget and the email was from support@company.com. It did not create the support+123456@ email address. I don't believe it will create the unique email address if you are using an externally connected address, shown below.
And here is a screenshot showing how it is not unique any longer:
0
Luis Pagan
Thanks for the help John! This is helpful. I will use your suggestion and test it out.
0
Phil Chamney
We too need to disable follow ups. Many customers just look for the last email they sent to us and reply. It's usually a new order or inquiry unrelated to the closed ticket.
Zendesk, just allow us to turn off follow ups in the admin panel.
0
Steven Hampson
I agree, this really needs to be fixed - our company is a B2B company and so we have literally thousands of customers who can contact us. And people keep old emails. Training our customers is not going to be a solution.
We can close the new tickets with a trigger but as Luis said, that means they get conflicting email notifications which is confusing to customers.
My question however is - does this impact on reporting for agent work time or requester wait time? i.e. if a customer replies to an old email after 5 weeks (or 5 months...) Does it calculate as a separate ticket, or does the work time on the original update to 5 weeks / months etc.? This will seriously impact our SLA reporting which has financial penalties for us, so I really need to know how that works.
Thanks!
0
Sydney Neubauer
+1 We have it where there is a single ticket, it will close and then the requester and CC will have a conversation and every single reply opens up a new ticket. As you can imagine, this creates 10+ tickets and a lot of work for our agents to merge the tickets together.
If we could unlink the follow ups, it would atleast help.
0
Jordan Moore
THIS ISSUE HAS BEEN OPEN FOR 6 YEARS!!
How do we turn off follow-up tickets. WE DO NOT WANT IT TURNED ON.
It's as simple as that.
4
Kai B
Hello - I think my issue is slightly different here but I would also like some more control over Follow-up tickets
There needs to be more granularity and options in the permissions here I think to allow for organisations to manage responses to closed tickets in the way that they see as necessary to their business.
0
Eric W.
The "follow up ticket" is a major issue for my organization. Our agents solve extremely complex issues and customers will use the follow up option for issues that are not related to the original ticket, expecting an immediate follow-up to an incorrectly routed ticket- and sometimes the customer requests are urgent in nature. This function has created serious confusion and often anger at our support agents since we already struggle with organizational response time. Being able to disable this feature would be a massive weight off our support team by reducing the number of lost/incorrectly routed tickets.
1
Hannah Lucid
+1 for this. Definitely a challenge.
Case: Agent solve the original ticket. This email address for the ticket (support@org.zendesk.com+1234567) stays in their email directory. They either find the last response on the ticket or type "Zendesk" or "support" in the to field and send their new request, creating a follow-up ticket that is not related.
Solve: Allow organizations to turn off "create follow-up tickets".
Additional ask: Is there a way to have the original ticket copied on the follow-up? I know they link the tickets together, but for Organizations that use custom roles, when you don't allow agents in a specific group to see tickets for another group, it presents a challenge when follow-up tickets are created since the follow-up ticket group cannot see the original ticket.
0
Ashley M
+1 this needs to be an option in the system or at the very least add conditions
1
Jordan Moore
WHYYYYYYYYYYYYYYYYYYYYYY Can Zendesk not address customer requests. People have been asking for you to have an option to disable Follow-Ups since 2017 on here (SIX YEARS). It has caused a major mess in our database. We're seriously about to pull our contract from you all for lack of responsiveness. You dev team does absolutely nothing.
2
Lukáš Kuzník
Dear ZenDesk support,
please fix this issue.
There are 2 updates we need :
1. give us possibility to generally turn off option
2. give us possibility to unlink follow up tickets for companies who wants to continue with follow up function
Thanks in advance
Lukáš
0
Gaurav Parbat
Hello all,
We understand the need for this enhancement. This means that we will think about adding it as a priority later in our planning cycle for 2025. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community.
0
Lukáš Kuzník
Dear Gaurav Parbat
thank you for your feedback.
the issue is opened from 2017 in this chain and maybe even older chain exist - means that this is not one piece of feedback but the general issue already for more than 7 years
the main problem for us is that users created follow-up cases by mistake (they overlooked the different email address) are sharing sensitive data related to a new support case with users involved in previous case (followed one) - and this is a BIG SECURITY ISSUE which should be fixed immediatelly as a hot-fix and not “maybe” in 2025 !
thanks for understanding
Lukas
0