ITSM records — anonymized service-desk datasets
The brief
An unusual one: buyers are sourcing IT Service Management records — the ticket data behind help desks and ops teams. If you own or operate a service desk (your own company, your MSP, your homelab-at-scale), exported ticket histories are licensable data.
What a good submission looks like:
- A structured export (CSV or JSON) of incidents / service requests / changes / problems, with fields like category, priority, status transitions, timestamps, resolution notes
- Volume matters: hundreds to thousands of tickets beat a sample of ten
- A short README describing the tool it came from, the date range and the field schema
Non-negotiable: the export must be fully anonymized before you submit — no names, emails, usernames, IPs, hostnames, URLs, company identifiers or free-text that identifies anyone. And you must have the legal authority to license the dataset (your company's data needs your company's sign-off, not just yours).
Requirements
- Structured CSV or JSON export (zip multiple files together)
- Fully anonymized: no names, emails, IPs, hostnames, company identifiers — in any field, including free text
- Include a README: source tool, date range, row count, field descriptions
- You have documented authority to license this data
- Real production records — synthetic or generated tickets are rejected
What your footage trains
Real ticket histories train IT support and workflow-automation models — triage, categorization, and resolution suggestions all learn from how actual incidents moved from open to closed.