A Zendesk account is a long run of small problems solved in writing: the customer's question, the agent's first reply, the internal note asking engineering for help, the macro that finally fixed it, and the satisfaction score at the end. Few systems pair a question with its resolution so cleanly, ticket after ticket.
We have not found a buyer that names Zendesk on its own page. Polyshares buys support tickets as a category, micro1 asks for task histories and workflows employees repeat, and Mercor says it supports 100+ tools beyond the ones it lists. This page covers what in a help desk buyers value, what has to come out first, and what to ask.
Buyers
Who buys Zendesk data
Each reason is the buyer's own published statement naming Zendesk or the kind of data it holds.
Featured partners
micro1
Asks for task histories and well defined workflows that employees execute repeatedly, which is what a ticket queue records.2,3
- $100K to $2M+, micro1 says4
Watch out for: Says it removes personal details only "when relevant", so ask exactly how.5
Polyshares
Lists support tickets among the data it buys, next to Slack, email and CRM.1
- $100K to $2M+, Polyshares says6
- None, Polyshares says7
- An offer in 1 to 2 weeks, then paid in 30 to 60 days8
Watch out for: Exclusive by default, and every deal it lists is exclusive with no end date.9,10
Everyone else we reviewed
By score, with full reviews. We have no referral agreement with these companies, so we do not link out to them.
What buyers value
What in Zendesk buyers value
The column on the right is not legal advice: it lists what to raise with the buyer before anything is exported.
| Data | Why a buyer values it | Raise with the buyer |
|---|---|---|
| Solved tickets with full threads | A question, the steps tried and the answer that worked, with the outcome recorded. | Customer names, emails and order details in every thread. |
| Internal notes and side conversations | The reasoning agents share with each other but never send to the customer. | Nothing specific |
| Macros and help center articles | Your team's tested answers to recurring problems, written by you. | Nothing specific |
| Escalations to engineering or billing | Hard cases worked across teams, often linked to a bug or a refund. | Payment details mentioned in tickets. |
| Satisfaction scores and tags | A label on each outcome, so good and bad handling can be told apart. | Nothing specific |
Process
How it works with each buyer
In each buyer's own published words. Where a buyer publishes nothing, we say so rather than guess.
micro1
- Internal docs, SOPs and playbooks, knowledge bases, project management workflows, internal comms, templates, CRM and workflow metadata, task histories2
- 30 to 200 employees17
- $100K-$2M+ per data package; over $1M for unique data4
- PII removed "when relevant"5
- The company keeps ownership of its data and reviews samples before release18
- Not published
Polyshares
FAQ
Zendesk data: questions, answered
They are the cleanest part to license: written by your team, about your product, with no customer in them. micro1 asks for knowledge bases and templates by name.2
Turing's Project Lazarus says it licenses tickets, code and communications from operating and winding-down companies. Turing is not in our seller ranking yet.24
We do not answer legal questions. Ask the licensing company: their team reviews this with you before anything is signed.
Before you sign
Legal questions go to the licensing company
We do not answer legal questions. Ask the licensing company before you sign: their team reviews these with you.
Questions for this kind of business
- Does our privacy notice or customer agreement restrict this use of tickets?
- Which export method will you use, and does our Zendesk agreement allow it?
- Will customer names, emails and order details be removed before any lab sees the data?
Questions for any buyer
- Is the license exclusive, and for how long?
- Can you sublicense the data, and to whom?
- Which AI labs will receive it, and will you tell us?
- How long do you keep it, and how is it deleted?
- What is your liability cap, and who indemnifies whom?
- Will the contract ban re-identification of people in the data?
- Who removes personal data, by what method, and do we approve it first?