# Zendesk operating knowledge referral for AI labs

Canonical: https://refer.sourcex.si/systems/zendesk
Last updated: 2026-11-04

Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Those with well-documented, proprietary operating knowledge derived from systems like Zendesk can be strong referral candidates for SourceX; AI developers have publicly described interest in this kind of operating data.

## Identify valuable Zendesk operating knowledge for referrals

Many businesses rely on robust customer service platforms like Zendesk to manage interactions, track issues, and maintain comprehensive records. The proprietary operational data generated and documented within these systems represents a rich source of knowledge that SourceX can license directly from companies for AI training and evaluation, subject to acceptance at Closing and agreed terms.

As a referral partner, recognizing companies in eligible countries that possess deep, well-structured Zendesk operating knowledge can help you identify high-potential leads. This isn't about exporting raw customer data, but about the *processes*, *workflows*, *resolutions*, and *internal best practices* documented by the company while using Zendesk.

### What makes Zendesk operating knowledge valuable?

SourceX's current data needs often seek data that reflects real-world operational insights. For companies that extensively use Zendesk, this can include:

*   **Detailed internal workflows:** Standard operating procedures (SOPs) for handling specific customer queries, escalations, or product issues, often documented directly within Zendesk's knowledge base or related internal systems.
*   **Resolution patterns and best practices:** Aggregated, anonymized insights into how complex problems are typically resolved, which agents or teams are most effective, and what documentation leads to successful outcomes.
*   **Support article effectiveness:** Data on the usage and impact of self-service content managed through Zendesk Guide, indicating what information is most useful to customers.
*   **Agent training materials:** Proprietary internal documentation used to onboard and train customer service staff, often reflecting the specific challenges and solutions unique to the company's products or services.
*   **Problem categorization and tagging schemas:** The company's unique approach to classifying customer issues, which can reveal valuable domain-specific ontologies and understanding.

### Screening for Zendesk-rich companies

When you encounter a business in an eligible country that uses Zendesk, consider these factors from our [initial screening profile](/who-qualifies) to gauge its potential for a SourceX referral:

*   **Operating maturity:** A company that has used Zendesk for several years and has 50 or more full-time employees at peak is more likely to have developed extensive, mature documentation and processes around its customer service operations.
*   **Original documentation:** Is the company actively creating and maintaining its own internal knowledge bases, SOPs, and training materials within or alongside Zendesk? This includes *how* they use Zendesk, not just the data *in* Zendesk.
*   **Rights to license:** Ensure the company owns its operational documentation and can license it without violating client confidentiality, employee privacy, or third-party agreements. The focus is on *proprietary operational knowledge*, not individual customer data.
*   **Authorized sponsor:** The ideal referral is an owner, executive, or manager of the customer service/support department who can discuss licensing their operational know-how.
*   **Relevance to SourceX's current data needs:** While SourceX determines the exact fit, proprietary insights into efficient customer support, problem resolution, and knowledge management are broadly relevant to AI applications focused on improving service, automation, and user experience.

### What is not a fit?

As with all referrals, avoid material that typically doesn't qualify:

*   Personal consumer data or data the company does not control.
*   Material belonging to the company's clients, rather than the company's own operational insights.
*   Just a list of Zendesk tickets without the underlying documented processes or resolutions.
*   Introductions made without the decision-maker's knowledge or consent.

### How SourceX handles the data

Remember, you do not need to export or upload any confidential records yourself. Your role is solely to make the introduction to a company in an eligible country. The referred company then controls whether to proceed, what scope of operational documentation to offer, and the terms it accepts. Nothing is shared without the company's explicit approval. As the company's direct licensing partner, SourceX manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. SourceX handles preparation through approved processing routes. The focus is on approved anonymized, metadata-level, or process-oriented documentation.

If you know a company in an eligible country with robust, well-documented Zendesk-powered operations, consider introducing them to SourceX. Use our [company fit checker](/tools/company-fit-checker) for a preliminary, non-binding assessment.

> Rewards are calculated as the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout (eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements), with no cap, subject to any signed Schedule A or addendum. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. SourceX funds rewards separately; they do not reduce the company's payout. A lead, meeting or signed agreement alone does not trigger payment. See the [program terms](/terms).
