This draft is part of the CCaaS procurement guide. It follows the 15-minute meeting agenda when that meeting ends on "introduce now".
Draft email
Fill each brace from your meeting card. Stay under 200 words.
Subject: {company} contact history before the {old_platform} contract ends
Hi {first_name},
Thanks for the time on {meeting_date}. Before {old_platform} access ends on {access_end}, we checked how its history hangs together. {admin_name} confirmed that transfers keep one shared call identifier, and {crm_owner} confirmed that repeat calls are attached to the original case {callback_share}. Cases close with a recorded reason, and the history covers about {years} years.
You asked whether that history matters beyond the platform switch. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. So you have the full picture: I am a SourceX referral partner and could receive a reward from SourceX if a qualifying license completes. SourceX funds it separately, it never reduces what {company} would be paid, and it has nothing to do with the vendor selection.
If helpful, I can introduce you. SourceX would start with a description only: channels, years, rough volumes and who can approve a discussion. No recordings, transcripts or exports. Just reply "yes" or "not now".
{your_name}
Notes on each line
| Line | What it does | What must stay out |
|---|---|---|
| Subject line | Names the company and a dated contract event, so it is easy to find later | "Monetize your calls", amounts or urgency words |
| "Before {old_platform} access ends on {access_end}" | Anchors timing to the documented end of the old contract | A date you estimated or a reminder that time is short |
| "Transfers keep one shared call identifier" | Reports the transfer finding in the admin's words | Call IDs, sample chains or screenshots of contact records |
| "Repeat calls are attached to the original case {callback_share}" | States the weakest link honestly, with whatever share was given | A percentage you calculated yourself from call data |
| "Cases close with a recorded reason" | Shows the chain ends in a known outcome | Customer names, claim amounts or complaint details |
| "SourceX licenses approved business data..." | One accurate sentence on what SourceX is | Named buyers, statements about demand, or pricing |
| The disclosure | Makes your connection to SourceX explicit before any introduction | "I may receive a small consideration", which hides who pays |
| "Nothing to do with the vendor selection" | Keeps the procurement mandate clean | Any hint that platform choice and referral are linked |
| "A description only" | Writes the metadata boundary down | Requests for recordings, transcripts or exports |
| "Reply yes or not now" | Offers a one-word decline | Follow-up timetables or reward figures |
Why the transfer sentence can be specific. On some platforms the linking is documented. Amazon Connect, for example, gives every transferred or consulted record the ID of the first record in the call, so one field groups an entire call. A repeat call days later starts a new sequence, which is why the repeat-call sentence carries the real information. Do not borrow those field names for a platform that uses different ones; quote the administrator instead.
Why the access date matters. Platforms keep records for limited periods. Amazon Connect documents contact records as available for 24 months from initiation, after which they are deleted. Combined with the old contract's end date, that defines what can still be described, which is why the date belongs in the first paragraph.
Why the disclosure is explicit. The FTC's Endorsement Guides call for clear and conspicuous disclosure of a connection between an endorser and a seller that the audience would not expect and that could affect the weight they give a recommendation. Whether that reaches a private email is a matter for your own advisers; stating it plainly costs one sentence.
Swapping lines for different findings
| What the meeting found | Edit to make |
|---|---|
| Transfers do not share an identifier | Replace the transfer sentence with "Transfers are recorded separately and joined through the case number." |
| Repeat calls are rarely attached to cases | Write "Repeat calls are attached to the original case only sometimes, and the team has not measured how often." |
| The company is an outsourcer | Add "Client contracts may govern these records, and counsel would confirm what {company} can license." |
| Consent for recordings has not been reviewed | Add "Recordings are out of scope until counsel has reviewed notice and consent." |
| No access end date yet | Drop the date and write "before the current platform is retired" |
| The owner wants the COO to lead | Address both and name the COO as SourceX's contact |
The CX consultant email templates cover other contact-center moments, and the introduction email builder assembles the placeholders.
Keep these out of every draft
- Call content. No recordings, transcripts, summaries of what a caller said or screenshots of a contact record.
- Personal data. No customer, agent or supervisor names.
- The reward as an expectation. 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. On a company's first qualifying transaction the reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; the USD 50,000 floor applies once per referred company. Illustrative only, not a promise of earnings: an $800,000 payout to the company would mean a USD 120,000 reward (15%, which exceeds USD 50,000 plus 5%). That arithmetic stays out of the email.
- Claims about the new vendor. Describe its migration scope only from its own documentation or quote.
- A copy to SourceX before the owner replies.
Check fit and authority first
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.
Authority: address the owner, CEO or COO, not the CCaaS project lead. Ownership of recordings and contact records is covered in 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. If retention or migration items are still open, close them with the archive context checklist first. More contact-center referral plays are on the CX consultant referral page.
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 owner replies "yes", register as a partner, confirm fit on who qualifies and read the program terms so the email's disclosure matches them.