# QA scoring redesign introduction email | SourceX

Canonical: https://refer.sourcex.si/resources/qa-scoring-redesign-introduction-email
Last updated: 2026-11-05

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.

It is part of the [QA scoring redesign guide](/guides/moment-qa-scoring-redesign-cx-analytics-advisors). Send it only after the owner has opted in, usually at the end of the [30-minute meeting agenda](/resources/qa-scoring-redesign-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.

| Line | Why it is there | Never put in it |
|---|---|---|
| Subject line | Tells the recipient what the email is about before they open it, and names both parties | The 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 pitch | Details 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 exist | Any score, criterion result, agent name or customer detail |
| "...roughly [number] years, alongside calibration results" | Gives shape (how long, what else) without content | A 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 choice | Pressure, deadlines or "before it is too late" |
| "...SourceX, which licenses approved business data..." | One accurate sentence on what SourceX does | Claims 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 inside | Any 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 separately | The 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 decline | A 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.

| Edit | Why it seems helpful | What it actually does |
|---|---|---|
| Attaching one "anonymized" scorecard | Shows what the records look like | Moves client records out of the company without authority |
| Adding "this could be worth six figures" | Creates interest | Sets an expectation no one can stand behind and invites distrust |
| Copying the whole QA team | Keeps everyone informed | Spreads a commercial conversation the owner has not approved |
| Dropping the disclosure to keep it short | Shorter email | Hides your interest; the owner agreed on the basis of disclosure |
| Saying the company "qualifies" | Sounds encouraging | Prejudges a review only SourceX can make |

The [introduction email builder](/tools/introduction-email-builder) and the [CX and contact center email templates](/resources/client-introduction-email-templates-for-cx-and-contact-center-consultants) offer other openings, and the [introduction email worksheet](/resources/a-reusable-worksheet-for-introduction-email-preparation) 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](/resources/qa-scoring-redesign-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](/rewards) 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](/data-types/call-center-quality-assurance-scorecard) 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](/register), confirm [who qualifies](/who-qualifies), and keep the [program terms](/terms) open while you send it.

## Sources

- https://refer.sourcex.si/terms
- https://help.mypurecloud.com/releasenote/january-31-2024
- https://help.mypurecloud.com/?p=380404
