# CCaaS procurement: linked call segments | SourceX

Canonical: https://refer.sourcex.si/guides/moment-ccaas-procurement-contact-center-consultants
Last updated: 2026-11-04

Sometimes, and CCaaS procurement is the right time to find out. A transferred call usually becomes several segments: IVR, first agent, a transfer, sometimes a callback days later. Linking them to the final resolution needs a shared contact ID across legs and, for later callbacks, a case or ticket number. Contact-center consultants can ask the owner whether that chain is intact before the old platform is retired. If it is and the company qualifies, the owner may choose an introduction to SourceX.

## Can the company link call segments to final resolutions?

Ask exactly that, then probe the two places links usually fail: between legs of one call, and between separate calls about the same issue. Within one call, many platforms keep a shared identifier. Across calls, the join usually depends on agents attaching the call to a ticket or CRM case, which is uneven in practice.

Why it gets overlooked during procurement: RFPs compare routing, workforce management, AI features, pricing and migration support. Requirements ask "can you import our recordings?" far more often than "can you preserve the links between transferred segments and the case outcome?" The context lost between transfers is the part buyers rarely specify, and it is the part that makes the history useful later.

One documented model shows what a good chain looks like. In Amazon Connect, each transfer or consult creates a new contact record. The first leg has no InitialContactId or PreviousContactId; each later leg points back with PreviousContactId, and every leg in the chain carries the first leg's ID as its InitialContactId, so the whole call can be grouped by that one field. A callback two days later, however, is a new contact with its own chain.

Illustrative worked example: a 340-person insurance services firm, one billing dispute, simplified fields.

| Segment | What happened | Shared call ID | Case number | Linked to the outcome? |
|---|---|---|---|---|
| A. IVR | Caller selects billing | Root of chain 1 | None yet | Only through B |
| B. Tier 1 agent | Agent opens case, cannot resolve the charge | Chain 1 | Case opened | Yes, if the case is saved |
| C. Transfer to billing | Specialist explains, promises review | Chain 1 | Same case | Yes |
| D. Callback, two days later | Customer calls again; new agent re-asks everything | Root of chain 2 | Attached only if the agent searched the case | Uncertain |
| E. Resolution | Credit issued, case closed with a reason code | Not a call | Same case | Yes, this is the outcome |

The segment that matters most is D. If the agent attached the case, the full story from complaint to credit survives. If not, chain 2 floats free and the repeated questioning, which is exactly what "context lost between transfers" means, cannot be measured. Your question tests which version the company has.

Why anyone would value this: a linked chain shows a problem passed between people, where context dropped, and what finally resolved it. That multi-step pattern with a known outcome is the kind of business record SourceX assesses for licensing; whether any buyer wants a given company's history is known only after SourceX reviews it. The [CX consultant referral page](/for/cx-consultant-referral-program) covers the wider set of helpdesk and QA records.

## Which four metadata questions follow the linking question?

Once the owner has answered, four follow-ups show whether the history is worth a closer look. Record answers as yes, no or unknown; never request exports, sample calls or screenshots.

1. **Where does the link live?** In the contact-center platform, in the CRM or ticketing system, or both, and which link breaks when it does: transfers or callbacks.
2. **How much and how long?** Roughly how many years of contact records and cases exist, and across which channels.
3. **What will survive the switch?** Platform retention varies. Amazon Connect, for example, documents that contact records are available for 24 months from initiation and are then deleted, and that each contact search covers up to 8 weeks at a time. Ask whether the company already copies records to its own storage, and whether the new vendor's scope includes historical contact records with their transfer identifiers and case references. The [contact-center migration retention page](/systems/contact-center-migration-call-recordings-retention) and the [call recording retention policy guide](/guides/call-recording-retention-policy) go deeper on this.
4. **Who owns it, and were notice and consent handled?** Name the executive who owns the records, and note whether counsel has confirmed how recordings were handled. If not, recordings stay out of any discussion.

For background on ownership, see [who owns call recordings in a contact center](/questions/who-owns-call-recordings-contact-center).

## How do you disclose the reward and get the owner's permission?

Raise the archive question with the owner or head of customer operations separately from vendor demos and the RFP. Explain that SourceX licenses approved business data directly from companies, that you are a SourceX referral partner, and that you could receive a reward if a license completes, which SourceX funds separately and never takes from the company's payout.

Then ask whether the owner wants an introduction. The owner can stop at any point, and a "no" still leaves the archive decision documented before cutover. If the answer is yes, introduce the person who can discuss licensing, describe only what you observed (that transferred segments stay tied to cases through to resolution, over several years), and say that no recordings or records have been shared.

## Who owns contact-center records, and who can authorize a licensing discussion?

The company that runs the contact center usually controls its contact records and cases, but client contracts (for outsourced centers), consent practices and sector rules can limit reuse, so the company's counsel decides. Outsourcers in particular may be processing on behalf of their clients. The person who can open a licensing discussion is normally the owner or CEO, not the CCaaS project lead.

| What you can note | Who confirms it | What stays unknown until SourceX reviews it |
|---|---|---|
| Channels, years and rough volumes | Contact-center operations or IT | Whether the records match current dataset demand |
| Whether client contracts or consent limit reuse | The company's counsel | The rights review result |
| The authorized decision-maker | Owner or executive team | Any offer, its terms and timing |
| Full-time headcount at peak | Owner or HR | Final eligibility confirmation |

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact; see [who qualifies](/who-qualifies). 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.

For your own disclosure: the default reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; the Actual Supplier Payout is the amount SourceX actually pays the company. Further qualifying transactions first agreed within 12 months of the first Closing pay 15%, and a transaction qualifies only when the Actual Supplier Payout is at least USD 100,000. Illustrative only: a $400,000 payout would pay USD 70,000. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details; see [rewards](/rewards). You sign the Channel Partner Agreement before submitting. Other partner roles are listed on the [partner hub](/for).

## Go deeper on CCaaS procurement

- [CCaaS procurement meeting agenda](/resources/ccaas-procurement-meeting-agenda): a timed 15-minute agenda with yes and no branches for the owner conversation.
- [CCaaS procurement archive context checklist](/resources/ccaas-procurement-archive-context-checklist): a tick-box checklist to complete before the old platform is retired.
- [CCaaS procurement introduction email](/resources/ccaas-procurement-introduction-email): a ready-to-edit email for introducing the owner to SourceX.

## 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.

If the client's segments stay linked to resolutions and the owner opts in before the new platform is chosen, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and check the [program terms](/terms) before you introduce anyone.

## Sources

- https://refer.sourcex.si/terms
- https://docs.aws.amazon.com/connect/latest/adminguide/identify-conferences-transfers.html
- https://docs.aws.amazon.com/connect/latest/adminguide/ctr-data-model.html
- https://docs.aws.amazon.com/connect/latest/adminguide/contact-search.html
