Question

My account is receiving spam tickets. How can I prevent further spam and manage the existing tickets?

Answer

If your account receives spam tickets, first identify where the spam comes from and apply the appropriate prevention method. You can then use views, automations, the API, or third-party apps to manage or remove the spam tickets.

Note: Zendesk is unable to delete data on your behalf by the Data Recovery Policy.

Identify the source of the spam

Open a spam ticket and check the ticket events. If the ticket was submitted through a channel other than the web form, such as X or email, the channel details appear in the events.

This step helps you choose the appropriate prevention method.

Prevent spam from contact forms

CAPTCHA is turned on by default to help prevent spam attacks on your web form. To add another layer of protection, require end users to register and verify their email address before they can access the web form.

If your contact form forwards submissions to Zendesk by email, don't use the Mark as spam option on those tickets. This can cause Zendesk to treat your external form as spam or place your email domain on a blocklist. Use bulk delete or another cleanup method instead.

Prevent spam submitted through web services

To protect the request and uploads APIs, require authentication for API requests:

  1. In Admin Center, click People in the sidebar
  2. Select Configuration then End users
  3. In the Anybody can submit tickets section, turn on Require authentication for request and uploads APIs
  4. Click Save
Note: Authentication prevents anonymous ticket creation through sources such as the Web Widget contact form, custom apps, and external web forms. Confirm that these sources don't rely on anonymous submissions before turning on this setting.

For more information, see Managing end user settings.

Prevent spam content from reaching end users

Spammers may use notification triggers to send spam content to other users through ticket placeholders. Review your version of the Notify requester and CCs of received request trigger and remove references to {{ticket.title}} or other placeholders that render ticket content.

If the trigger doesn't already include it, add the condition Current user | Is | (end user). This prevents the trigger from sending spam content while preserving notifications for tickets created by agents.

This doesn't stop spam tickets from being created, but it prevents spammers from distributing their content to recipients.

Temporarily block spam domains

To block ticket creation from a domain or email address across channels, add the reject: modifier before the domain or address in your blocklist. For example:

reject:domain.com reject:name@gmail.com

Without the reject: modifier, the blocklist affects only domains received through the email channel.

Bulk delete in views

Delete multiple tickets at a time using 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 after selecting all the tickets in that view. This option is recommended if you have a relatively small number of spam tickets as you're able to delete only 100 tickets at a time. Tickets can be bulk-selected across pages.

Bulk mark tickets as spam

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

Marking a ticket as spam not only permanently deletes the ticket, but also suspends the requester, preventing them from being able to create further tickets. You can mark up to 100 tickets as spam at a time. Tickets can be bulk-selected across pages.

Bulk close with an automation

Automations run hourly and can act 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 add a spam tag to the ticket. If you have an Explore Professional or higher plan, you can use custom reports to filter the tagged spam tickets out of your reports or to identify them later for deletion. For more information, see Reporting with tags.

Automations can act on only up to 1,000 tickets during each hourly run. If you have several thousand spam tickets, it may take several 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.

To set up this automation:

  • Determine a way to identify these spam tickets, such as a specific string in the description, a certain ticket creation timeframe, or a specific requester language
  • If there isn't a single identifying feature among all the spam tickets, use a combination of different identifying conditions to help the automation 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:

  1. Create the automation
  2. Under Meet all of the following conditions, add Ticket: Hours since created | Greater than | 1 and Ticket: Status category | Less than | Solved
  3. Under Meet any of the following conditions, add Ticket: Description | Contains the following string | Enter common strings
  4. Under Perform these actions, add Ticket: Set tags | spam and Ticket: Status category | Closed
  5. Click Create automation

Automation setup to close spam tickets.png

In the example above, Ticket: Description is placed under Meet any of the following conditions, in case multiple strings 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 with custom ticket statuses deactivated, use the Status conditions instead of the Status category.

Bulk delete tickets through the API

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 doesn't support the code needed to create the script. Post any issues you have in the comments section or try searching for a solution online.

Install third-party apps from the Marketplace

Some third-party apps available in the Marketplace can help you delete or restore tickets on a 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.
Powered by Zendesk