# Support team merger referral: when to ask the CEO | SourceX

Canonical: https://refer.sourcex.si/guides/the-referral-conversation-after-a-company-combines-two-support-teams
Last updated: 2026-11-05

When a company combines two support teams, its CEO is already looking at what the merged function holds and what the old setup will leave behind. That makes it a fair moment for a partner who knows the CEO to ask one question: would the company like to hear whether material it created itself, such as its support procedures and internal knowledge base, could be licensed to SourceX? Confirm who decides, wait until the cutover has settled, ask once, and never open, export or summarize a single ticket.

This is for the partner network strategist at a consultancy, MSP, implementation partner or fund platform whose people hear about support consolidations before most outsiders do.

## What a support merger changes, and why the CEO is already thinking about it

Two queues become one. Two sets of procedures, two knowledge bases and often two help desk platforms are reduced to one, and someone has to decide what moves, what is rewritten and what is retired. Those decisions come with dates.

The tooling makes the dates real. Zendesk's own help article, for example, says there is no quick way to merge two of its accounts: each object carries a unique ID, migrated tickets and users get new IDs in the target account, and historical reporting data cannot be moved from one instance to another (our paraphrase). Whatever stays behind in the platform being retired depends on choices the company makes during the merger, and the CEO, or a support leader reporting to the CEO, knows when they fall.

The material in play is easy to name at the level of types: procedures, knowledge articles, macros, quality scorecards and ticket history. Some of it the company wrote itself; SourceX's screening page lists SOPs, internal knowledge bases, QA records and support workflows among the original documentation it looks for. Some of it was written by customers, and material belonging to clients is usually not a fit. Which is which, and what the company may license, is decided in SourceX's review; the split between customer-written and company-written history is the subject of [the referral questions around a ticketing platform replacement](/guides/the-referral-questions-around-a-ticketing-platform-replacement). The partner's part ends at the question.

## Four kinds of support merger, and who decides in each

The merger tells you whose question it is. Name the kind before you name a person.

| Kind of merger | What happened | Who decides | Floor and timing |
|---|---|---|---|
| 1. Folded in after an acquisition closed | The acquirer moved the target's support team onto its own desk | The acquirer's CEO, for the target as well | The USD 50,000 floor applies once, to the group's first qualifying transaction; ask once the combined desk is running |
| 2. Announced, not yet closed | Two companies plan to combine support after a sale | The target's CEO for the target until closing | The integration plan is not the partner's to discuss; wait for closing unless a CEO raises it |
| 3. Two internal teams combined | Product lines, regions or channels merged into one support function | The company's CEO | Ask after cutover |
| 4. Moved into a parent's shared desk | A subsidiary's support team now runs from the parent's shared service center | The parent's CEO, for the group | The floor applies once across the group; ask the parent's CEO, not the subsidiary's support lead |

When the merger follows a deal, the [integration team guide](/guides/what-an-integration-team-can-tell-a-referral-partner) covers what the people running it can say, phase by phase. In kinds 1 and 4, the group is one referred company for the reward: the USD 50,000 floor applies once, to its first qualifying transaction, and further qualifying transactions first agreed within 12 months of that Closing pay 15% with no cap. Whether one group company's earlier contact with SourceX affects credit for another is not settled in the terms, and SourceX looks at each such case in duplicate review.

## The support consolidation introduction guide

Five checks before anyone writes, then one question and one record. Every check is answered by a person or a public announcement, never by looking at a system.

| Step | Check | Where the answer comes from | If it is not met |
|---|---|---|---|
| 1 | The merger is confirmed by the company | A public announcement, or the CEO telling you directly | Wait; a vendor's or an engineer's mention is not confirmation |
| 2 | The entity and its current CEO are named | The announcement or the company register, dated | Find the right CEO; after closing, that is the acquirer's |
| 3 | The combined team is past cutover | The CEO or the support leader says it is running | Note the date they give and wait for it |
| 4 | Sponsor and decider are kept apart | The support leader may sponsor; the CEO decides | Ask the sponsor whether the CEO would want to hear about it |
| 5 | No earlier contact with SourceX | The CEO's answer | Stop; a company already known to SourceX is reviewed as a duplicate |

**The question (Illustrative wording).** "Now that the two support teams are running as one, a question that has nothing to do with the merger itself: SourceX licenses business records that companies created themselves, such as procedures and knowledge bases, for AI training and evaluation. Would you like an introduction to see whether anything you hold fits? I'm a referral partner, so SourceX could pay me a reward; it comes from SourceX and doesn't reduce what the company would receive. A no is a perfectly good answer."

**The record.** One entry: the date, who you asked, the CEO's answer in a few words and the next step with its owner, if there is one. The [referral note format](/guides/the-referral-note-format-that-preserves-context) has a template; nothing about the merger's internals belongs in it.

If the answer is yes in writing, the person who will submit registers and signs the SourceX Channel Partner Agreement before submitting. Credit goes to the first valid introduction within the 90-day attribution window, once the company submits a verified application.

## Signals that it is the wrong week

A consolidation is a trigger only when the question can be heard as what it is. Hold the message when:

- **The cutover is happening now**, or the combined queue is visibly behind.
- **Roles are being cut** as part of the merger. The licensing question is about records the company created, and raising it beside job losses reads as opportunism.
- **A sale is pending.** Until closing, the integration plan belongs to the two companies.
- **The CEO is changing.** Wait until the new CEO is in place and ask them.
- **The pitch drifts toward savings.** Never present licensing as a way to pay for the integration or as a source of new income. What a company might license, and on what terms, is unknown until SourceX's review.

## What the partner never touches

The partner never reviews, exports or summarizes support records, and never asks for ticket counts, samples or screenshots. If your firm is running the migration, the access that work gives you belongs to the engagement, and referral notes stay out of the client's own systems, as [keeping referral notes out of client support tickets](/guides/how-to-keep-referral-notes-out-of-client-support-tickets) describes. Nobody gathers material for SourceX: an introduction is one company whose CEO agreed to it, and what the company shares later is between the company and SourceX.

## Three merged support teams (Illustrative)

Illustrative. Generic companies with invented facts; no outcomes implied.

**A. Kind 1, ask now.** A 320-person software company bought a 90-person competitor in the spring and moved both support teams onto one desk in August. The acquirer's CEO, who knows the partner as the company's outside accountant, mentions that the old desk retires in January. In October the partner asks the question once, with the reward disclosed. The CEO answers yes in writing; the partner, already signed, submits the introduction. The floor applies once to the group; there is no cap.

**B. Kind 3, wait.** A 450-person logistics operator announces that two regional support centers will merge next quarter. The partner sends nothing, notes the date the company gave and plans to ask only after the combined center is running.

**C. Kind 4, the right CEO.** A 120-person distributor's support now runs from its parent's shared service desk. The subsidiary's support lead is keen and offers to "send some examples". The partner declines the examples, asks whether the parent's CEO would want to hear about the program and waits. The support lead's enthusiasm is not the yes; the [contact-level permission guide](/guides/when-an-account-has-several-contacts-with-different-permissions) shows how to record the difference.

## Where this trigger misleads

- **A merger is not a fit.** The combined company faces the same screen as any other: full-time headcount that reached 50 or more at its peak, contractors excluded, an operating history in its own records, the right to license that material and a CEO who asks to hear more.
- **Much of a help desk may be customer-written.** Ticket threads hold customers' words as well as the company's, and SourceX's review, not the partner, decides what could ever be licensed.
- **Retirement dates are the company's.** A dated retirement is a reason to ask sooner, never a reason to advise on what to keep.
- **Nothing has been measured.** Whether support mergers lead to more introductions than other triggers is unknown. To find out, log each merger you hear about, the step at which it stopped and the CEO's answer, over two quarters; no figures are published.

More trigger guides are in the [guides library](/guides).

## 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 a consolidation passes all five checks and the CEO wants the conversation, [register as a partner](/register) before you submit, confirm the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) on who is credited in a group.

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://support.zendesk.com/hc/en-us/articles/4408887037082-How-do-I-merge-or-migrate-two-Zendesk-accounts
