This agenda is part of the CCaaS procurement guide, which explains why the question "Can the company link call segments to final resolutions?" matters during procurement. This page is for running the conversation.
Who to invite
Keep it to four people. Procurement meetings attract crowds; this one should not.
| Role | Why they are there | Blocks they answer |
|---|---|---|
| Owner, COO or head of customer operations | Decides about the old platform's history and any licensing discussion | 1, 4, 5 |
| Telephony platform administrator | Knows how the current platform records transfers and how long it keeps records | 2, 4 |
| CRM or ticketing owner | Knows whether repeat calls are attached to the original case | 3 |
| You, the consultant | Holds the procurement timeline and the old contract's end date | 1 |
Leave out shortlisted vendors and any outsourced contact-center provider. An outsourcer's role belongs in the ownership notes, not in the room.
Invite text: "Fifteen minutes on the history in our current contact-center platform before we switch. Descriptions only; no recordings, no exports."
The agenda, block by block
Illustrative. A consultant is running procurement for a fictional 290-person home warranty company. Its current platform has handled inbound claims calls for six years, and agents log cases in a separate CRM.
| Minutes | Block | Question | Who answers | A good answer sounds like |
|---|---|---|---|---|
| 0-2 | Contract dates | When does the new platform go live, and when does access to the old one end? | Consultant and owner | "Go-live in Q2; the old contract ends 60 days later, per the renewal notice." |
| 2-5 | Transfer hops | When a call is transferred, does every hop carry one shared identifier? | Platform admin | "Yes, each hop carries the ID of the first one, so a whole call groups on one field." |
| 5-8 | Repeat calls and cases | When the customer calls back days later, is the new call attached to the same case? | CRM owner | "Agents must search the case before wrap-up; we audit that monthly." |
| 8-12 | Retention and ownership | How long are contact records kept, what moves to the new platform, and who owns the history? | Platform admin and owner | "We copy records to our own storage nightly; the COO owns them; counsel reviewed consent in 2023." |
| 12-15 | Disclosure and decision | Would the owner like an introduction to SourceX? | Owner | "Yes, and the COO should lead it." |
Block two in practice. Amazon Connect is one documented model: each transfer or consult creates its own contact record, and every record in the sequence carries the ID of the first, so one field groups the whole call. Other platforms name and store this differently. Ask the administrator how theirs works rather than assuming.
Block three is where chains break. A repeat call is a new contact with a fresh sequence. The only bridge back to the original problem is usually a case or ticket number an agent attaches. If the answer is "sometimes", ask what share of repeat calls carry a case reference and whether anyone has measured it. "Not measured" is an honest answer; write it down.
Block four needs dates, not impressions. Retention varies by platform. Amazon Connect 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. Ask whether the company already copies records to its own storage, and whether the new vendor's migration scope includes historical records with their transfer identifiers and case references.
Scoring the chain as you go
Fill one line per block in the meeting. Three marks: linked, partly linked or unknown.
| Link in the chain | Mark | Note |
|---|---|---|
| IVR to first agent | Linked | Shared identifier on every hop |
| First agent to specialist transfer | Linked | Same identifier |
| Repeat call to original case | Partly linked | Case search required; compliance not measured |
| Case to final resolution | Linked | Closure reason code on every case |
| History survives the switch | Unknown | Migration scope not yet agreed |
A sheet with one "partly linked" and one "unknown" still describes a usable history. It also gives procurement a concrete requirement: ask shortlisted vendors whether they import transfer identifiers and case references, not just recordings.
The decision to close on
Spend the last three minutes on disclosure and the decision, even if earlier blocks ran long.
Say that SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Say that you are a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes, funded separately and never deducted from the company's payout. Then record one outcome.
| Outcome | Choose it when | What follows |
|---|---|---|
| Introduce now | Transfers and cases link for a substantial share of contacts, the owner opts in and can authorize a discussion | Send the CCaaS procurement introduction email |
| Revisit by a date | Retention or migration scope is unknown but has an owner | Carry the open lines into the archive context checklist |
| Stop | The owner declines, or the history will not survive and nobody plans to keep it | Note the date; procurement still gains a sharper migration requirement |
Before anyone is introduced
Fit: 50+ full-time employees at peak (contractors excluded; outsourced agents do not count), documented operating history, rights to license and an authorized contact. 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. Rights can be limited by client contracts and by how notice and consent were handled, so the company's counsel decides; see who owns call recordings in a contact center. SourceX's current data needs, the rights review result and any offer stay unknown until SourceX reviews an application.
Sign the Channel Partner Agreement before submitting. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. Illustrative only, not a promise of earnings: a USD 400,000 Actual Supplier Payout on a company's first qualifying transaction would pay USD 70,000 (USD 50,000 plus 5%, which exceeds 15%). 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. The CX consultant referral page covers other contact-center plays, and the sell-side kickoff agenda and quarterly board meeting agenda show timed formats for other audiences.
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 meeting closes on "introduce now" before the new platform contract is signed, register as a partner, confirm fit on who qualifies and read the program terms before you introduce anyone.