GessoA useful support dataset preserves the customer’s problem, the investigation and the result. For industrial software companies, that may mean connecting a support conversation to an engineering issue, a tested change and a confirmation from the customer. An export containing only ticket subjects and status labels leaves much of that work unexplained.
You can begin assessing the opportunity without exporting customer records. Start by asking your support administrator what the system retains and what its export includes.
Check these five parts of a resolved case
| Record | What it helps explain | What to check |
|---|---|---|
| Original request | The operational problem | Is the full request present, with relevant context? |
| Replies and internal notes | Investigation and handovers | Are messages ordered, with internal and external replies distinguished? |
| Linked engineering issue | Reproduction, cause and proposed fix | Do references still connect to an accessible issue? |
| Attachments | Screenshots, logs and supporting work | Are files included, and can sensitive content be excluded? |
| Resolution evidence | What happened after the response | Is there a test result, release reference or follow-up reply? |
A closed status does not establish that the customer confirmed a fix. If the outcome is missing, describe it as missing rather than inferring success.
Keep the useful links when replacing identities
Consider a fictional field-service software case: an appointment disappears after a schedule change. Support reproduces the issue, engineering reviews a fix, and a later reply confirms the appointment is visible. The relationship between those records explains the work. Replacing ticket and company identifiers consistently can preserve that relationship while removing identifying details.
The fictional case could contain these records. The labels are invented.
| Record in the fictional case | Useful content | Connection to preserve |
|---|---|---|
| Support case S-104 | The reported schedule change, observed behavior and ordered replies | Keep the same case label on the original request and later messages |
| Engineering issue E-22 | Reproduction steps, investigation and the proposed change | Link the issue back to S-104 without exposing a private system URL |
| Release record R-8 | The tested change and when it became available | Connect the release to E-22; distinguish a proposed fix from a released one |
| Follow-up on S-104 | The customer’s recorded confirmation or remaining problem | Keep its position after the release and identify whose observation it is |
During assessment, ask the administrator to describe whether these links are stored as IDs, text references or attached files. A list of ticket titles cannot answer that question. A small inventory of record types and export fields can, without sending customer conversations.
Export formats also differ within the same product. For example, Zendesk’s export documentation says its CSV export omits ticket comments and descriptions, while oversized tickets can lose comments from the JSON export. Check the actual export’s coverage before treating its ticket count as a count of complete conversations.
The review also needs to cover screenshots, logs, private URLs, account IDs and credentials. A text export can look clean while an attached screenshot still shows customer information. Customer-submitted content and third-party code require permission checks separate from redaction.
Decide whether code belongs in the offer
Source code is a separate licensing choice. A support-and-product history can be assessed with code excluded. If a buyer needs code to understand the engineering work, the proposed dataset and rights should make that requirement explicit before your team prepares it.
Useful volume means complete, permitted cases after exclusions, rather than the total number displayed in the support dashboard. Missing attachments, broken issue links and repetitive automated messages can change the assessment.
Prepare for a qualification call
Bring the names of your support system and issue tracker, approximate years of history, and an administrator’s description of available export options. Note customers, channels or repositories you would exclude. No ticket archive is needed for the first call.
Gesso checks the opportunity, develops a buyer proposal and guides export and preparation after buyer terms are settled. Read the software licensing overview and data-protection process, or book a call to discuss your records.