Can an IT services company or MSP license its data to AI?
A managed service provider spends every day fixing other companies' machines, and writes down most of it. Years of tickets, runbooks and alert notes show how a skilled technician moves from a vague complaint to a working fix. That know-how is the asset. The clients' systems and secrets are not, and most of the early work is separating the two.
What an IT services company has that is licensable
| Ticket queues with resolution notes | A user's vague report, the questions the technician asked, the steps tried and the note that closed it. Triage reasoning is the part that is hard to find elsewhere. |
| Runbooks and standard procedures | Step-by-step guides for password resets, backup failures, mailbox migrations and server patching, with the edits made after something went wrong. |
| Change records | A planned change, its approval, the rollback plan and what actually happened on the night. |
| Alert histories paired with the fix | A monitoring alert from the remote management tool, matched to the ticket that explains what caused it and how it was cleared. |
| Onboarding and review notes | How a new client's environment was documented in the first weeks, and what was said in the quarterly business reviews about recurring trouble. |
The desk staff count, not the field visits
The size check counts people who work at a computer all day. Service desk technicians, engineers, account managers, project coordinators and billing staff are all on that list. A firm with a large desk and a thin sales team can still qualify.
Most providers keep their history in a professional services automation tool, a remote monitoring console and a documentation platform. Records are spread over all three, so the first job is a short map of which system holds what, and how many years each goes back.
Whose records are inside the ticket
A ticket is written by the provider but about the client. It can quote an error screen with a customer name on it, a pasted configuration file or a forwarded email. The provider's own wording is usually its to license. The client's content inside it often is not.
Managed service agreements commonly contain confidentiality clauses and limits on reusing client material. Read yours before anything is pulled, and ask counsel where the wording is unclear. This is general information, not legal advice.
What stays out for an IT services company
| Passwords, keys and access links | Anything that could open a client's system. Tickets that contain them are cleaned or left out of the license. |
| Client network and security details | Addresses, diagrams, open vulnerabilities and audit findings about a named client are not licensed. |
| Accounts whose agreements bar reuse | Where a client contract forbids sharing, that client's tickets and reviews are left out in full. |
| Names of client staff and end users | People who raised tickets are de-identified, or their records are dropped if that cannot be done reliably. |
How a first package might be scoped
Picture a regional provider with forty staff, six years of tickets in one service tool and its runbooks in a wiki. Its agreements are sorted into three piles: clients who allow reuse, clients who need to be asked, and clients whose contracts say no. Only the first pile feeds the first package. Tickets that carry a secret are scrubbed or removed, and the owner approves a small sample before any export is made.
Questions owners ask about this
Does a monitoring alert on its own have value?
Less than an alert linked to the ticket that explains it. The pair shows cause and cure. Raw alert streams from a client's network are also more likely to hold addresses and device names.
Can we license our runbooks even if the tickets are off limits?
Often yes, since runbooks are the provider's own writing. They still get checked for client names, example screenshots and copied vendor documentation.
A client has asked us never to share anything. What happens to their records?
They are left out, and nothing about that client appears in a sample. The rest of the history can still be considered on its own.
Didn't find your question? Ask us directly.
Keep reading
Records to look at first
- Support tickets: The whole thread, wrong guesses included, with customers replaced by stand-ins.
- Team chat: Slack and Teams threads, where one person must stay one person and direct messages stay out.
- Project and task history: Jira, Asana, Linear, Monday, Trello, ClickUp and Airtable comments and status changes, not task titles.
- SOPs and knowledge bases: Procedures with their edit history and comments; published help articles add nothing.
Other industries
- Software companies: Tickets, postmortems and renewal threads; customers appear everywhere and code is a separate deal.