Can an MSP license its ticket history and runbooks to AI companies?
This guide is for the owner or service director of an MSP or IT support firm. The short answer: parts of what you hold may be licensable, but most of the ticket text itself probably is not yours to license on its own. This is general information, not legal advice.
Can an MSP license its ticket history and runbooks to AI companies?
Possibly, in part. Your own runbooks, internal knowledge base and the way work moves through your service desk are more likely to be yours. Ticket text usually describes clients’ systems and people, so using it needs client permission or may be off limits. A solicitor should confirm the specifics.
AI data programmes look for records of how real work gets done: what came in, how it was triaged, what was tried and what fixed it. An MSP has plenty of that. The question is whose it is. Most search results on this topic are MSPs using their own ticket data inside their business. Licensing it out is a different matter, and it starts with your contracts. See what data AI labs buy for the wider picture.
Who owns the data in your tickets?
Often it is not only you. A ticket can contain a client’s staff names, email addresses, system details and problems. For that personal data, an MSP is frequently a processor acting on the client’s instructions under UK GDPR, which limits what you can do with it. Your client agreements decide the detail.
Two layers matter. First, personal data: if you handle it for a client, you generally do so on their instructions, so using it for your own commercial purpose is a problem unless the client agrees and the law is satisfied. Second, confidentiality and contract terms: your master services agreements may restrict what you do with client information even where no personal data is involved. Read both before anything else. Our guide to client consent and licensing company data goes through the same questions for any firm, and our privacy notice shows how we handle the information you give us.
What is more likely to be yours to license?
Material you created for your own business: runbooks, resolution playbooks, your internal knowledge base, triage rules, escalation paths and service-level routines. Patterns of how tickets move, with client detail stripped out, may also qualify. Check each against your contracts first.
A runbook you wrote describing how to rebuild a failed mailbox is your own work product. So is the rule set that decides which tickets go to which tier. Anonymised workflow patterns, such as how long each stage takes and what usually resolves each category, are more likely to be yours than the tickets behind them, though how well they are separated from client detail matters. Procedure-type material is covered in licensing SOPs and playbooks to AI companies.
How do you triage what an MSP holds?
Sort everything into three groups: likely yours to license, needs client permission, and leave out. Start with where each item came from and whether it names a client, a person or a credential. When in doubt, move it to the cautious group.
Ticket-data triage checklist
| Group | Examples | What to do |
|---|---|---|
| Likely yours to license | Runbooks you wrote; internal knowledge base articles; triage and escalation rules; service-level routines; anonymised workflow patterns (stages, timings, categories) | Check your contracts and any third-party content in them, then include. |
| Needs client permission | Ticket text about a client’s systems; client-specific documentation, diagrams and configuration notes; resolution notes that reveal a client’s setup | Ask the client in writing, or hold it back. Do not assume silence means yes. |
| Leave out | Personal data in tickets; passwords and credentials; client names; security details such as network layouts, vulnerabilities and incident reports | Exclude. Do not rely on a quick find-and-replace to clean it. |
Run this against what sits in your PSA or helpdesk, your documentation tool and your shared drives. When in doubt about an item, put it in the more cautious group.
What happens after triage?
You have a short list of what you could offer and a list of questions for clients and your solicitor. Then a free check can show which programmes might suit that material, before anyone is contacted or any data leaves your systems.
Nothing is shared with a programme without your agreement, and we do not ask you to upload ticket data. The 3-minute check asks about your processes and records, and the estimate on our homepage gives an illustrative range for a firm of your size. It is an estimate, not an offer. How programmes handle the process end to end is in how AI data programmes work, and what drives the price explains why clean provenance matters.
On money: the check is free, and Orca charges a success fee only if a deal closes, agreed in writing before anything starts. Programmes may also pay Orca a referral fee, which we tell you about first. Neither decides what we recommend. The detail is on the disclosures page, and every guide is listed on the guides page.
Common questions
Can we license old tickets if we remove names and company details?
Not automatically. Removing names helps, but ticket text can still describe a client’s systems, and proving data is truly anonymous is hard. Your client contracts may also limit use of their information. Treat removal as a step in the triage, then ask a solicitor before relying on it.
What if our client contracts say nothing about AI?
Silence is not permission. Look at what the contract says about client information, confidentiality and what you may do with it. If it is unclear, ask the client, or keep that material out and license the parts that are clearly yours.
Is monitoring and alert data any different from tickets?
It can be. Alerts and logs often name devices, users and networks, so they carry the same client questions. Generic patterns, such as which alert types lead to which fixes, are easier to separate from client detail than the raw feed.
Does the size of our MSP matter?
Programmes tend to look for documented, consistent work, not headcount alone. A small firm with clear runbooks and a clean triage can be a better fit than a larger one with scattered notes. The free check shows where you stand.