The focus is on understandable workflows
A support case with a clear problem, documented steps and an identifiable outcome can provide more useful context than a large, unstructured message archive. The same applies to operating procedures, project handovers and documented quality processes.
We focus on business knowledge that can be meaningfully described and scoped. Whether it can become a suitable dataset for research, evaluation or training depends on a specific requirement and a separate review.
- Approved operating procedures and internal knowledge documentation.
- Scoped ticket and service workflows with a clear resolution.
- Documented tasks, handovers and project outcomes.
- Aggregated or effectively anonymised process information, where its use is lawful.
An export is not permission to reuse
Slack, Microsoft Teams and project platforms may provide ways to export information. That does not automatically permit disclosure to another organisation or licensing for AI training. The collection method and the relevant platform and API terms must be reviewed.
Privacy requirements, employee interests, customer agreements, copyright and confidentiality also matter. Private messages, credentials and particularly sensitive material are not an appropriate starting point. Businesses should not send complete communication archives simply to find out whether they might be useful.
Anonymisation needs to work in context
Removing names does not necessarily make a dataset anonymous. Roles, timestamps, projects or technical details can still make individuals identifiable. Pseudonymised information generally remains personal data.
Even effective anonymisation does not automatically resolve every other issue. Customer confidentiality, trade secrets and contractual limits may still apply. The intended use and the steps involved in preparing the data therefore need their own documented assessment.
How to describe a potential dataset
For an initial enquiry, describe the workflow, the system used, the approximate time period and the scale. Explain whether customer-specific information or employee data may be involved, and what permissions have already been established.
Do not include individual messages, tickets or examples containing personal information. We can first discuss whether a narrower selection, a technical overview or a professional rights review would be useful. Not every organisation will have a dataset that can be made commercially usable.
An abstract workflow description is a useful starting point: what triggers a case, which steps follow and how is the outcome recorded? Then identify the systems and data categories involved. This gives useful context without disclosing individual employee or customer content. It may also reveal that the relevant knowledge already exists in approved manuals rather than in conversation archives.