Skip to content

Record type

The market for support ticket records

Support histories are accepted by Grepped, Troveo, Polyshares, Replay, Turing and SimpleClosure, and micro1 asks for the QA processes and knowledge bases around them. No buyer publishes a per-ticket price; tickets are valued inside a company's whole record, using the per-company ranges each programme publishes.

Page updated 19 Oct 2026. Figures checked 18 Oct 2026 at their sources.

A customer support team at work: one agent on a headset at her monitor while two colleagues discuss a case

Tools that hold it

  • Zendesk
  • Intercom
  • Freshdesk
  • HubSpot
  • Salesforce

Programmes

Who says they accept it

What it saysZendesk and ServiceNow under tasks.
(Grepped, checked 18 Oct 2026)
What it saysIntercom and Zendesk among 30+ systems.
(Troveo, checked 18 Oct 2026)
What it saysSupport tickets among the operational records it licenses.
(Polyshares, checked 18 Oct 2026)
What it saysSupport history in its list of operating data.
(Replay, checked 18 Oct 2026)
What it saysTickets as build history; customer support as a named vertical.
(Turing, checked 18 Oct 2026)
What it saysTickets inside both SourceCode and WorkspaceData.
(SimpleClosure, checked 18 Oct 2026)
What it saysKnowledge bases, SOPs and QA processes.
(micro1, checked 18 Oct 2026)

Price signals

What the record has fetched, where anyone says

None

No programme or report we track gives a per-ticket price. The figures available are per-company ranges.

(Polyshares, checked 18 Oct 2026)

$100K to $500K

micro1's lowest published tier, which covers operational data such as knowledge bases and QA processes.

(micro1, checked 18 Oct 2026)

Full tables: AI training data prices and the disclosed deals database.

What buyers say they do with it

  • Turing lists customer support as one of the verticals it builds from and tickets as part of build history. (Turing, checked 18 Oct 2026)
  • micro1 uses de-identified operational data, including QA processes, to build RL environments. (micro1, checked 18 Oct 2026)

Notes for reading the market

Ticket histories usually hold customer names and contact details, so every programme above says it de-identifies before licensing.

Zendesk starts irreversible deletion 90 days after cancellation, and exports are only available on certain plans.

Keep reading

FAQ

Frequently asked questions

01Which programmes accept support ticket data?

Grepped, Troveo, Polyshares, Replay, Turing and SimpleClosure list tickets or support history; micro1 asks for related knowledge bases and QA processes.

02Is there a price per support ticket?

Not one that is published. Programmes value tickets as part of a company's record and publish ranges per company.

03How long does Zendesk keep data after cancelling?

Deletion starts 90 days after the account is cancelled or terminated and cannot be reversed. After a missed renewal, all data is deleted 90 days from the suspension date.

04Do HubSpot and Salesforce delete ticket data?

HubSpot deletes workflows, sequences and knowledge bases 90 days after a downgrade takes effect. Salesforce returns data on request within 30 days of contract end and then deletes it.

05Why would AI buyers want tickets?

Turing names customer support as a vertical and micro1 builds RL environments from operational data. A ticket shows a problem, the steps taken and the outcome.

Stay current

Get the monthly price update

Once a month: deals that disclosed a value, programmes that changed their published figures, and corrections to this site. Free, and one click to leave.

One email a month: new deals, changed programme figures, corrections. See the data protection notice.

Holding an offer already? Compare it with published ranges.