Dispatch platform change data introduction email: an annotated draft for field service integrators

Short answer

Write to the owner who said yes at the end of your meeting: a subject line naming the old dispatch system, one paragraph restating what you learned about diagnosis revisions and repair verification, one paragraph on what SourceX does with your referral interest stated outright, and one paragraph offering the introduction with a description-only ask. Attach nothing and name no figures. Adapt the draft below, then check each line against its note.

Visual briefFull-size diagram
Margin notes on the left appear one by one beside an email to a service company owner that composes itself line by line: subject, what the old system keeps about repeat visits, what SourceX does, the disclosure and a description-only ask.
The draft with its margin notes. Braced placeholders come from your meeting notes.

The email is the last step in the dispatch platform change guide for field service integrators. Send it after the 30-minute meeting agenda closes on "introduce now", and once the archive context checklist has the key facts confirmed.

Draft to adapt

Replace every brace. Aim for under 180 words, short enough to read on a phone between jobs.

Subject: Repeat-visit history in {old_system} before it is retired

Hi {first_name},

Thanks for the meeting on {meeting_date}. A short follow-up in writing: we asked whether your work orders keep diagnosis revisions and successful repair verification. {service_manager} confirmed that each visit has its own dated diagnosis since {first_year}, that callbacks are flagged and linked to the original job, and that closed work orders stay in {old_system} until {retire_event}.

SourceX licenses approved business data directly from companies for AI training and evaluation, and handles the agreement, rights review, data preparation, delivery and payout. Nothing leaves {company} unless you agree terms. So you know where I stand: I am a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes. SourceX pays it separately, it never reduces what {company} would receive, and it has nothing to do with our dispatch project.

If you would like, I will introduce you. SourceX would start with a description only: years of history, which service lines, which system and who can approve a conversation. No work orders or exports. "Yes" or "not now" is all I need.

{your_name}

{retire_event} should be the company's own words, such as "the old contract ends" or "the server is decommissioned". If nobody knows, drop the clause rather than inventing a date.

Line notes: purpose and limits

LinePurposeKeep out of it
SubjectNames the system and the event so the owner can find and forward it"Opportunity", "money", any figure
"Thanks for the meeting on {meeting_date}"Ties the email to a meeting the owner chose to attendImplying the project needs a reply
"We asked whether your work orders keep diagnosis revisions and successful repair verification"Repeats the exact question from the meetingYour opinion of how valuable the history is
"{service_manager} confirmed..."Credits facts to the person who gave themCallback rates, failure counts, customer or site names
"Callbacks are flagged and linked"States the one detail that makes repeat visits traceableA guess about links nobody confirmed
"Stay in {old_system} until {retire_event}"Anchors timing in the company's own planAn invented deadline or "before it is too late"
"SourceX licenses approved business data..."Says accurately what SourceX doesNamed buyers, AI labs or demand claims
"Nothing leaves {company} unless you agree terms"Shows the next step is free of obligationAny hint that SourceX has seen records
The disclosurePuts your interest in plain sight before the offer"I might benefit" without naming SourceX
"Nothing to do with our dispatch project"Keeps the referral apart from your project fees and scopeDiscounts or favors linked to a yes
"A description only"Writes the metadata boundary into the recordA request for a sample work order, a report or photos
"'Yes' or 'not now'"Makes declining effortlessReminder threats or chasers

The disclosure is spelled out because 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 how much weight they give the recommendation. Whether that reaches a private business email is for your own advisers to judge; saying it plainly settles the question.

Facts the first paragraph may claim

Paragraph one is the only part of the email that describes records, so each clause needs a person behind it, or vendor documentation when you mention how a platform works.

ClauseBasisSafer wording
"Each visit has its own dated diagnosis"The service manager or adminCredit them by name
"Callbacks are linked to the original job"The service manager"flagged and linked since {year}" if it started later
"Reopened jobs are visible"Platform behavior: in Dynamics 365 Field Service, for example, booking statuses are separate from the work order system status and a booking status can return a work order to an earlier stageOnly if the client actually runs that platform and the admin confirmed it
"Diagnoses are coded"Platform design, such as incident types for the specific request versus work order types for the general category"coded by incident type" only if confirmed
"Closed jobs stay until {retire_event}"The owner or ITUse their words for the trigger

If a clause has no basis, cut it. An owner forwarding the email to counsel should find nothing that needs correcting.

Rewrites for common situations

Illustrative. Situations an integrator might meet at a fictional 160-person elevator and escalator service company, and the edit each calls for.

SituationEdit
Diagnoses were overwritten each visit before {year}Add "revisions are kept from {year}; before that only the final diagnosis remains"
Callbacks were never linkedReplace the callback clause with "callbacks were booked as new jobs, so links would need rebuilding"
The owner wants their COO to leadAddress both and name the COO as SourceX's contact
An OEM program has rights over some recordsAdd "{counsel} will want to review the OEM terms first"
The owner asked about the rewardAdd a link to SourceX's rewards page instead of quoting a number

The introduction email builder assembles the placeholders, and the wealth advisor introduction email shows the same disclosure in a different relationship.

After sending: fit, attribution and what stays open

On "yes", submit the introduction through your partner account with the owner's details and your meeting notes, then step back. On "not now", record the date and leave it. 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.

Fit: 50+ full-time employees at peak (contractors excluded), a 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. Unknown until SourceX reviews it: dataset fit, the rights review, de-identification and any offer.

If the owner asks about your reward, the default is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, payable only after the conditions on the rewards page are met. Illustrative only: a $250,000 Actual Supplier Payout would mean a $62,500 default reward. The HVAC roll-up page and the guide to AI dispatching give more context on the companies you are likely to meet.

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.

Before the draft goes to the owner, register as a partner, check the company against who qualifies and read the program terms, so your disclosure matches what you signed.

  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 the service manager I work with every day?

Only if they are the person who can authorize a licensing discussion. That is the CEO, or the owner in an owner-run company. Thank the service manager by name in the email for the facts they supplied.

Can I mention how many repeat visits the company has had?

Use spans the company gave you, such as years of closed work orders. Counts of callbacks or failure rates are operational records; leave them to SourceX's own review with the company.

What if the owner replies with questions about price?

Say plainly that SourceX makes any offer after its review, and that you cannot estimate it. Point them to SourceX directly for anything about terms.

Sources

  1. learn.microsoft.com/en-us/dynamics365/field-service/work-order-s…
  2. learn.microsoft.com/en-us/dynamics365/field-service/incident-typ…
  3. ecfr.gov/current/title-16/chapter-I/subchapter-B/part…
  4. refer.sourcex.si/terms
  5. refer.sourcex.si/rewards

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