Industry
Sell customer support data to AI labs
Outrich Data is a direct buyer of support records from companies with 50 or more employees that run their own support teams. Resolved tickets, chat transcripts, macros and help center articles are de-identified and licensed to AI labs for training and evaluation. Customer names and pasted customer content are removed. Nothing ships without your written approval.
Customer Support data and AI labs
A support team produces a rare kind of record: a real problem, stated badly by the person who has it, followed by the steps a trained agent took and a clear sign of whether it worked. Ticket status, reopen flags and satisfaction ratings supply the outcome. AI labs use these threads to train support agents and to test them.
The support queue is also where customers paste things they should not. Screenshots show account pages. Log files carry tokens. A business customer may forward its own client's details. So the work here is less about one statute and more about careful cleaning, plus a look at what your contracts and privacy notice promised.
Outrich Data buys from companies with at least 50 employees and two years of ticket history. If your team supports another company's customers as an outsourcer, those tickets belong to that company and need its consent. Your own queue is the starting point.
Records in demand
| Record | What AI labs use it for |
|---|---|
| Resolved tickets with full thread history | Training text agents on the path from first message to fix, including the clarifying questions an agent asked. |
| Live chat transcripts with timestamps | Teaching models the pace of real-time support, where customers send fragments and change topic mid-conversation. |
| Macros, saved replies and internal notes | Pairing the approved answer with the private reasoning an agent recorded before sending it. |
| Escalations to engineering and linked bug reports | Training agents to judge when an issue is a defect, and what evidence engineers need to reproduce it. |
| Help center articles and their revision history | Fine-tuning on documentation your team wrote, and on how an article changes after it fails to deflect tickets. |
| Satisfaction ratings and reopen records | Scoring model answers against outcomes, so a reply that closed the ticket counts for more than one that did not. |
| Quality review rubrics and graded tickets | Benchmarking a model against the same standard your team leads apply to human agents. |
Rules that apply
What the title search looks at in customer support.
- Your privacy notice and FTC Act Section 5
- The Federal Trade Commission treats a use of customer data that contradicts a company's own privacy promises as a deceptive practice. Have counsel compare the notice in force when tickets were collected with the proposed use.
- CCPA and CPRA
- California counts many transfers of personal information for value as a sale, with notice and opt-out duties. Deidentified data sits outside that definition when specific safeguards are in place. Review those conditions with counsel.
- GDPR and UK GDPR
- Tickets from customers in Europe or the UK remain personal data while a person can still be singled out. Counsel should decide whether your cleaned records reach anonymization or should be left out by region.
- Business customer contracts and DPAs
- If you sell to businesses, support threads often contain their confidential information and their users' personal data. Those agreements usually restrict use to providing the service. Read the confidentiality and data use clauses.
- State wiretap laws for recorded chats and calls
- Statutes such as the California Invasion of Privacy Act govern recorded calls and have been invoked in claims about chat sessions captured by third-party tools. Counsel should confirm how notice and consent were handled on each channel.
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.
Excluded
What we will not license.
- Customer names, emails, phone numbers, account identifiers and order numbers.
- Attachments and screenshots that cannot be reliably cleaned of personal or confidential content.
- Passwords, API tokens, card numbers and security answers that customers typed into a ticket.
- Tickets your team handled on behalf of another company, without that company's written consent.
- Threads involving minors, or threads routed to legal counsel over a dispute.
Data types common in customer support
Questions
Customer Support: what companies ask.
Can a company sell its support tickets for AI training?
What happens to things customers pasted into tickets?
Does it matter which help desk software we use?
We support business customers under contract. Is that a problem?
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.