# Identify US Company Support Tickets for Data Licensing

Canonical: https://refer.sourcex.si/guides/how-to-identify-support-tickets-with-useful-resolution-context
Last updated: 2026-11-03

Support tickets become valuable for data licensing when they offer more than just problem/solution, providing proprietary operational context like detailed processes, decision-making, and unique business workflows. Such material helps AI labs and data users understand real-world operational challenges and resolutions.

## Identifying Support Tickets with Useful Resolution Context for Data Licensing

For **businesses** considering data licensing with SourceX, identifying the right kind of proprietary operational data is key. Support tickets, when rich in context, can be a valuable source of such data. It's not just about the problem and solution, but the unique operational context embedded within the ticket that makes it valuable.

### What makes a support ticket valuable for data licensing?

AI developer programs worldwide are often looking for **original documentation** that reflects a company's unique internal processes, decision-making, and problem-solving methodologies. Support tickets that go beyond a simple query and answer, and instead provide insight into how a company in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) operates, can be highly relevant.

Look for tickets that contain:

*   **Detailed operational workflows:** How an issue moves through different departments, what checks are performed, and the specific steps taken within the company's unique environment.
*   **Proprietary problem-solving methods:** Unique or innovative approaches the company uses to diagnose and resolve issues, which might not be standard industry practice.
*   **Contextual information:** Details about why certain decisions were made, the impact of the issue on specific operational areas, or how the resolution integrates into broader company systems.
*   **Evolution of issues and solutions:** Tickets that demonstrate how recurring problems are addressed over time, leading to process improvements or system changes.
*   **Specific internal documentation references:** Mentions of internal SOPs, knowledge base articles, or training materials that shed light on how the company manages its operations.

*Illustrative:* A ticket detailing a customer service agent's multi-step investigation, involving checks across three different internal systems, collaboration with a product team for a custom script, and a follow-up process to update an internal FAQ, provides far more operational context than a ticket simply stating "Customer reported login issue; reset password." The former reveals a complex internal workflow.

### Why is rich context important?

AI labs and data users are often seeking data that helps them understand real-world operational challenges, predict future issues, or train AI models on nuanced problem-solving. Generic data has limited value; highly contextual, proprietary information is what sets a company's data apart.

SourceX evaluates opportunities based on factors like **relevance to SourceX's current data needs** and the presence of **original documentation**. Support tickets with strong resolution context can fulfill these criteria by providing a granular view of a company's functional processes and institutional knowledge.

### What to avoid and what to ensure

When considering support tickets for data licensing, remember these points from the SourceX eligibility criteria:

*   **Rights to license:** The company must own the material or be able to license it without breaching client confidentiality, employee privacy, or third-party contracts. This is crucial for any data, including support tickets.
*   **Metadata, not raw data:** As a referral partner, you **never** need to export or upload actual company data. Your role is to identify the *type* of data that might be valuable and introduce the company. The company itself decides what data scope to provide under an agreement with SourceX.
*   **Not usually a fit:** Personal consumer data or material that belongs to clients rather than the company itself is generally not suitable.

Focus on identifying **companies** that possess this type of richly contextual operational data within their support systems. Use the [company fit checker](/tools/company-fit-checker) for a preliminary, non-binding screening of potential referrals.

Your role as a referral partner is to make an introduction to an owner, executive, or authorized decision-maker at a company in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia who can discuss licensing its proprietary data, not to evaluate or handle the data itself. SourceX will manage the detailed evaluation of the data's suitability and commercial terms with the referred company.

> Rewards are calculated as the greater of $50,000 plus 5% and 15% of the compensation SourceX actually pays the company you refer, with no cap. A lead, meeting or signed agreement alone does not trigger payment. See the [program terms](/terms).
