This system map sits under the guide to urgent work order records, which walks through one exception record by record. Here the job is different: identify which system holds each record, what identifier connects it, and who can describe it, so a dispatch software consultant can tell a client whether its history can be joined at all.
The four systems behind one urgent dispatch call
Most field service companies spread the decision across four places, even when two of them come from the same vendor.
- Service desk or call log. Where the customer, store manager or site contact reports new facts. It holds the call or ticket ID, a timestamp, the caller and free-text notes. The question is whether the agent typed the work order number into the call.
- Dispatch platform. Where the work order and its priority live. The priority scheme itself is configuration: in Dynamics 365 Field Service, for example, a priority record carries a level of importance from 1 to 10 and a priority value from 1 to 100. The order record holds the current priority; the change history is a separate question.
- Scheduling board. Where bookings sit against technicians and time slots. A moved booking is the cost side of every upgrade: something else waits. The board may record that swap as a person's choice, a tool's suggestion or an ordinary reschedule, and only the first two say why.
- Technician mobile app. Where on-site time, completion notes, attachments and any follow-up job are logged. It usually stores the work order number by design, which makes it the most reliable node.
Some companies add a fifth: a contract tracker, if response targets are measured outside the dispatch platform.
System, record, linking key and owner
The table is the map in one view. Owners are roles, not names; the key column is what a reviewer would join on.
| System | Record | Linking key | Typical owner |
|---|---|---|---|
| Service desk | Escalation call or ticket, with time and caller | Call ID, plus the work order number if the agent recorded it | Service desk manager |
| Dispatch platform | Work order with current priority | Work order number | Service operations director |
| Dispatch platform audit log | Each priority change, with old value, new value, user and time | Work order number and change timestamp | Dispatch system administrator |
| Dispatch platform configuration | Priority definitions and target times in force | Priority code and effective date | Service operations director |
| Scheduling board | Booking moved to make room | Booking ID and the work order number it served | Scheduling lead |
| Response-time tracker | On-site and fix-time measures against target | Work order number and target record | Service operations director or contracts lead |
| Technician app | On-site time, completion note, attachments | Work order number | Field operations manager |
| Dispatch platform | Follow-up work order | Parent or related work order reference | Service operations director |
The audit log row deserves its own question. A platform can show today's priority on every job and still hold no trace of how it got there, if nobody switched on change logging for that field. Ask when logging began.
One fully joined case (Illustrative)
A fictional 640-person facilities contractor maintains refrigeration and HVAC for a grocery chain. Its priority scheme has three levels: P3 routine, P2 next day and P1 urgent with a four-hour on-site target. Nothing here describes a real company or a completed deal.
| Step | Time | System | Record | Key that joins it |
|---|---|---|---|---|
| Order raised | 07:40 | Dispatch platform | Work order WO-58213, "walk-in freezer reading high", P3 | WO-58213 |
| New fact | 08:25 | Service desk | Call C-11907: staff report a hissing sound and a chemical smell near the condenser | C-11907, with WO-58213 typed in the call |
| Upgrade | 08:31 | Dispatch audit log | Priority P3 to P1, reason "possible refrigerant leak", user: duty scheduler | WO-58213 and change time |
| Trade-off | 08:34 | Scheduling board | Booking B-30455 (a P2 filter change) moved to the next day | B-30455, served WO-57990 |
| Clock | 08:31 | Response-time tracker | P1 four-hour clock starts | WO-58213 target record |
| On site | 10:02 | Technician app | On site; area ventilated, unit isolated | WO-58213 |
| Completion | 11:15 | Technician app | Leaking valve replaced, pressure logged | WO-58213 |
| Outcome | Day 4 | Dispatch platform | Follow-up order to recheck pressure | Related to WO-58213 |
Every row joins because WO-58213 appears in each system, and the call agent happened to type it in. Remove that one entry from call C-11907 and the priority jump at 08:31 has no recorded reason outside the scheduler's own text.
Where the joins usually break
Four breaks recur, and each is worth one direct question to the owner:
- Calls with no work order number. Escalations taken on a supervisor's mobile phone leave no record at all. Ask what share of escalations reach the service desk.
- Priority stored as a value, not a history. Ask whether the platform audits the priority field and since when.
- Moved bookings with no link back. If the board simply reschedules, the bumped job looks like an ordinary delay. Ask whether the moved booking records why.
- Target records canceled by the change. Microsoft advises against driving response targets from frequently updated fields because a change can cancel the target record. A priority that moves mid-job is such a field, so ask whether the target history survives a priority jump.
A partner records the answer to each as yes, no or unknown, with who said so. The maintenance data page covers the asset-side records that often sit beside these four systems.
What the map tells you about qualification
A complete map shows which records exist, which systems and years they cover, and who owns each one. It does not show whether the company can license them. That needs an executive with authority, usually the COO, CFO or CEO, and the who can license decision tree shows how to reach that person from the service operations director. If a platform change is coming, the preservation timeline sets out what to inventory first.
The introduced company needs 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 90% of the data is in English. What stays unknown until SourceX reviews it: how client contracts affect site and incident records, the preparation effort, SourceX's current data needs and any offer. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application. The dispatch and service workflows guide covers routine dispatch.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the work order number runs through a client's service desk, dispatch log and technician app, register as a partner, confirm the company on who qualifies and read the program terms before you describe the map to SourceX.