Skip to content

Customer support

Find and export
your Zendesk data.

Zendesk ticket counts describe cases, while comments and attachments supply the conversation behind them. Export format and account permissions affect how much of that history is collected.

Report in
Records
Category
Customer support
Last checked

Find your Zendesk data size

  1. With reporting access, create an Explore report using Support → Tickets and the ticket-count metric.
  2. Set dates to cover the retained account history.
  3. Without the report, ask an administrator or developer to use the Tickets Count API.
  4. Record the count, date window and whether the API marks the result approximate.
Ticket visibility and reporting permissions affect the count. Keep deleted or excluded ticket categories identified separately.

What to include in your data inventory

Report in records, with ticket count and years covered. Describe public replies, internal notes, attachments and help-center content available.

Include the agents represented and use the oldest retained ticket date. State any exclusions in the count.

Add the dates covered and the people who use this software. Label estimates and describe how you calculated them.

Export your Zendesk history

  1. Ask the account owner to confirm export entitlement and enablement with Zendesk support.
  2. As an admin, open Admin Center → Account → Tools → Reports → Export.
  3. Choose the JSON ticket export and the required date range, then download the completed archives.
  4. Collect attachment files through their authorized links or API route and preserve the ticket relationships.

The JSON export uses NDJSON, meaning one structured JSON record per line. A CSV omits conversation content that can be essential to the dataset.

Check the export's omission reports: very large tickets can have comments excluded. Attachment links also need separate download and access checks.

Why Zendesk data has value for AI training

Support threads can show how an issue is described, investigated and resolved.

Internal notes and ticket context can explain the reasoning behind an agent's response.

What stays private

Choose the tickets, comments and attachments in scope, reviewing customer identifiers and sensitive support content.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.

Common questions about Zendesk data

Does CSV preserve the conversation?

Use the JSON route when comment history is required. Check the fields provided by a CSV separately.

What does NDJSON mean?

It is a text file with one JSON record on each line, suitable for processing a large export incrementally.

Are attachments downloaded with the ticket file?

Plan collection of actual attachment files separately from their references.

Why is the export option absent?

Ask the owner to check plan entitlement and whether Zendesk support has enabled account exports.

Your data inventory

Add your numbers to the picture.

Enter the quantities and years covered in your data inventory, then share it with your Telegraph Lab contact. We’ll review the material and discuss the next step with you.

Discuss your data