Skip to main content
Export tickets from the Chatbase Helpdesk to a CSV file to report on them in a spreadsheet or move them to another tool. You can export a whole view or a selection of tickets, on any plan that includes the Helpdesk. The file has one row per ticket with its details, dates and response times. It leaves out message text. Owners and Members can export. Support Associates and Viewers do not see the export buttons. Export is controlled by its own permission, shown as Helpdesk · Export on the Members page, so permission to edit tickets doesn’t include it. Without it, the Export buttons are hidden.

Export a view

Click Export next to the Filter button. The file has the same tickets in the same order as the list, so it follows the view’s conditions, any filters you added and the current sort. Filters you haven’t saved as a view count too. An export holds at most 10,000 tickets. When the list has more, the button reads Export first 10000 and you get the first 10,000 in the current sort. To get the rest, change the sort or narrow the filters and export again.
Ticket list header with the export button next to the filter button, its tooltip open over the column headers
You can’t export search results. Use filters to find the same tickets, then export.

Export selected tickets

Select tickets with the checkboxes, then click Export in the bar that appears. This works for up to 50 tickets at a time.
Two selected tickets in the list and the action bar showing 2 selected with Edit and Export buttons
You can start one export per minute. Each file is called tickets-<date>.csv.

File format

The file is UTF-8 with a byte order mark (BOM) and Windows (CRLF) line endings, so Excel reads accented and non-Latin characters correctly when you open it. There is no scheduled or automatic export. Exports run only when someone clicks Export.

Columns

After these, each custom field on the AI agent gets its own column, named after the field. Archived fields are included. Dropdown fields show the option’s label.

Merged tickets in an export

A merged ticket appears as its own row, with the closed status it got from the merge and its own tags, custom fields, requester and message counts. There is no column that marks a merge. The kept ticket’s Agent messages and Customer messages counts don’t include the merged ticket’s messages.

Recurring reports with the API

For a daily or weekly report, use the List tickets endpoint instead of exporting by hand. It needs the helpdesk_tickets:read scope and filters by status, channel, assigneeId, teamId, priority, createdAfter and createdBefore. Results come in pages of up to 50 tickets with a cursor. It has no tag filter. For a poller, sort with sortBy=updatedAt&order=asc and keep the last updatedAt you processed.

Frequently asked questions

Up to 10,000 tickets from a view, in the current sort, or up to 50 selected tickets. Each person can start one export per minute.
Yes. The file is UTF-8 with a BOM, which Excel uses to read accented and non-Latin characters correctly.
Export needs the Helpdesk · Export permission, which is separate from permission to edit tickets. Ask a workspace owner to check your role.
No. Export is on demand only. For recurring reports, pull tickets from the List tickets API endpoint on a schedule.
The Channel column holds each channel’s system name, such as iframe for the Chat Bubble or helpdesk for tickets your team created, not the label shown in the inbox.
Yes. The Tags column lists each ticket’s tags separated by ; , so you can count them in a spreadsheet. For a quick count without exporting, save a view filtered on the tag and read its count in the sidebar.