---
title: "Sell support tickets and conversations to AI companies"
description: "Can a company license its Zendesk, Intercom or Freshdesk tickets, macros and call transcripts for AI training? What raises value, what is removed and the gates."
canonical_url: https://www.fearofgod.ai/sell/support-tickets-and-customer-conversations
last_updated: 2026-10-25
site: "fearofgod.ai"
lang: en
---

# Your solved support tickets can keep earning

A company that owns its support history, such as help-desk tickets, macros, chat logs and call transcripts with their resolutions, can license it securely for long-term revenue, and fearofgod.ai partnerships typically range from $50K to $3M+. Value depends on outcomes, history and how customer data is handled.

## Can a company license its support tickets for AI training?

Yes, if your company owns its support history and can handle the customer information inside it. Every ticket records a problem in the customer's own words, the steps your team took, the internal notes and escalations, and how the case ended. Over years, that becomes the most complete record of how your product breaks and how your people fix it. Much of a company's data already lives in third-party software. Licensing it means re-licensing what already exists, and getting paid for it rather than giving it away for free. For support, that software is your help desk: Zendesk, Intercom, Freshdesk, Salesforce Service Cloud, or the contact-centre platform that keeps call recordings and transcripts.

Help desks already let you export this history, though not every export is complete. Zendesk, for example, exports tickets, users and organisations as JSON, CSV or XML on plans above Team, once the account owner has asked Zendesk to enable exports, but the CSV export leaves out ticket comments, which are the conversation itself, while the JSON export includes them except for tickets over 1 MB ([Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408886165402-Exporting-ticket-user-or-organization-data-from-your-account)).

## Why do AI labs and agent builders value support conversations?

Because customer service is one of the jobs AI agents are built and tested for, and your real cases show what a test can only simulate. τ-bench, a 2024 research benchmark, simulates customers talking to an agent that has tools and written policy guidelines, and found that even the best function-calling agents it tested, such as GPT-4o, succeeded on fewer than half of the tasks ([τ-bench, arXiv, Jun 2024](https://arxiv.org/abs/2406.12045)). Its authors point to following rules reliably: knowing which rule applies, when to escalate and how to finish the job.

The parts of a support history that teach the most:

- **Procedures.** Macros, saved replies, escalation paths and help-centre articles are your support SOPs, already written down.
- **Resolutions.** Tickets that ended solved, with the steps that solved them, and reopened tickets that show what did not work.
- **Edge cases.** Refund exceptions, outages, billing disputes and the internal notes where an agent asked a colleague what to do.
- **Policy decisions.** When an agent made an exception, refused a request or escalated, and the reason recorded.
- **Real language.** Live-chat logs and call transcripts show how customers actually describe problems, interrupt and change their minds.

## What makes support data more valuable?

Support history is worth more when each conversation carries its outcome and the rule that was applied. In rough order of impact:

1. **Outcomes attached.** Status, resolution codes, satisfaction ratings, reopen flags and time to resolve, joined to each ticket.
2. **Full threads.** Every customer message, public reply and internal note in order, not only the first message and the final status.
3. **The procedures behind them.** Macros, knowledge-base articles and policy documents with their version history, so a buyer can see which rule applied at the time.
4. **History.** Several years across product changes, outages and seasonal peaks.
5. **Domain depth.** Technical or specialised products, such as B2B software, insurance, logistics or telecoms, where answers depend on expertise.
6. **Links to other systems.** Tickets that reference bug reports, orders, refunds or CRM records.

## What gets removed or de-identified from support tickets?

Customers' personal data is the main thing, and you set the scope. You approve the scope before anything is shared, and anything you want left out, such as a customer, a product line, a channel or a period, stays out. fearofgod.ai de-identifies the data before it goes to buyers. Raw data is deleted according to a schedule agreed with the partner.

Typical exclusions you decide on:

- **Contact and account details.** Names, emails, phone numbers, addresses, account numbers, and card or bank details pasted into a ticket.
- **Attachments.** Screenshots and files, which often carry more personal data than the text.
- **Regulated data.** Health, financial and children's information, and anything a sector rule covers.
- **Restricted clients.** Business customers whose contracts bar sharing their tickets.

Replacing a name with a customer ID does not take the data outside European data-protection law while the ID can still be linked back to the customer. The GDPR treats pseudonymised data that could be linked back to a person with additional information as information about an identifiable person, and only data rendered anonymous, so the person is no longer identifiable, falls outside it ([GDPR, Recital 26, EUR-Lex](https://eur-lex.europa.eu/eli/reg/2016/679/oj)).

Delete this line from the 'What gets removed or de-identified from support tickets?' section. The first FAQ answer already carries both tokens.

## What rights and consent do support tickets need?

The gates come from your customers, your contracts and the way calls were recorded. This is general information, not legal advice.

- **Your privacy notice and terms.** Staff at the US Federal Trade Commission have warned that it may be unfair or deceptive for a company to start using consumers' data for AI training, or sharing it with third parties, and tell them only through a surreptitious, retroactive change to its terms or privacy policy ([FTC technology blog, Feb 13 2024](https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/02/ai-other-companies-quietly-changing-your-terms-service-could-be-unfair-or-deceptive)). Check what your notice said when the tickets were collected.
- **Personal data rules.** For EU and UK customers, the GDPR's line between pseudonymised and anonymous data (above) decides whether the law still applies to what you license: pseudonymised data stays inside it, anonymous data falls outside it.
- **Business customers.** B2B support threads often contain your clients' confidential information, and master agreements and NDAs can limit what you may do with it.
- **Call recordings.** US federal law allows a call to be recorded with the prior consent of one party ([18 U.S.C. § 2511(2)(d)](https://www.law.cornell.edu/uscode/text/18/2511)), and other jurisdictions set their own rules. A recording announcement written for your own quality and training purposes may not cover licensing; that is a question for counsel.
- **Platform terms.** Read your help-desk agreement on exports and API use before pulling data at scale.

## What are support tickets worth?

Public prices for support data are rare, so the nearest reference points are deals for company records and conversation text. None is a fearofgod.ai price.

| Reference point | Market side | Figure and source |
|---|---|---|
| A data buyer's programme for midsize companies | Published buyer offer, reported Oct 2026 | [$100,000 to $2 million for anonymised data (Business Insider)](https://www.businessinsider.com/ai-training-employee-data-emails-slack-dms-2026-10) |
| A forum platform's conversation data | Company filing, Feb 2024 | [licensing arrangements signed in Jan 2024 with an aggregate contract value of $203.0 million and terms of two to three years (Reddit S-1)](https://www.sec.gov/Archives/edgar/data/1713445/000162828024006294/reddits-1q423.htm) |
| Bankrupt airline's emails, messages, code and records | Court-process bids, Sep 2026 | [$10 million bid, then a $12.5 million proposal; no sale court-approved as of Sep 14 (Fortune)](https://fortune.com/2026/09/14/micro1-tries-to-beat-googles-bid-to-buy-bankrupt-spirit-airlines-data-for-12-5-million-highlighting-value-of-data-to-ai-companies/); [the $10 million bid was still held up as of Oct 13 (Business Insider)](https://www.businessinsider.com/ai-training-employee-data-emails-slack-dms-2026-10) |

The forum figure is public posts at platform scale. A support history is smaller, but it holds what forums lack: your own procedures and the outcome of each case. Partnerships typically range from $50K to $3M+.

## How does licensing support tickets work with fearofgod.ai?

You license the support history your company already keeps, securely, and earn additional, long-term revenue from it. It already sits in your help desk, so there is nothing new to collect. Your company can be paid more than once, through renewals and repeat licences.

The steps are the partnership form, a conversation, scope and terms, data preparation, then delivery and payment. A useful first description covers your help-desk and contact-centre tools, the years of history, a rough ticket volume, the channels (email, chat, voice), whether resolutions and ratings are recorded, and whether macros and help-centre articles can come with them. [Talk to our team](https://www.fearofgod.ai/partner) when you are ready. If your tickets link to bug reports or internal discussion, see [licensing codebases](https://www.fearofgod.ai/sell/codebases-and-engineering-history) and [licensing chat and email archives](https://www.fearofgod.ai/sell/chat-and-email-archives).

## Selling support tickets to AI companies

A company that owns its support history can sell its support tickets and customer conversations to AI companies by licensing them with fearofgod.ai, securely and for long-term revenue. Partnerships typically range from $50K to $3M+. Partners can be paid more than once, through renewals and repeat licences.

## Frequently asked questions

### Can we sell our support tickets to AI companies?

Yes, if your company owns the support tickets and has the rights to license them. You sell them by licensing them with fearofgod.ai. Your company can keep ownership of its data. This is agreed case by case. Your company's name stays confidential until the agreement is fully signed, and a completely anonymous partnership is also possible.

### Do our customers have to consent?

It depends on where they are and what your privacy notice said when the tickets were collected. Common safeguards are de-identification, leaving out regulated data and restricted accounts, and checking that your notice covers this use. Take legal advice for your jurisdictions.

### Are macros and help-centre articles worth including?

Yes. They are your support procedures written down, and next to the tickets they were used on they show how each policy worked in practice. Their version history shows how the policy changed.

### We use Zendesk, Intercom or Freshdesk. Do we have to change anything?

You do not have to change help desks. No new data collection is needed. The tickets already sit in your help desk, and licensing them means re-licensing what is already there. Check which export your plan offers: Zendesk's export tools are off until the account owner asks Zendesk to enable them, are not on Team plans, and ticket comments come with the JSON export, not the CSV one ([Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408886165402-Exporting-ticket-user-or-organization-data-from-your-account)).

### Do call recordings count, or only transcripts?

Transcripts are the closer fit: they are text, like the rest of your tickets. Recordings can be in scope too, but they also carry callers' voices, so they need more care. You decide which, if either, is included.

### How much can our support data earn with fearofgod.ai?

Partnerships typically range from $50K to $3M+. Value depends on history, the outcomes attached, the domain and the rights. fearofgod.ai does not publish per-ticket prices. Your company can be paid more than once, through renewals and repeat licences.

### Who ends up using the data?

fearofgod.ai licenses data to AI labs and teams building AI models and agents, and never names its buyers. fearofgod.ai de-identifies the data before it goes to buyers.

---

Source: https://www.fearofgod.ai/sell/support-tickets-and-customer-conversations · Index for AI systems: https://www.fearofgod.ai/llms.txt · Contact: sean@fearofgod.ai