Updated
For teams with a help desk
Sell Support Ticket Data to AI Companies
Short answer
Yes. An AI company pays to learn from a copy of your solved help desk tickets, and the originals stay yours. Each solved ticket shows a real problem and the fix that worked, which is why buyers want them. Customer names and details get taken out.
To sell support ticket data to AI companies, you let a buyer copy your solved help desk tickets. You do this under a license. That means the buyer pays for the right to work with a copy. The originals stay yours. Each ticket shows a customer problem and the steps your team took to fix it. AI labs value this because a solved ticket is a full lesson. It has a question, the back and forth, and an answer that worked.
This page covers which tickets buyers want. It shows how to export them from Zendesk, Freshdesk, Intercom and Help Scout. It explains how customer details get removed. It also shows why your saved replies and help articles add value. The estimate below takes two minutes and asks for no logins.
- Customer details removed
- Solved tickets only
- Program covers the referral fee
Why tickets
Why is a solved ticket worth more than an open one?
A support ticket has a shape AI makers love. It starts with a real person who describes a problem in their own words, often badly. Then an agent asks questions and tries something. The agent may check a log or a setting. Finally, the agent writes the fix.
When the ticket is marked solved, you know the ending worked. That makes it a tested example, not a guess. Open or dropped tickets show the problem but not the answer. So they are worth far less. Solved tickets with several replies are worth the most, because they show the thinking in between.
Internal notes add even more. These are private notes agents leave for each other inside a ticket. They show why a case went to engineering. They also show what the real cause turned out to be.
The labels your team added over the years help too. Tags, categories, priority, product area and satisfaction scores all count. They tell a buyer what each ticket is about. They also show whether the customer was happy at the end. Few public sources are sorted this well.
Tickets are one record type among many. Our sell data to AI companies hub explains the others.
What qualifies
Which help desk records do buyers license?
Most of this sits in one help desk tool. A few pieces may sit in a bug tracker or a shared drive.
| Record | Where it usually lives | Why AI companies want it |
|---|---|---|
| Solved tickets with the full thread | Zendesk, Freshdesk, Help Scout, Intercom, Jira Service Management | A real problem, the questions asked and the fix that worked |
| Internal notes | Private notes inside each ticket | What agents tell each other but never tell the customer |
| Tags, categories and priority | Ticket fields and custom fields | Labels that sort thousands of cases by topic and how urgent they are |
| Satisfaction ratings and comments | Customer happiness (CSAT) surveys in the help desk | Shows which answers customers liked and which fell flat |
| Cases sent up to engineering | Linked Jira issues or bug reports | How support hands a hard case to the people who built the product |
| Macros and saved replies | Macros in Zendesk, canned responses in Freshdesk, saved replies in Help Scout | Your team's best tested answers to the most common questions |
| Help center articles | Zendesk Guide, Freshdesk Solutions, Help Scout Docs, Intercom articles | Clear, approved explanations by people who know the product |
Export
How do you export tickets from the major help desks?
Each tool has its own way to export. In most of them, the CSV option leaves out the conversation itself. Some tools need an API for full threads. An API lets software pull data straight out of a tool. These facts come from each company's own help pages. Your admin or IT person runs the export. The buyer tells you which format it needs.
| Help desk | Built-in export | What to know |
|---|---|---|
| Zendesk | JSON, CSV or XML from the admin settings. You need a Professional or Enterprise Support plan, or Growth and above on Suite plans (Zendesk guide). | Exports start out turned off. The account owner asks Zendesk Support to turn them on. CSV leaves out ticket comments, so JSON is the format to use. The download link lasts at least three days. |
| Freshdesk | Admin, then Account, then Account Details, then Export data (Freshdesk guide) | Only an account admin can run it. The export comes as an XML file. It holds tickets, solution articles, forums and the customer list. |
| Intercom | CSV views and datasets, or one conversation at a time as PDF or text. You can also use the Conversations API or a JSON export to Amazon S3 (Intercom guide). | Intercom says its CSV exports hold report data, not the message text. It says S3 files leave out the transcript too. Full conversations come out through the Conversations API or as PDF or text from the inbox. |
| Help Scout | CSV or XLSX report exports, plus the Inbox API and Docs API (Help Scout guide) | Report exports skip the conversation threads. Threads come out through the Inbox API. Help articles come out through the Docs API. |
Customer privacy
What the buyer removes, and what you keep out
Tickets are full of customer names, emails and order numbers. Buyers scrub those details before any training. You can usually look over a cleaned sample. But scrubbers still miss things now and then. So some tickets should never go in the copy at all. The license lists every item you keep out.
Names and contact details
The buyer strips customer names, email addresses, phone numbers, street addresses and account IDs. Agent names in signatures come out the same way.
Payment details and passwords
Customers sometimes paste card numbers, bank details or passwords into a ticket. Before export, filter out tickets tagged billing or payment. Also remove any you know hold this kind of detail.
Health, legal and other sensitive topics
Some customers describe health problems, legal trouble or something similar. Leave those queues or categories out. Some industries have their own legal rules, so bring in your lawyer.
Clients with strict contracts
Business customers sometimes sign agreements that limit how you use their information. Read those contracts. Leave out the tickets they cover.
Attachments and screenshots
Screenshots and uploaded files can show account pages, IDs or other people's data. Most owners license the ticket text and leave attachments out.
Promises in your privacy policy
Read what your privacy policy and customer terms say about support messages. If they promise a narrow use, ask your lawyer before you license tickets.
Tickets tied to disputes
Some tickets involve chargebacks or complaints that turned into legal claims. Others are under a legal hold, which means you must keep them as they are for a lawsuit. Keep all of these out until your lawyer clears them.
Bonus content
Saved replies and help articles your company already owns
Tickets are the main draw. But your team also wrote a library of tested answers. Your staff created it, and it rarely holds any customer data. Buyers value how clean it is.
Macros and saved replies
A macro is a saved reply an agent can send with one click. These are your best answers, polished over years of use. In Zendesk, your IT person can pull them through the Macros API. Paired with tickets, they show how agents adjust a template for each customer.
Help center articles
Zendesk explains how to back up a knowledge base with its Help Center API. Freshdesk puts solution articles in its account export. Help Scout releases Docs articles through its Docs API.
Old versions and retired articles
Drafts and archived articles show how your answers improved as the product changed. Your public site hides them, but they often still sit in the tool.
How-to guides for agents
Your agents may keep step-by-step guides in Confluence, Notion or a shared drive. These pair well with tickets. They explain the fixes agents use again and again.
Check what your ticket history is worth
Take a short quiz about headcount, company age, systems and location. A cautious number shows up on screen. Nobody logs into your help desk.
The process
How a support ticket license works
An owner or support lead spends about an hour on the whole deal. Your help desk admin handles the export.
Take the short quiz
Tell us your size, years in business, systems and region. We need no ticket samples and no help desk access.
2 minutesWe match your tickets
We check your help desk history against programs that pay for support conversations. Then we rank the 3 most likely to pay the most.
SecondsChoose and set the scope
Each match explains what the program buys. It also warns you about terms that lock you in. You pick a program and a date range. You choose which ticket statuses go in and which categories stay out. Then you sign up.
One clickExport and get paid
Your help desk admin sends the agreed tickets and articles. The buyer strips customer details and checks quality. Then it pays you on its own timetable. Published timetables span one week to several months.
Weeks to monthsThe market
Real records already earn real money
Each of these comes from a public report or filing. DillisData took part in none of them.
Dollars that captioning company cielo24 got as it shut down. Its 13 years of Jira tickets are the closest public match to a help desk archive.
Forbes, Apr 2026An AI data company's October 2026 pledge, to be spent within a year on records from businesses. Knowledge bases and QA records are on its list.
Company announcement, Oct 2026The sum Meta put in to own 49% of an AI training data supplier.
TechCrunch, Jun 2025How OpenAI co-founder Ilya Sutskever described the supply of public training text in late 2024.
The Verge, Dec 2024Timing
Why ticket archives are worth acting on now
No one can say how long prices will stay where they are. These are the pressures we see.
Solved cases are hard to find
Public forums show questions. But they rarely show a confirmed fix from the company that made the product. That gap is why buyers want help desk records now.
Your product area may fill up first
A buyer may already have tickets from several companies that sell what you sell. Then the next archive in that space adds less. It tends to draw lower offers.
Help desk plans change
When companies switch tools or move to a cheaper plan, old tickets often get left behind or deleted. Licensing while the history is complete keeps that value.
Demand will ease over time
Labs keep collecting and keep testing other ways to train. In time they will need fewer tickets. Nobody knows when.
Support teams turn over
The agents who wrote your best fixes move on. Their notes get harder to find. Sorting solved tickets is easier while that team is still around.
Questions
Questions owners ask
Do customers' names stay in the tickets the buyer uses?
No. The buyer strips names, emails, phone numbers, addresses and account IDs before training. Most buyers let you check samples. No method is perfect, though. So keep out tickets with payment, health or legal details from the start.
Should we include open or unsolved tickets?
Usually not. Buyers pay for the fix, and an open ticket has none. Most deals cover only solved and closed tickets, within a date range you set.
Our Zendesk CSV export has no conversation text. Is something wrong?
No. Zendesk's guide says CSV exports leave out ticket comments. The JSON export includes them. If exports are not turned on yet, the account owner asks Zendesk Support to turn them on.
Can we license help center articles even though they are public?
Yes. Your staff wrote them, so your company owns them. A buyer gets clean source copies with their sections and labels in place. That is more useful than copying them off a website.
What is a support ticket archive worth?
It depends on company size, years of history, ticket count and region. Buyers publish their payouts. Across them, a single company might land between about $100K and $5M+. Your estimate runs those public prices for your top matches. Then it averages them.
We switched help desks years ago. Do old exports count?
Yes, if the files still open and hold the full conversation. Older years are often worth a lot. They show how support changed as your product grew.
Can we license tickets along with other records?
Yes. Many buyers like to see the same customer issue in a ticket, an email and a team chat. For the chat side, see how to sell Slack data to AI companies. If you sell to shoppers, see our retail business data guide.
Does DillisData see our tickets at any point?
No. We only handle the matching. Your admin exports the tickets straight to the buyer you chose.
Get your number
Turn years of solved tickets into a license
Answer a few questions in two minutes and get one cautious number. If the number is not worth chasing, close the page. Nothing will have left your help desk.
Free to your company. No help desk login. Top ticket buyers ranked.