- The ticket is deleted and moved to the Deleted tickets view for 30 days until it is permanently deleted.
- The ticket requester is suspended and cannot submit or access tickets, or access your Help Center.
To recover a deleted ticket, you can restore it from the Deleted tickets view (see Restoring a deleted ticket) , and unsuspend the user (see Suspending a user). Any further tickets that the suspended user submits are added to the Suspended tickets view where you can review them (see Understanding and managing suspended tickets and spam).
You can also mark multiple tickets as spam at the same time. See Bulk marking tickets as spam and suspending the requesters.
To mark a ticket as spam and suspend the requester:
- Open the ticket you want to mark as spam.
- Click the Ticket options menu in the upper right, then select Mark as spam.
You will only see this option on tickets where the requester is an end-user.
- Click Immediately mark as spam to confirm that you want to continue.
The ticket will be deleted and cannot be recovered. The requester will be suspended. Alternatively you can click Cancel.
Reporting on tickets marked as spam
You can't run report on spam tickets. Additionally, some companies may not want to use the Mark as spam feature, for example, regulated companies.
As a workaround, you can have your agents add a tag that indicates the ticket is spam before clicking Mark as spam. You can then use that information to generate reports on tags. For more information, see Reporting with tags (Explore) and Reporting on ticket tags (Insights).
To report on tickets marked as spam
- Create a custom ticket field called Spam (or whatever you choose to call the custom field) to check tickets that are considered to be spam.
- Create a macro that automatically checks the field Spam and then routes the tickets to a certain group or agent.
- Train your agents to use this macro when they spot spam tickets.
- Once a week or a month, have an agent or a group of agents checking the queue to ensure no tickets are categorized incorrectly.
You can then use the custom ticket field to run reports on these tickets.