How can I bulk delete spam tickets in Zendesk?

Question

My account was spammed and I now have all these tickets which I need to get rid of. Is there a way that I can bulk delete them without having to do it one by one?

Answer

There is no native way to bulk delete every single ticket from a large spam influx in a Zendesk Support account, in one go.

However, there are a couple of available options to delete more than one ticket at a time within Zendesk. Each option has its own set of limitations and choosing the best route is entirely based on your workflow and can vary for each use case.

• Bulk delete in views
• Bulk marking as spam 
• Bulk closing with an automation
• Bulk delete tickets via the API
• Zendesk Apps
• Install third-party apps from the Marketplace

Bulk delete in views

The first option to delete multiple tickets at a time is to use the bulk delete feature within views. Identify the spam tickets within your views and manually select each ticket you wish to delete.

Select the Delete option from the dropdown. This option is recommended if you have a relatively small number of spam tickets as you are only able to delete 100 tickets at a time. Tickets can be bulk-selected across pages.

Bulk marking as spam 

Important: If the spam tickets were created by submissions to your external contact form which is forwarded into Zendesk by email, do not use the Mark as spam option. This can cause an issue where you are flagging your own form submissions as spam, rather than the person who filled it in. In turn, this can lead to issues where this external form could always be seen as spam, or your email domain could even be on the blocklist.

Similar to how you can manually bulk delete tickets in views, you can also bulk mark the tickets as spam. Marking a ticket as spam in this way not only permanently deletes the ticket, but also suspends the requester, preventing them from being able to create further tickets. You will be able to mark up 100 tickets as spam at a time. Tickets can be bulk-selected across pages.

 

Bulk closing with an automation

The next option is to close spam tickets with an automation. Automations run hourly and can perform an action to close these tickets. Although this option doesn't delete the tickets, it places them into a closed status and removes them from your live ticket queues. The automation can also be configured to add a spam tag to the ticket, which can be leveraged to filter these spam tickets out of your reports, or to identify them later for deletion. Automations have limitations, so they can only act on up to 1,000 tickets during each hourly run. In the event that you have several thousand spam tickets, it may take a number of hours for those tickets to be closed. For example, if you had 30,000 spam tickets in your account, it takes a minimum of 30 automation cycles, or 30 hours, for the automation to completely remove these tickets.

The first step to setting up this automation is to determine a way to identify these spam tickets. This could be based on identifiers like a specific string in the description, a certain ticket creation timeframe, a specific requester language, etc. Oftentimes, there will be no single identifying feature between all of the spam tickets, so you would need to use a combination of different identifying conditions. These identifiers will then be used as conditions of the automation to help it determine which tickets to run on. Below is an example of how to configure an automation to close and tag tickets based on the presence of a particular string.

Meet all of the following conditions:

• Ticket: Hours since status category created | Greater than | 1
• Ticket: Status Category | Less than | Solved

Meet any of the following conditions:

• Ticket: Description | Contains the following string | (common string goes here)

Perform these actions:

• Ticket: Status Category | Closed
• Ticket: Set Tags | spam

In the example above, Ticket: Description is placed under Meet any of the following conditions, in case there are multiple strings that are used to identify spam tickets. You can add as many of these additional conditions as needed to ensure all of your spam tickets are addressed by a single automation.

Note: In accounts without custom ticket statuses enabled, use the Status conditions instead of Status category.

Bulk delete tickets via the API

Another option would be to utilize the Zendesk API to bulk delete tickets. Using this option means you are restricted to deleting 100 tickets at a time, however, if you have developer resources, the API can be leveraged in a script to run continuously in the background until all the spam tickets are deleted as well. For more information on using the API to bulk delete tickets, see Bulk Delete Tickets.

Disclaimer: This option is provided for instructional purposes only. Zendesk does not support the code needed to create the script. Please post any issues you have in the comments section or try searching for a solution online.

Zendesk Apps

"Built by Zendesk" released an App that allows for Bulk Delete of suspended tickets. This is the official app and an alternative to managing spam tickets. For more information about this app, see Bulk Delete App.

Install third-party apps from the Marketplace

Some third-party apps available in our Marketplace can help you delete or restore tickets in large scale. One example of those apps is the GDPR: Search & Destroy.

Disclaimer: This option is provided for instructional purposes only. Zendesk can't provide support for third-party apps. Reach out to the app developer's support email address under "App details" in the App Marketplace or try searching for a solution online.