# Who can license escalation recovery records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-customer-escalation-recovery-records
Last updated: 2026-11-04

Introduce the CEO, together with general counsel, and bring in the customer success director as sponsor. The director knows which escalations happened, where executive updates were written and how renewals were decided, so they are the right first contact, but they rarely hold authority to license company records alone. Helpdesk and success platform admins have access, not authority. Customer contract terms and personal data in tickets need counsel, and what can be licensed stays unknown until SourceX's rights review.

This decision tree is part of the [customer escalation recovery guide](/guides/workflow-customer-escalation-recovery), which covers what to inventory before a customer platform renewal. Its job is narrower: helping a customer success consultant work out who inside a software or services company can say yes to a conversation about its escalation history.

## The tree: five questions from the record to the signer

Work down the questions in order. Each answer either moves you one level closer to the signer or sends a branch to counsel.

1. **Who knows the cases?** Start with the customer success director. If the company has no such role, the head of support or the COO usually fills it. Ask which record classes exist and which systems hold them. *Outcome:* you have a sponsor, not yet a signer.
2. **Who administers the systems?** Support operations, customer success operations or revenue operations. They answer coverage questions, such as whether Zendesk's archiving of tickets 120 days after close affected exports, or whether Salesforce field history is limited to 18 months because Field Audit Trail is off. *Outcome:* facts for the brief; no authority.
3. **Do customer contracts restrict use of customer data?** If the company signed confidentiality clauses or data processing agreements with its customers, the answer is "possibly". *Outcome:* branch to general counsel.
4. **Do the records contain personal data?** Executive update emails, ticket comments and contact fields usually name people at the customer and inside the company. *Outcome:* branch to general counsel or the privacy lead.
5. **Who approves new uses of company data and new revenue lines?** The CEO; in a portfolio company, sometimes with the board or the investor's operating partner informed. *Outcome:* this is the signer you introduce, with counsel alongside.

Whether a board needs to approve is a separate question, covered in [does licensing data require board approval](/questions/does-licensing-data-require-board-approval).

## Roles around an escalation record, and what each can decide

| Role | What they know | Can they authorize a licensing discussion? |
|---|---|---|
| Customer success director | The cases, playbooks, update habits and renewal decisions | Sponsors and convenes; rarely approves alone |
| VP customer success | Which escalations reached executives and how they ended | Sponsors; does not approve |
| Support operations or helpdesk admin | Retention, archive behavior, tags, exports | No; technical access only |
| Revenue operations | CRM fields, renewal stages, field history settings | No; technical access only |
| General counsel or privacy lead | Customer contracts, data processing agreements, employee data | No; advises on rights and privacy |
| CEO | The case for a new revenue line and its risks | Yes, as the decision-maker and signer |

The pattern matches most workflows: the person closest to the records is the sponsor, the people with admin rights supply facts, and the CEO decides, with counsel.

## The amber branches: customer contracts and personal data

Two questions cannot be settled by anyone in customer success.

**Customer contracts.** Escalation records describe the company's own customers: their outages, their complaints, their executives' names. Many B2B contracts restrict how the vendor may use customer information. Where the company processes personal data on a customer's behalf, data protection law can add a further limit: under Article 28 of the GDPR, a processor must handle personal data only on the controller's documented instructions, and a processor that decides the purposes and means of processing itself is treated as a controller for that processing. Whether any of that applies to a given record class is for counsel, not for the partner or the director.

**Personal data inside the company's own records.** Even where customer contracts allow use, tickets and emails name individuals. That affects de-identification and scope, which SourceX's rights review handles with the company. The [data rights explainer](/proof/why-data-rights-matter) explains why that review comes before anything else.

## What stays unknown until SourceX's rights review

The tree tells you who to introduce. It does not answer whether the records can be licensed. Until SourceX reviews the opportunity with the company, these stay open:

| Open question | Who resolves it |
|---|---|
| Which customer contracts permit use of escalation content | General counsel with SourceX's rights review |
| What must be removed or de-identified | SourceX with the company's privacy lead |
| Whether there is dataset demand for this record type | SourceX |
| Which years and accounts are in scope | SourceX with the customer success director |
| Whether any offer is made, and its terms | SourceX and the company's CEO |

SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Partners never handle the records.

## Making the introduction

Once you know the sponsor and the signer, keep the introduction short. Send the director a draft built from the [referral brief template](/resources/customer-escalation-recovery-referral-brief-template), ask them to correct it, and suggest that they forward it to the CEO with counsel copied. If a joint call follows, the guide on [preparing for a joint call with a company sponsor](/guides/how-to-prepare-for-a-joint-call-with-a-company-sponsor) covers the agenda. The [records across systems map](/guides/customer-escalation-recovery-records-across-systems) gives you the coverage questions for the admins, and the [CX consultant program page](/for/cx-consultant-referral-program) explains how this fits a consulting practice.

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. 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. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application, and only one partner is credited per company.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When the customer success director has agreed to sponsor and you know the CEO will take the introduction, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before the introduction goes out.

## Sources

- https://refer.sourcex.si/terms
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
- https://support.zendesk.com/hc/en-us/articles/4408887617050-About-ticket-archiving
- https://help.salesforce.com/s/articleView?id=xcloud.tracking_field_history.htm&language=en_US&type=5
