# Support consolidation referral timing: a brief | SourceX

Canonical: https://refer.sourcex.si/guides/the-referral-conversation-after-customer-support-consolidation
Last updated: 2026-11-04

A customer support consolidation changes who answers for the support function, how stretched that team is and which vendor contracts or old help desks end on a date. It does not change who decides about licensing, or whether the company fits. Write those changes down as facts the company itself gave you, keep the unchanged checks beside them, wait until the consolidated desk runs steady, then ask the CEO one question that names what moved.

This playbook is for a VC portfolio engagement lead who hears in an operating review or a board update that a portfolio company has cut its support vendors, brought outsourced support in-house, closed a regional center or moved everyone onto one help desk. When two teams join because two companies merged, [the support team merger guide](/guides/the-referral-conversation-after-a-company-combines-two-support-teams) covers who decides under each kind of deal. Funding stage plays no part in fit, here or anywhere else in the program.

## What "we consolidated support" can mean in a board update

The phrase covers at least four different projects, and each one moves a different fact that the referral question depends on.

| What the company did | What usually moves | The fact to hear from the CEO |
|---|---|---|
| Cut several outsourced vendors down to one | Contracts, the vendor's staff, contract end dates | Which vendor contracts end, and when |
| Brought outsourced support in-house | Who employs the agents and who writes new procedures | Full-time headcount at peak, since vendor agents never counted |
| Folded regional centers into one site | Team size, managers, local ways of working | Who leads support now, and whether the move is finished |
| Retired old help desks for a single platform | Where the history sits, and when an old platform's data goes | The company's own retirement date for the old tool |

Retirement dates are real because some vendors delete data on a schedule. Freshdesk's help center, for one, says a cancelled account and its data are permanently deleted 14 days after the subscription end date, though an older page there gives a different period (our paraphrase). Such dates belong to the company and its vendor; a partner uses them only to know when the question should not wait. How a platform switch splits company-written from customer-written history is the subject of [the ticketing platform replacement guide](/guides/the-referral-questions-around-a-ticketing-platform-replacement).

Consolidation also scrambles authorship. SourceX's screening page names SOPs, internal knowledge bases, QA records and support workflows among the original documentation it looks for, and treats material that belongs to the company's clients as usually not a fit. After a consolidation, one knowledge base may hold articles written by an outside vendor's staff, macros the in-house team rewrote and threads full of customers' own words. The screening page asks whether the company can license its material "without breaching client confidentiality, employee privacy or third-party contracts." A vendor contract is read by the company's counsel, and SourceX's review settles what could be licensed. A partner settles neither.

## The operational-change introduction brief

Fill one brief per company before any outreach. Every line comes from something the company said or published, carries a date and is marked changed, unchanged or unknown. Nothing in it comes from the company's systems.

| Line | What you record | Where it comes from | Changed, unchanged or unknown |
|---|---|---|---|
| 1. The milestone | The change in the company's own words, with its date | The CEO, a board update the CEO wrote, or a public announcement | Changed |
| 2. Who decides | The CEO's name and since when; after a sale has closed, the acquirer's CEO | The CEO or the company register | Usually unchanged |
| 3. Who leads support | Name and role of the support leader, as a possible sponsor only | The CEO | Often changed |
| 4. Steady-state signal | The CEO's or support leader's own word that the desk runs without vendor help | Workload feedback, quoted | Changes over the months |
| 5. Dated ends | Vendor contract ends, an old tool's retirement, a site closure | The company | Changed |
| 6. Full-time headcount at peak | The figure, with contractors and vendor agents left out | The CEO | Unchanged, or higher if agents became employees |
| 7. Whose material | Company-written, vendor-written or customer-written, as the CEO describes it | The CEO, then SourceX's review | Unknown until review |
| 8. Earlier contact with SourceX | Any application, lead, account or email exchange | The CEO | Unchanged |
| 9. What you hold | Nothing from the company's systems: no tickets, counts, exports or screenshots | You | Unchanged |

Read the brief from the bottom up. If line 9 holds anything at all, the brief is not ready. If line 8 shows earlier contact, stop: section 3 of the terms makes such a company a duplicate, credited to no later partner. If line 2 names someone other than the person you planned to ask, start again with the right CEO.

Line 6 is the one eligibility input a consolidation can genuinely move. SourceX counts full-time employees at the company's peak and leaves contractors out, so agents employed by an outside vendor were never part of the figure. A company that hires its own agents may now report a higher peak. Record the number the CEO gives and let SourceX decide fit; never tell anyone the change made the company eligible.

Line 4 sets the timing. A desk is steady when the company says so: the last vendor has gone, procedures are rewritten and the backlog is back to normal. That is the company's judgment, never yours, and every other line can be complete while the answer is still "not yet".

## One portfolio company before and after, with a badly timed ask (Illustrative)

Illustrative. A generic company with invented figures; no outcome is implied.

| Fact | Before, in January | After, in September |
|---|---|---|
| How support is delivered | Two outside vendors plus 12 in-house agents | 46 in-house agents and no vendor |
| Help desks | Two platforms | One platform; the older one retires on 31 December |
| Who leads support | A vendor manager in operations | A head of support hired in April |
| Full-time headcount at peak | 120 | 154, because the new agents are employees |
| Who decides | The CEO | The CEO, unchanged |
| Earlier contact with SourceX | None, per the CEO | None, per the CEO |
| Workload, in the company's words | "Two vendors, two sets of habits" | "A full quarter without vendor help" |

**The badly timed ask.** In May, while the second vendor was still handing over and the new head of support was rewriting procedures, a partner at the fund emailed the head of support, suggested the old ticket archive could "earn its keep", and asked how many years of tickets each platform held. Wrong person, wrong month, and a request no partner should make. The head of support forwarded it to the CEO with a puzzled note. The repair was an apology to the CEO, the request withdrawn and a dated line in the fund's log saying nobody raises the subject again unless the CEO does.

**The better moment.** In September the CEO mentions in a check-in that the desk has run a quarter on its own and that the old platform goes at year end. The engagement lead fills the brief, finds nothing on lines 8 and 9, and asks the question set out below. The CEO wants to hear more and names the head of support as the company's point person; the company applies itself, and the engagement lead submits the introduction with the CEO's written yes.

## Sponsor, decider and spare capacity after the new desk settles

Recheck three things just before you ask, all through the CEO.

**The decider.** Is the person you know still the CEO? If the consolidation followed a sale, the target's CEO decides until closing and the acquirer's CEO after it. If support moved into a parent company's shared service, ask which entity holds the records; for the reward cap, a parent and its subsidiaries count as one company.

**The sponsor.** A new head of support can be valuable later, describing the desk to SourceX at the CEO's request and joining the first call. Sponsoring is not deciding, and it never involves sending you anything. SourceX's sample partner agreement says it gives a partner "no authority to share a supplier's inventory, records, raw data or personal information" (section 4.2), so a support leader who offers examples should be thanked and declined. [Keeping referral notes out of client support tickets](/guides/how-to-keep-referral-notes-out-of-client-support-tickets) covers the case where your own firm works inside the company's help desk.

**The capacity.** A SourceX conversation asks something of the company: it applies, SourceX reviews its history, documentation, rights and relevance, and the company decides scope and terms. Ask the CEO who inside the company would take that on, and in which month. If the answer is "once the new platform beds in", write down that date and wait.

If you learned of the consolidation through a board seat, it may prompt one question to this company's CEO. It never travels further, and it never reaches another company.

## Asking with the facts that moved

Once line 4 says steady, use the change the CEO already knows about and nothing you inferred:

> "Now that support runs in-house and the old help desk retires at year end, would you like to hear about SourceX? It licenses records that companies created themselves, such as support procedures and knowledge bases, for AI training and evaluation. You would decide whether to talk to them, and SourceX decides fit after its own review. If your company went ahead, SourceX might pay me a referral reward, separately from anything it pays you. I don't need any tickets or files."

The payment line rests on section 4 of the terms: the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation." Record the date, the CEO's answer in their own words and any condition they set. A "not yet" with a date goes back on the calendar; a no is final unless the CEO reopens it. Whoever submits must first have signed the SourceX Channel Partner Agreement, and credit goes to the first valid introduction within the 90-day attribution window, once the company files a verified application.

## Where the consolidation signal points the wrong way

- **Cost cutting with job losses.** If the consolidation removed roles, a licensing question beside it reads as opportunism. Hold until the CEO raises something related.
- **Vendor-written material.** Procedures an outside vendor wrote may belong to the vendor or be limited by its contract. That is decided in SourceX's rights review with the company's counsel, and it may shrink what could ever be licensed.
- **Customer-written history.** Ticket threads carry customers' words as well as the company's, and client material is usually not a fit.
- **History already gone.** If an old platform was cancelled before anyone asked, its history may no longer exist. A date that has passed is not urgency.
- **Demand.** Whether a company's records match a current SourceX program is decided in review, and programs change.
- **Nothing measured.** No figures have been published on whether support consolidations lead to introductions. To learn for your own portfolio, log each consolidation you hear about, whether its brief reached line 4, whether the CEO was asked and what the CEO said, over two quarters.

**Methods note.** The brief and the before-and-after table were built on 2026-10-27 from SourceX's screening page, program terms and sample partner agreement, plus one help desk vendor's published deletion schedule. They set out a reasoned sequence, not measured results. It leaves out demand, record quality and payout, which SourceX alone assesses in review.

## 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 brief is complete, the desk is steady and the CEO wants the conversation, [register as a partner](/register) and sign before you submit, check the company again against [who qualifies](/who-qualifies) and read the [program terms](/terms). SourceX's note on [licensing customer support data](/resources/license-customer-support-data-for-ai) describes the category, and more timing playbooks sit in the [guides library](/guides).

Briefing a CEO after a consolidation is referral work; weighing SourceX itself as an investment is a separate decision, and materials for it can be requested through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://support.freshdesk.com/support/solutions/articles/237798-when-will-the-data-be-deleted-once-i-cancel-my-account-
- https://sourcex.si/investors
