Bulk Operations
Close, tag, prioritise, export, delete, or purge many tickets in one action from the dashboard
Bulk operations let you select several tickets on Tickets and apply one action to all of them: close, add or remove a tag, set a priority, export, delete, or purge. They are for clearing a backlog after an incident, tagging a batch of related tickets, or exporting a week's conversations without opening each ticket.
Anyone with dashboard access to a bot can run bulk actions on its tickets. Purge is the exception: only the bot owner can purge, and only tickets that were already deleted (their Discord channel or thread is gone).
Selecting tickets
Enter select mode
Go to Tickets, open the ⋯ menu (More actions) next to Filters and choose Select tickets. A checkbox appears on each row.
Pick the tickets
Tick individual tickets, or click Select all on this page to select every ticket on the current page (20 tickets). Use the Open, Closed, and All tabs, the search box, Filters, or a saved view first so the page shows exactly the tickets you mean. Changing the page, the tab, a filter, the search, or the order clears the selection.
Choose an action
The action bar appears with the selection count, for example "3 selected". On phones, Close tickets and Delete stay in view and the other actions are in the bar's ⋯ menu. Every action except Export opens a dialog that asks for any details and for confirmation before anything happens.
Review the result
When the operation finishes, a message tells you how many tickets were updated, how many failed, and how many were skipped. Click Done selecting to leave select mode.
Available actions
| Action | Input | Notes |
|---|---|---|
| Close tickets | Optional close reason, up to 1,000 characters | Follows each server's close settings (transcript, deletion, feedback). Tickets whose channel or thread was already deleted are skipped |
| Add tag | Tag name, 1 to 50 characters, letters, numbers, hyphens, and underscores. Pick a suggestion or type a new one | Added to every selected ticket |
| Remove tag | A tag picked from the tags on the selected tickets | Removed where present |
| Set priority | None, Low, Medium, High, or Urgent | Tickets whose channel or thread was deleted are skipped |
| Export | Format: PDF, HTML, JSON, or CSV | Downloads a zip containing one file per ticket. Starts as soon as you pick the format, with no dialog |
| Delete | Confirmation | Removes the tickets' Discord channels or threads and marks the tickets deleted; they stay in history with their transcripts until purged |
| Purge N from history | Confirmation | Permanently erases deleted tickets; bot owner only. The button only appears when the selection includes deleted tickets on a bot you own |
Tickets whose channel or thread was deleted are listed under the Closed tab.
Limits
| Limit | Value |
|---|---|
| Tickets you can select at once | 20, the tickets on the current page |
| Tickets per PDF export | 10 |
To act on more tickets, run the action page by page.
What happens
- Access is checked first. You must own or manage the bot of every selected ticket; if any ticket fails this check the whole batch is refused rather than partially applied.
- Tickets are processed a few at a time. Each one succeeds, fails, or is skipped independently, so one bad ticket does not stop the rest.
- Skipped tickets are counted in the result message. For Delete it reads "N ticket(s) were already deleted and were skipped"; for Purge it reads "N ticket(s) were skipped (not deleted, or on a bot you don't own)"; for Set priority it says how many deleted tickets were skipped. Before you confirm, the Delete and Purge dialogs already say how many selected tickets will be skipped.
- For Delete, open tickets are closed first and then deleted, so close-time behaviour such as transcripts still runs.
- For Export, the files are generated and delivered as a single zip download.
Purge cannot be undone. It removes the ticket record, stored messages and compressed history, transcript links, archived attachments, staff notes, SLA and feedback data, analytics contributions, and any knowledge base learning derived from those tickets. Export first if you might need any of it.
There is no bulk reopen, bulk assign, bulk claim, or move-to-category action. Reopening and claiming are done per ticket, with /reopen and /claim or the Reopen and Claim buttons on the ticket page.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The whole batch was refused | At least one selected ticket belongs to a bot you do not own or manage | Under Filters, set Bot or Your access so the selection only contains your tickets |
| Some tickets were "skipped" | They were already in the target state, or the action does not apply (for example purging a ticket that is not deleted) | The result message counts them; nothing else is needed |
| A thread ticket failed to delete | The bot lacks Manage Threads in its thread channel. The thread is archived instead and the ticket stays closed | Give the bot Manage Threads in that channel, then delete the ticket again |
| There is no Purge button | The selection has no deleted tickets on a bot you own. Dashboard staff never see it | Select tickets whose channel or thread was deleted (they are under Closed), or ask the bot owner to purge |
| PDF export is refused | More than 10 tickets were selected | Select 10 or fewer, or export as HTML, JSON, or CSV |
| Export fails on a large selection | The combined size or message count exceeded the export limits | Export fewer tickets per run |
| Select all on this page did not select every matching ticket | It selects only the current page of 20 | Run the action page by page |
| "Bulk PDF export is limited to 10 tickets per request." | Same as above | Reduce the selection |
Common questions
How many tickets can I close at once? Up to 20, the tickets on one page. On Tickets, choose Select tickets in the ⋯ menu, tick the tickets or click Select all on this page, choose Close tickets, add an optional reason, and confirm. Repeat page by page for more.
Can I export a whole week of tickets? Yes, one page (20 tickets) at a time, or 10 at a time for PDF. Set the Order and Bot under Filters, choose Select tickets in the ⋯ menu, click Select all on this page, and pick a format under Export. Each run downloads a zip.
Does bulk close send transcripts and feedback requests? Yes. Each ticket is closed the same way as a single close, so the server's close settings apply.
Why can't I purge? Purge is limited to the bot owner and to tickets that are already deleted. The Purge button only appears when your selection includes deleted tickets on a bot you own. Dashboard staff can delete but not purge.
Can I undo a bulk delete? No. Deleted tickets cannot be reopened. They stay in your history under the Closed tab, with their transcripts, until purged.
Can I bulk claim tickets or move them to another category? No. Those actions are per ticket in Discord or on the ticket page.
Join our Discord server for support
Was this page helpful?
Last updated on