# Dispatch platform change: repeat-visit records | SourceX

Canonical: https://refer.sourcex.si/guides/moment-dispatch-platform-change-field-service-integrators
Last updated: 2026-11-05

Often they do in the legacy system, and the migration plan decides whether they survive. A repeat visit usually leaves a first diagnosis, a callback, a revised diagnosis, parts used and a closing record showing the fix held. Field service integrators can ask the owner whether that sequence stays attached to the work order and the asset, or whether only final statuses move to the new dispatch platform. If the history survives and the company qualifies, the owner may choose an introduction to SourceX.

## Do work orders retain diagnosis revisions and successful repair verification?

Ask it in those words, then listen for where the chain breaks. Three answers are common: the history is intact and linked to the asset; the revisions exist only as free text or attachments; or the old platform overwrote the diagnosis field each visit, so only the last one remains.

What a complete repeat-visit record looks like, in one Illustrative example: a 180-person commercial HVAC service company, one rooftop unit, two visits.

| Day | Event | Record left behind | Lost if only final status migrates? |
|---|---|---|---|
| Day 1 | Customer reports no cooling | Work order, problem code, asset ID | No, the work order header moves |
| Day 1 | Technician diagnoses a failed capacitor and replaces it | First diagnosis, part used, labor time | Often, if the diagnosis field is overwritten |
| Day 4 | Customer calls back: unit trips again | Callback flag or new work order linked to the first | Often, if links between work orders are not mapped |
| Day 5 | Second technician finds a refrigerant leak | Revised diagnosis, notes, photos | Often, if notes and attachments stay behind |
| Day 5 | Leak repaired, system recharged, readings logged | Resolution and test readings | Partly, readings are rarely mapped |
| Day 35 | No further callback within the company's window | Verification by absence of a callback | Yes, unless the history is queried later |

Platforms model this differently, so treat the table as a set of questions rather than a description of any one product. One documented example: Microsoft's Dynamics 365 Field Service separates the work order type (the general category) from incident types (the specific request), and notes that incident types support reporting such as the number of power failures for an asset category. Administrators can map several resolutions to one incident type, and the system suggests them on work order incidents. Booking statuses are kept separate from the work order system status, which runs from Unscheduled through Completed to Posted, and a booking status can be set to send the work order back to an earlier stage for follow-up. Whether a given client's platform keeps each revision, rather than the latest value, is the thing to check.

Why it is worth asking: a diagnosis that was wrong, then corrected, then verified is a reasoning trail with a known outcome. Records like that are hard to find in public, and they are the kind of operational history SourceX asks about when it reviews a company for AI training and evaluation data. The [field service histories](/data-types/field-service-histories) page describes the record type in more depth, and [how to assess resolution notes](/guides/how-to-assess-field-service-records-and-resolution-notes) explains what makes notes useful.

## Why is repeat-visit diagnostic history easy to overlook at a dispatch change?

Because the project is scoped around tomorrow's dispatch, not yesterday's diagnoses. Replacement work centers on scheduling, routing, mobile forms, technician adoption and integrations with billing. Migration teams typically load open work orders, customers, assets, agreements and price lists, then leave closed history in the old system or a flat export.

Three habits make the gap wider. Callbacks are often logged as new work orders with no link to the original job, so the repeat visit looks like an unrelated call once exported. Diagnosis fields on some legacy tools hold one value per work order, and a second technician's finding replaces the first. And the evidence that a fix held, a passed reading or the absence of a callback within the company's window, is rarely a field at all; it exists only if someone can still query the history later.

None of this is anyone's mistake. The record that shows how a diagnosis changed between visits is not needed to dispatch a technician on Monday, so it has no owner on the project plan. An integrator who raises it is often doing the company a favor regardless of what follows.

## Four metadata questions for the owner

Stay at metadata level: what exists, how much, how long, which system and who owns it. Four questions cover the kept question without touching a record:

1. **Revisions or last value?** When a second visit changes the diagnosis, does the old platform keep both entries with dates, or overwrite the first?
2. **Linked or loose?** Are callbacks and follow-ups linked to the original work order and asset, or created as unrelated orders?
3. **How is a fix verified?** What does the company itself record as proof the repair held: a resolution code, a customer sign-off, a test reading, or no callback within a set window?
4. **How much, and whose?** Roughly how many years of closed work orders exist, across which service lines, and do customer, OEM or warranty contracts limit how they can be reused?

Record the answers as yes, no or unknown, with ranges rather than exact counts. Do not request exports, screenshots or sample work orders; SourceX handles any review of records directly with the company. If telematics sits beside the dispatch tool, as on the [Samsara export page](/systems/samsara-export-data), note it as a linked system and leave its value to the review. The [field service work order field guide](/guides/a-partner-field-guide-to-finding-companies-with-field-service-work-orders) covers which kinds of companies tend to hold this history in the first place.

## How do you disclose the reward and get the owner's permission?

Ask before you mention SourceX, and disclose your interest at the same time. For example: "Separately from the migration, that history may have value to the company. May I mention one option? I should tell you I am a referral partner and may receive a reward if it goes ahead."

If the owner agrees, explain that SourceX licenses approved business data directly from companies for AI training and evaluation and pays the company, and that your reward is funded separately and never reduces the company's payout. If the owner declines, the archive question is still on the record before cutover, which is good project practice.

Describe the reward exactly. The default is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, the amount SourceX actually pays the company, with no cap in total. Illustrative only: a $400,000 payout would mean a $70,000 reward. 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.](/rewards) sets out.

## Who owns service records, and who can authorize a licensing discussion?

The service company normally owns its work order history, but customer agreements, OEM warranty programs and service contracts can restrict reuse, which is for the company's counsel to judge. The person who can open a licensing discussion is usually the owner, CEO or COO, not the dispatch manager running the project.

| What you can note | Who confirms it | What stays unknown until SourceX reviews it |
|---|---|---|
| Record types and years of history | Service operations or IT | Whether the records fit current dataset demand |
| Whether contracts limit reuse | The company's counsel | The rights review outcome |
| The authorized decision-maker | Owner or executive team | Any offer, its terms and timing |
| Headcount at peak | Owner or HR | Final eligibility confirmation |

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact; [who qualifies](/who-qualifies) has the detail. 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.

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. IT and systems integrators can also read the [IT consulting firm page](/industries/refer-it-consulting-firm-data-licensing), and the [partner hub](/for) lists other roles.

## Go deeper on dispatch platform change records

- [Dispatch platform change meeting agenda](/resources/dispatch-platform-change-meeting-agenda): a timed agenda for the owner meeting where repeat-visit history and the referral option are raised.
- [Dispatch platform change archive context checklist](/resources/dispatch-platform-change-archive-context-checklist): a checklist of dates, scope and linked systems to confirm before the legacy platform is retired.
- [Dispatch platform change introduction email](/resources/dispatch-platform-change-introduction-email): a ready-to-adapt email for introducing an opted-in owner to SourceX.

## 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 a client's repeat-visit history survives the dispatch change and the owner wants to explore it, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and keep the [program terms](/terms) open while you prepare the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://learn.microsoft.com/en-us/dynamics365/field-service/work-order-resolutions
- https://learn.microsoft.com/en-us/dynamics365/field-service/incident-type-overview
- https://learn.microsoft.com/en-us/dynamics365/field-service/work-order-status-booking-status
