Source system · Support
Sell your company's Zendesk ticket data for AI training
Outrich Data is a direct buyer of Zendesk ticket data from companies with 50 or more employees. Years of solved tickets, with replies, internal notes and satisfaction ratings, can often be licensed to AI labs after customer details are removed. Your admin exports the records. Outrich Data does not connect to your Zendesk account at any point.
What Zendesk holds that AI labs value
A Zendesk account stores each customer problem as a ticket: the first message, every public reply, the internal notes agents wrote to each other, status changes, tags, custom fields and the satisfaction rating at the end. Many accounts also hold help center articles, macros, chat transcripts and voice call records.
AI labs want tickets because each one is a problem paired with its resolution and a signal of whether the resolution worked. Internal notes are especially useful. They show the diagnosis the customer never saw: what the agent checked, what they ruled out and why they escalated.
Macros and help center articles tie tickets to the company's standard answers. A lab can see which article an agent used, how they adapted it and whether the customer came back. That supports training for support agents and evaluation sets built from real cases.
What a usable export looks like
Zendesk offers account data exports in JSON, CSV and XML from the admin center, and Zendesk states that data export availability depends on plan and may have to be enabled for the account. Comment bodies are not carried in every export format, so confirm that the format you choose includes the full conversation, or pull comments through the API. Exporting depends on your plan and admin role; check Zendesk's current documentation.
For large accounts the incremental export APIs return tickets, ticket events, users and organizations changed since a given time. That suits one historical pull followed by scheduled refreshes. Attachments are referenced by URL instead of being embedded, and help center articles come from the separate Help Center API. A usable dataset joins each ticket to its comments, its events and its rating.
Outrich Data does not connect to your Zendesk account, and it does not ask for credentials or an access token. Your company exports the agreed records itself, removes what is out of scope and approves the packaged dataset in writing before delivery.
Records and fields in a Zendesk dataset
| Record | Typical fields | Why it matters to AI labs |
|---|---|---|
| Tickets | Subject, description, status, priority, tags | The problem as the customer stated it |
| Public comments | Body, author role, timestamp | The conversation turn by turn |
| Internal notes | Body, author role, timestamp | Agent reasoning that never reached the customer |
| Ticket events | Field changed, old value, new value, time | Escalation and reassignment history |
| Satisfaction ratings | Score, comment | Outcome label for each resolution |
| Macros and articles | Title, body, usage | The standard answer agents started from |
Removed before licensing
What comes out of a Zendesk export first.
- Requester names, email addresses, phone numbers and postal addresses
- Organization names and account identifiers
- Attachments and inline screenshots
- Card numbers, bank details and government ID numbers typed into tickets
- Passwords, API keys and log excerpts that customers pasted
- Email signatures and people copied on the thread
- Tickets about legal threats, security reports or minors
Data title search
Rights and contract checks.
Vendor terms for business software generally treat the content a customer puts into the service as the customer organization's data. Read your own agreement with the vendor to confirm. That settles ownership between you and the vendor. It does not settle it with your employees, customers and partners, which is what these checks cover.
- Customer agreements. If your customers are businesses, their DPA or master agreement may limit you to using ticket content for providing the service.
- Privacy notice. If your customers are consumers, check whether your notice covers licensing to third parties and whether opt-out rights apply.
- Outsourced desks. If you run support for clients, those tickets are usually the client's data.
- Integration data. Order, billing or bug details synced in from other systems carry those systems' own restrictions.
- Voice records. Recorded calls attached to tickets need the recording consent review that any call recording does.
This page is general information, not legal advice. Whether your company can license a given dataset depends on your contracts, your privacy notices and the law where you and your customers are. Review it with your own counsel before signing anything.
Value
What moves the price of Zendesk data.
A written offer follows the rights review. The data valuation calculator gives an illustrative range first.
| Factor | Effect on value |
|---|---|
| Internal notes | Accounts where agents documented their reasoning are generally worth more than those with public replies only. |
| Outcome labels | Satisfaction ratings, reopen flags and resolution codes raise value. |
| Technical depth | Multi-step troubleshooting is scarcer than password resets and shipping questions. |
| Customer contract terms | Restrictive DPAs across most of the customer base shrink the licensable set. |
Related data types and industries
Questions
Selling Zendesk data: what companies ask.
Do our customers have to agree?
Are internal notes safe to include?
We moved to Zendesk from another help desk. Does old data count?
Does Outrich Data need an API token?
Zendesk is a trademark of its owner. Outrich Data is not affiliated with Zendesk.
Find out if your data qualifies.
Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.