Dispatch platform change referral meeting agenda: 30 minutes on repeat-visit history for field service integrators

Short answer

Hold 30 minutes in five timed blocks. Minutes 0-4 confirm what the new dispatch platform will import; 4-11 ask the core question, "Do work orders retain diagnosis revisions and successful repair verification?"; 11-17 check whether callbacks link to the original job; 17-23 find out how the company proves a fix held; 23-30 name the owner, disclose your referral interest and close on a decision: introduce, revisit by a dated deadline, or stop. Nobody opens a work order.

Visual briefFull-size diagram
A meeting clock divided into five wedges that fill in turn, labeled migration scope (0-4 minutes), diagnosis revisions (4-11), callbacks and links (11-17), proof the fix held (17-23) and owner and decision (23-30).
The 30-minute agenda as a clock. Shift minutes between blocks if you must, but keep the last seven.

This agenda is part of the dispatch platform change guide for field service integrators. The archive context checklist follows up on the answers before the old platform is retired, and the annotated introduction email is what you send if the meeting ends in a yes.

Who sits at the table

Keep it to four or five people, and choose them for what they know about past jobs, not the new rollout.

SeatWhat they knowBlocks
Owner, CEO or COOWho owns the service history and whether to discuss licensing5
Service operations managerHow diagnoses, callbacks and resolutions are actually recorded2, 3, 4
Admin of the old dispatch platformField behavior, years of closed work orders, attachments1, 2, 3
Integrator lead (usually you)What the migration will import and what stays behind1
Warranty or contracts lead, if there is oneOEM and customer terms that limit reuse5

The invite needs one sentence of purpose: "Thirty minutes on the closed work order history before the old platform is retired. Descriptions only, nothing pulled." Leave the new platform vendor off the list; their job is the future, and this meeting is about the past.

Agenda sheet: minute by minute

Illustrative. An integrator is moving a fictional 210-person fire protection and sprinkler service company to a new dispatch platform. Its old system holds closed work orders from 2012.

MinutesBlockQuestion to askWho answers
0-4Migration scopeWhich work orders move: open only, or closed history too, and with notes and attachments?Integrator lead and admin
4-11Diagnosis revisionsDo work orders retain diagnosis revisions and successful repair verification?Service operations and admin
11-17Callbacks and linksWhen a customer calls back, is the new job linked to the first one and to the asset?Service operations
17-23Proof the fix heldWhat does the company record as evidence the repair worked?Service operations
23-30Owner and decisionWho owns this history, do contracts limit reuse, and would the company like to hear how licensing works?Owner and contracts lead

Ask the admin to keep time. Take notes in four columns: block, answer, who said it, open item with a name.

What a usable answer sounds like

Minutes 0-4: migration scope

Usable: "Open work orders, assets, customers and agreements move. Closed jobs stay in the old system, read-only, until the contract ends." That tells you the history exists and has a lifespan. If the reply is "we'll export everything to a spreadsheet", ask whether notes and attachments go into it; a flat export may keep the header and drop the rest.

Minutes 4-11: diagnosis revisions

Usable, in the sprinkler company's terms: "The tech who found the corroded dry-pipe valve logged it on the first job, and the tech who later traced the real fault to a failing air compressor added a second, dated finding. Both are still there." Weak: "The deficiency field says what was wrong." A single field usually means the last entry wins and the first technician's reading is gone. Product design varies: Microsoft's Field Service documentation, for one, keeps a broad job category apart from the specific incident and lets an admin attach several possible resolutions to that incident. You are not auditing the tool's features, only asking whether the old system kept the first finding once a second one arrived.

Usable: "A return trip for a dropped alarm panel or a repeat low-air signal is opened from the original job, so it carries the parent number and the building's system ID." Weak: "Dispatch books a new call." Without that parent number, the second trip reads as a fresh service call once it is exported. Ask one follow-up: can a technician reopen the original job instead of starting a new one? Some tools allow it; Microsoft documents a setup in which a booking outcome sends the job back an earlier step for follow-up, with booking status tracked apart from the job's own status. Note which approach the client used, and since when.

Minutes 17-23: proof the fix held

Usable: "After a valve or compressor repair the tech runs a trip test, records the trip time and air pressure on the job, and the next quarterly inspection confirms it." Fire protection companies may have a natural verification point in the scheduled inspection that follows a repair, so ask whether that inspection is linked back to the repair job or stored as a separate visit. Let the company describe its own proof: a logged test, a customer signature, a passed inspection, or simply no return trip within a window it names.

Minutes 23-30: owner and decision

Before the decision, say three things. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. You are a SourceX referral partner and may receive a reward if a qualifying license completes; SourceX pays it separately and it never reduces the company's payout. The dispatch project carries on the same whatever the answer.

Answers that end the meeting before minute 30

What you hearWhat it meansNote to record
"The old system was shut down last year and nothing was kept."No history remains to describeClosed
"Most of our work is subcontracted, and the subs keep their own records."The company may not hold or own the diagnosesNote the arrangement; stop
"Our OEM warranty program owns all service data."Rights likely sit with a third partyRecord for counsel; stop
"We have about 40 people."Below the 50 full-time baselineClosed
"We'd rather not."The owner has declinedClosed; the migration is unaffected

What the meeting decides

End with one outcome, a name beside it, and a date drawn from the company's own retirement plan where there is one.

OutcomeFits whenNext
Introduce nowRevisions and verification are recorded for several years, the owner is clear and opts inSend the annotated introduction email
Revisit by a dateThe archive plan or the old contract's end is still openFollow up before the documented read-only end
StopThe owner declines, or rights or size rule it outRecord why and close

For "introduce now", check 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: whether repeat-visit histories fit current dataset needs, the rights review on OEM and customer terms, de-identification and any offer.

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. Illustrative only: a $400,000 Actual Supplier Payout would mean a $70,000 default reward; the rewards page has every payment condition.

The field service histories data type describes the record in depth, the HVAC roll-up page shows where such companies cluster, assessing dispatch workflows in transportation covers a neighboring sector, and the portfolio review agenda uses a similar timed format for investors.

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 meeting closes on "introduce now", register as a partner, confirm the company on who qualifies and read the program terms before the old platform goes read-only.

  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 technicians be in the meeting?

Usually not. A senior technician or service manager can brief the service operations lead beforehand on how diagnoses are written. In the room, technicians tend to discuss the new mobile app rather than the old history.

What if the old platform is a homegrown tool or spreadsheets?

The agenda still works. The questions are about whether revisions, links and verification were recorded, not about a particular product. Note the tool's name and who maintains it.

Can I bring a sample work order to make the discussion concrete?

Bring the illustrative table on this page instead. Client work orders stay with the company; the meeting works from descriptions.

Sources

  1. learn.microsoft.com/en-us/dynamics365/field-service/work-order-r…
  2. learn.microsoft.com/en-us/dynamics365/field-service/incident-typ…
  3. learn.microsoft.com/en-us/dynamics365/field-service/work-order-s…
  4. refer.sourcex.si/terms

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