# ITSM consolidation introduction email draft | SourceX

Canonical: https://refer.sourcex.si/resources/itsm-consolidation-introduction-email
Last updated: 2026-11-05

Write it after the owner has said yes, address it to the authorized contact, and keep it to a subject line, three short paragraphs and one ask. The email describes what the company told you: whether incidents reference the change that caused them, where rollback reasoning is written, and how many years and instances are involved. It discloses your referral interest and asks for a short metadata conversation. The annotation below explains each line and what must never appear in it.

It belongs to the [ITSM consolidation guide for ServiceNow consultants](/guides/moment-itsm-consolidation-servicenow-consultants). It usually follows the "introduce now" close of the [25-minute meeting agenda](/resources/itsm-consolidation-meeting-agenda).

## Before drafting: permission, recipient, agreement

- **Explicit opt-in.** The CEO or owner agreed to an introduction, not merely to a chat about the archive. If you are unsure, confirm it in one line first.
- **A named recipient.** The person who can authorize a licensing discussion: the CEO, or the owner in an owner-run company. Not the platform admin who answered block two.
- **Signed partner agreement.** The Channel Partner Agreement is signed before any introduction is submitted.
- **Disclosure rules for your profession.** Some consultants have contractual or professional disclosure duties beyond the email; [do you have to disclose a referral fee](/questions/do-i-have-to-disclose-a-referral-fee) covers the common cases.

Plain text, short enough for a phone, no attachments, no screenshots of the instance.

## Draft email, ready to adapt

Illustrative. Replace the bracketed parts and keep the structure.

> **Subject:** Introduction: [Company] and SourceX, change and incident history before consolidation
>
> [Name], following our conversation on [day], I'm introducing you to SourceX while [legacy instance] is still in place. Your team described [number] years of change requests in which incidents point back to the change that caused them, with backout plans and rollback decisions recorded in work notes and CAB minutes.
>
> SourceX licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation and delivery. Replying commits you to nothing and shares nothing. I should be clear that I am a SourceX referral partner: if a qualifying license completes, SourceX may pay me a referral reward from its own funds, never from the company's payout.
>
> Could your team spare 20 minutes with SourceX to describe what exists, how much, and who owns it? No exports or access are needed. [Your name]

## Why each line is there, and what stays out

| # | Line | Its job | Never put in it |
|---|---|---|---|
| 1 | Subject | Names both parties and the event so the thread is easy to find | "Urgent", amounts, or a vague "data opportunity" |
| 2 | "Following our conversation on [day]" | Shows consent already exists | Anything implying the owner agreed to a license |
| 3 | "While [legacy instance] is still in place" | Grounds timing in the documented consolidation | A guessed retirement date or a countdown |
| 4 | The record description | Restates the chain in the company's own terms: change, caused incident, rollback decision, years | Change or incident numbers, outage details, customer names, quoted work notes |
| 5 | What SourceX does | One accurate sentence about the service | Named buyers, acceptance promises or a value estimate |
| 6 | "Commits you to nothing and shares nothing" | Keeps discovery at metadata level | Any request for a sample, export or read-only login |
| 7 | The disclosure | States your interest before a decision | A reward amount for this company, or vague wording about who pays |
| 8 | The ask | One small, bounded action | A second ask, a deadline, or a request to involve the MSP without the owner |

Line 4 is the reason the email exists, so keep it precise. On a standard ServiceNow incident form, Caused by Change holds the number of the change request that resulted in the incident, and a change request's Backout plan holds what is needed to restore the system if an implementation fails. The email should say only that those links and plans exist, how consistently and for how long, never what any single change or incident involved.

## Rewrites for common situations

| Situation | Replace or add |
|---|---|
| The link is used only for major incidents | "Major incidents reference the change that caused them; lower-priority incidents mostly do not." |
| Reviews live in a wiki outside ServiceNow | Add: "Post-implementation reviews are kept in a separate wiki." Name the system type only. |
| An MSP operated one instance | Add: "One instance was run by [provider]; ownership of that history is to be confirmed." |
| An earlier merger renumbered changes | Add: "Change numbers from an earlier merger may need a cross-reference." |
| Archive tables are at risk | Add one factual clause if the [archive context checklist](/resources/itsm-consolidation-archive-context-checklist) flagged it, without urgency language |

Change one sentence, not the structure. The three-paragraph shape is what keeps the email credible.

## What the contact should expect next

SourceX will check 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.

Demand for change-failure records, the rights review result (including service provider and customer contracts), de-identification of names in work notes and any offer remain unknown until SourceX reviews the company. Partners never see tickets at any stage.

For you, attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, and one partner is credited per company. 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; illustrative only, a USD 100,000 payout would mean a USD 55,000 reward, and the floor applies once per company. The [rewards page](/rewards) confirms the reward is funded separately. The [introduction email builder](/tools/introduction-email-builder) and the [wealth advisor introduction email](/resources/wealth-advisor-business-owner-client-introduction-email) show the same discipline in other settings, and the [ServiceNow incident data page](/systems/servicenow-incident-data-for-ai-training) and [archiving guide](/guides/servicenow-data-archiving-retention-policy) give platform background.

## 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 named the contact, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before sending the email.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
- https://www.servicenow.com/docs/r/it-service-management/incident-management/create-an-incident.html
- https://www.servicenow.com/docs/r/BgFKZnPHldZ62gGtzQ71Mw/cZZFYNfdM7ypDoSb~J9Mag
