QA scoring redesign data introduction email: an annotated draft for CX analytics advisors

Short answer

Write a short email that names the record types the company described, identifies the authorized contact, discloses your referral interest, and asks only for a conversation about metadata. The draft below has a subject line, three short paragraphs and a single ask. The annotation after it explains why each sentence exists and what must never go into it: no scores, no agent names, no transcripts, no attachments, and no estimate of value.

Visual briefFull-size diagram
An email draft writing itself line by line, subject, context, contact, disclosure and ask, with a margin note appearing beside each line to explain it.
The introduction email with its annotations. Placeholders in brackets; no client records ever go in.

It is part of the QA scoring redesign guide. Send it only after the owner has opted in, usually at the end of the 30-minute meeting agenda.

Before you write a word

An introduction email is the last step of a permission process, not the first. Three conditions should be true before you open a draft.

  1. The owner said yes, out loud or in writing. A nod in a workshop is not consent. If in doubt, ask again in one line: "Are you comfortable with me introducing you?"
  2. You know who the recipient is. It must be the person who can authorize a licensing discussion, by name and title. A generic inbox or a junior analyst is the wrong address, however helpful they were.
  3. You have signed the partner agreement. The Channel Partner Agreement comes before any introduction is submitted.

Keep the message short enough to read on a phone. Plain text, no logos, no tracking links, no attachments. If you would not be comfortable with the recipient forwarding it to their legal team, rewrite it until you would.

The draft, ready to adapt

Illustrative. Placeholders are in brackets.

Subject: Introduction: [Company] and SourceX, QA evaluation history

Hi [Contact name],

During [Company]'s QA scoring redesign, [Owner name] and I talked about the evaluation history the current scorecard leaves behind. As the team described it, the platform keeps the first evaluation, the agent's dispute and the final adjudicated decision as separate records for roughly [number] years, alongside calibration results.

You are the right person to decide whether any of that is worth discussing with SourceX, which licenses approved business data directly from companies for AI training and evaluation and handles the agreement, rights review, data preparation, delivery and payout. I have not seen, exported or shared any evaluations or recordings.

For transparency, I am a SourceX referral partner, and if a qualifying license completes, SourceX may pay me a reward from its own funds; it never reduces what [Company] is paid. Would a 20-minute call with SourceX about record types, years and systems, and nothing more, be useful?

[Your name]

Line-by-line annotation

Each row is one line of the draft. The third column is the part people get wrong.

LineWhy it is thereNever put in it
Subject lineTells the recipient what the email is about before they open it, and names both partiesThe words "opportunity", "deal" or a dollar figure
"During [Company]'s QA scoring redesign..."Anchors the email in work the recipient already knows about, so it does not read as a cold pitchDetails of the redesign that the recipient may not be cleared to share
"...first evaluation, the agent's dispute and the final adjudicated decision as separate records"States the finding at metadata level: which record types existAny score, criterion result, agent name or customer detail
"...roughly [number] years, alongside calibration results"Gives shape (how long, what else) without contentA count you guessed; use the owner's figure or leave it out
"You are the right person to decide..."Confirms the recipient's authority and hands them the choicePressure, deadlines or "before it is too late"
"...SourceX, which licenses approved business data..."One accurate sentence on what SourceX doesClaims about buyers, prices, or that the data "will sell"
"I have not seen, exported or shared any evaluations or recordings."Tells the company its records have stayed insideAny hint that you hold a sample or screenshot
"For transparency, I am a SourceX referral partner..."Discloses your interest and states that the reward is funded separatelyThe reward amount, or language suggesting the company pays it
"Would a 20-minute call... record types, years and systems..."A small, metadata-only ask that is easy to accept or declineA request for files, exports, logins or sample records

Why name the dispute and calibration records at all? Because they are the reviewer disagreement evidence the email is about. In Genesys Cloud, for example, agents can dispute completed evaluation scores, and calibration measures each evaluator against a scoring index set by an expert evaluator. Naming those record types tells SourceX what kind of history this is without revealing a single evaluation.

Edits that quietly break the email

Most damage comes from well-meant additions. These are the common ones.

EditWhy it seems helpfulWhat it actually does
Attaching one "anonymized" scorecardShows what the records look likeMoves client records out of the company without authority
Adding "this could be worth six figures"Creates interestSets an expectation no one can stand behind and invites distrust
Copying the whole QA teamKeeps everyone informedSpreads a commercial conversation the owner has not approved
Dropping the disclosure to keep it shortShorter emailHides your interest; the owner agreed on the basis of disclosure
Saying the company "qualifies"Sounds encouragingPrejudges a review only SourceX can make

The introduction email builder and the CX and contact center email templates offer other openings, and the introduction email worksheet helps you collect the facts first. Whatever version you use, keep the disclosure and the metadata-only ask.

Last checks before you press send

Run through these in under a minute.

  • Company fit. 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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.
  • Ownership. For outsourced providers, confirm the records belong to the company and not to its client. If two programs are client-owned, say so in the call, not in the email.
  • Facts. Every number in the email came from the owner. If the archive context checklist left an item unknown, leave it out.
  • Attribution. The first valid introduction within the 90-day window is credited when the company submits a verified application, with one partner per company.
  • Reward. Illustrative only: if the company were paid $400,000 for a qualifying completed handoff, the default reward would be $70,000. Nothing is payable on the email, a meeting or a signature alone. The rewards page has every condition.

What stays unknown until SourceX reviews it: whether buyers need this record type, the rights review result, de-identification needs for customer conversations, and any offer. The QA scorecard data type describes scorecard records in general.

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 has opted in and the draft passes the last checks, register as a partner, confirm who qualifies, and keep the program terms open while you send it.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. 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.

Common questions

Should the email go to SourceX, the owner, or both?

Address it to the company's authorized contact and copy SourceX through the route your partner registration gives you. The contact should see exactly what was said about their company.

Can I mention the platform the company uses?

Yes, naming the system is metadata. Do not describe how a specific evaluation was scored or quote anything from one.

What if the owner wants the reward disclosure removed?

Keep it. Disclosure protects the company and you, and it is the basis on which the owner agreed to the introduction.

Sources

  1. refer.sourcex.si/terms
  2. help.mypurecloud.com/releasenote/january-31-2024
  3. help.mypurecloud.com

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment