How CX operating partners can check support histories before a help desk migration

Why CX operating partners are well placed

A customer experience operating partner works with portfolio companies on support quality, cost to serve and retention: help desk consolidation, contact center outsourcing, knowledge base rebuilds, quality assurance scorecards and, more and more often, AI agent pilots. Every one of those projects runs through the support history, and several of them end with an old system being switched off.

That history is an asset many companies never think to check. Years of tickets with full threads, internal notes, escalations to engineering and a recorded resolution are records of real work with outcomes attached: what the customer asked, what the agent tried, what finally worked. AI developers training agents to handle multi-step service work need exactly that, and it is thin on the public web. The CX operating partner is often close to the cutover plan and knows when the old help desk contract ends.

Which support histories are worth a closer look?

These signals only count at a US company that clears the baseline on the who qualifies page, starting with 50+ full-time employees at peak (contractors excluded) and several years of documented operations.

The 3T check: tickets, transcripts, terms

Run three short checks on any portfolio company with a deep support history.

• Tickets: Is the full history still in the current help desk or an archive, including closed and merged tickets, attachments and internal notes, and can an administrator export all of it?
• Tickets: Do tickets link to the systems around them, such as the CRM account, the engineering issue or the billing record?
• Transcripts: Were calls and chats recorded with notices to customers, and are recordings retained or already purged under a retention schedule?
• Transcripts: Are recordings stored by the company, or only by a telephony vendor or outsourcer?
• Terms: Did the company create these records serving its own customers, or does it run support for clients whose records they are?
• Terms: Do customer contracts, the privacy policy and any outsourcing agreement allow the company to license redacted support records?

A company that passes all six is worth an introduction. One that fails the terms check usually is not, however large the ticket count.

When should it come up in a CX program?

The moment that matters is the one just before history becomes harder to reach.

Do not delay a migration for a licensing review. The aim is a complete export that keeps the option alive after the project. If the sponsor runs a CIO or customer success forum, the guide to functional councils across a PE portfolio shows how to raise the 3T check with several companies at once.

Call recordings: consent and notice

Recordings raise the sharpest legal questions in support data. Federal law is generally one-party consent: under the Federal Wiretap Act, 18 U.S.C. 2511, a person who is a party to a communication, or who has one party's prior consent, may intercept it unless the purpose is to commit a criminal or tortious act. Some states require more. California's Penal Code section 632 prohibits recording a confidential communication without the consent of all parties.

That is why the notice matters as much as the recording. A message saying calls may be recorded for quality and training purposes was typically written with the company's own staff training in mind. Whether it supports licensing redacted recordings to an outside AI developer is a question for the company's counsel, along with the rules in the states its customers call from.

This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

How the introduction works

The CX operating partner opens the door; the company's team does the work.

1. Confirm with the portfolio CEO that the company wants to explore a license, then share a referral link or submit the company through the referral form.
2. SourceX confirms size, history, breadth of systems and rights with the company's sponsor.
3. The company's support and IT leads complete a data inventory: each system, its years of history and what can be exported.
4. Redaction and de-identification rules for items such as customer names, contact details and account data are settled with the company before anyone prepares a single record.
5. Price and terms are settled with the company as a single all-in figure, after which AI labs and data buyers review the opportunity.
6. After an executed agreement and the company's authorization, the agreed records are delivered and the company is paid.

The operating partner never exports tickets, forwards transcripts or describes customer conversations to anyone.

What to say to the portfolio CEO

The operating partner playbook has wording for the wider portfolio conversation.

How rewards work for a CX operating partner

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, and the reward becomes payable only after the buyer pays and SourceX receives its fee. A screen, an introduction or a signed agreement on its own does not trigger payment, and rewards are not guaranteed.

The reward is a share of SourceX's fee, so the company's proceeds are untouched. Before registering, ask the fund CFO how the firm treats fees connected with portfolio companies; the fund CFO playbook explains what that review covers.

When not to bother

• The portfolio company is itself an outsourcer or BPO, and the tickets belong to its clients.
• Support is mostly for consumers, and the records are personal data with no licensing basis.
• Most interactions involve patients' medical information, with no authorization or de-identification in place.
• The old help desk was cancelled without an export, or recordings were purged.
• The support history was already licensed for AI training.
• The company falls short of the size or history baseline.

When a company fails only on exports today, fix it at the next migration and revisit. For a portfolio-wide view, record each company's result on the portfolio heat map.

Next step

Write the 3T check into the cutover plan of the next help desk project. Then work out which other portfolio companies and CX contacts are worth a call with the network opportunity finder, and register as a partner before the old system is retired.