This guide is for the partner network strategist at a customer experience consultancy, managed service provider, accounting firm or fund platform whose people hear about service changes before they are announced.
What a service-model change decides
Three things move together when the model changes: who answers customers, who writes down what happened, and where that record lives. Everything the old model produced stays behind, in whatever systems it used.
ISO's standard for customer contact centres shows how wide the range of models is. ISO 18295-1:2017 is written to apply to both in-house and outsourced contact centres of all sizes, across sectors and interaction channels, and the edition now in development describes its scope as all operating models, including human-assisted, automated or digitally enabled interactions (our paraphrase of search excerpts from iso.org). A company can move between those models, and each move changes who writes the record.
Neighboring triggers have their own guides. When two support teams combine, the people change (the support-team merger guide); when a catalog is redesigned, the list of services changes (the service catalog redesign guide); when outsourced work comes home, the authorship of the record flips back (the insourcing guide). This page is about the model itself: who answers, and how.
Why the switch suits one question to the CEO
Three features make the weeks after a service-model change a relevant time rather than an opportunistic one.
- The CEO has just looked at service as a whole. A model change is approved at the top, after someone has laid out what service costs and what it produced.
- The old history has dates attached. Old platform contracts, provider handovers and knowledge-base rewrites each fall on a day the company chose.
- The company's own material comes into view. Agent guides, escalation procedures, macros and quality scorecards are reviewed, rewritten or handed over. SourceX's screening page lists support workflows, internal knowledge bases and QA records among the original documentation it looks for.
Hold the question when the change comes with service jobs being cut, when complaints spiked after the switch, when the provider or vendor contract is still being negotiated, when the CEO is about to change, or when you heard about the change through paid work your engagement does not let you use.
The service-model transition questions
Four directions, each with the question it raises. The middle columns are asked of whoever told you about the change, in conversation; the decision is never theirs.
| Direction | What changes in the record | Ask whoever told you | Why the CEO is already thinking about it | Ask the CEO after |
|---|---|---|---|---|
| To an outside provider | Provider staff write new contacts, often in the provider's own tools; the in-house years stay behind | "Will the in-house years stay in a system the company controls?" | The CEO approved what the provider receives and what stays in-house | The handover is complete and the provider runs the desk |
| To automated or AI-assisted channels | Knowledge articles and agent guides the company wrote now feed a tool | "Has any of this material been licensed for AI training, to the tool's vendor or to anyone else?" | The CEO approved which company material the tool may use | The launch has settled and the old macros are frozen |
| To self-service | Customers write more of the record and staff write fewer answers | "Which years were written mostly by your own staff?" | The CEO chose which past answers become public help pages | The portal has been stable for a while |
| To dedicated account teams | Work moves from a ticket queue to account plans and notes in a CRM | "Where will the queue's history live once it closes?" | The CEO decided what the old queue is still for | The old queue has closed |
The automated-channel question is a gate, not a detail. SourceX's company process page lists, among what a supplier confirms, that the data has not been licensed for AI training before; if the company's guides were licensed for that purpose to a tool vendor or anyone else, that material is out. The self-service question matters for a different reason: SourceX's screening page treats personal consumer data and material that belongs to clients as usually not a fit, so the years when the company's own staff wrote the answers are the ones worth naming.
Method note. The directions follow the operating models named in ISO's contact-centre standard as excerpted above; the questions apply SourceX's who-qualifies screening profile, its company process page and the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), all read on 2026-10-27. The timing column is this page's design, not a measured result, and SourceX has published no figures on introductions raised after service changes.
Head of service, sponsor and CEO
| Person | What they can do here | What they cannot do |
|---|---|---|
| Head of customer service | Answer the table's questions from what they know; sponsor the idea internally | Agree to a licensing discussion |
| The outside provider or the tool vendor | Nothing in this conversation | Speak for the company; their records about other clients are never part of it |
| The CEO | Decide whether the company talks to SourceX, and sign for it | Hand that decision to a partner |
Who decides moves with ownership: once an acquisition closes, the acquiring company's CEO decides for the business it bought, and before that the target's own CEO keeps the decision. A whole corporate group, parent and subsidiaries, counts as one referred company, so the USD 50,000 floor applies once across it. The published fit facts hold whatever the model: at least 50 full-time employees at the company's peak (contractors, a provider's agents among them, are not counted), several years of records its people created, the rights to license them and a CEO interested in talking, plus the location rules on who qualifies.
One question to the CEO, and a dated record
The question (Illustrative wording). "With the new service setup running, one question that has nothing to do with it: SourceX licenses material a company's own staff created, such as agent guides, escalation procedures and quality scorecards, for AI training and evaluation. If you like, I can send two paragraphs on how it screens companies, and you can decide whether to talk. You should know I'm a referral partner: SourceX could pay me a reward, separately, without changing anything the company would receive."
The record. The direction of change, who told you and when, the answers to the table's questions in a few words, the CEO's reply, the next step with its owner, and a revisit date if the answer was not now. Nothing from the service records themselves goes in it, and no one collects those records for SourceX.
Nothing is submitted without a written yes, and the person who submits registers and signs the SourceX Channel Partner Agreement beforehand. The terms tie credit to dated evidence, not clicks: section 2 gives it to the first valid introduction of a company that is new to SourceX, made within the 90-day attribution window and followed by the company's own verified application, and it says an earlier link click alone does not decide credit. A company that had already been in touch with SourceX in any recorded way, by application, lead, account or email, is a duplicate under section 3. When several people know the same company, agree who asks before anyone does; SourceX settles overlapping claims in duplicate review.
A 260-person distributor hands its phone desk to a provider (Illustrative)
Illustrative. The company and its numbers are invented, and nothing here predicts a review outcome.
- March. A building-products distributor with 260 full-time staff hands front-line phone and email contacts to an outside provider. Its in-house desk had run on the company's own help desk since 2014, with agent guides and escalation procedures written by its staff since 2015. The help desk stays read-only, under the company's control.
- April. The COO mentions the change to an IT consultant who supports the distributor's network, not its help desk. The provider's first weeks are rough and complaints are up, so the consultant waits.
- June. The desk has settled. The COO answers the first row's question: the in-house years stay in the company's system. The consultant asks whether the CEO would want to hear about SourceX; the CEO reads the two paragraphs and says yes by email.
- July. The consultant, registered and signed since the spring, submits the introduction. The distributor applies itself and SourceX reviews fit and rights. Nobody contacts the provider.
If the distributor later licensed data and SourceX paid it USD 400,000, the default reward on that first qualifying transaction would be USD 70,000, the greater of USD 50,000 plus 5% and 15% (Illustrative). Section 4 of the terms says the reward "is never deducted from the supplier's agreed compensation", so the distributor would receive the same amount with or without the consultant.
When the service-model trigger misleads
- Customers write much of a service record. Messages, chats and calls hold customers' words and personal details, and only SourceX's review decides what the company could ever license.
- Provider-held years may not be the company's. Records an outside provider wrote in its own tools raise their own rights questions, which belong to SourceX's review, never to the partner.
- A new model is not a fit. The company faces the same screen as any other; a modern service setup proves nothing about its history or rights.
- The change is the company's to explain. Never present licensing as a way to fund the new model or as income; what a company might license is unknown until review.
- Nothing is measured. Log each service-model change you hear about, its direction, where the conversation stopped and the CEO's answer, for two quarters; no benchmark exists.
For what support material looks like at the level of types, see customer support workflows and the operational history behind a fast-growing support team. If your firm also works inside the client's service tools, keep referral notes apart as described in keeping referral notes out of client support tickets. More trigger guides sit in the guides library.
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 new service model has settled and the CEO has asked to hear more, register as a partner before submitting, set the company against who qualifies and read the program terms on duplicates and credit.