This guide is for people who have run or rebuilt dispatch from the inside: field service consultants, scheduling software implementers, former operations directors who now advise, and owners of service businesses who sit on peer boards. It answers one question before any introduction: whose account of a dispatched job can you trust, and whose permission does each part of it need?
A dispatched job, told stage by stage
The Bureau of Labor Statistics defines dispatchers outside police, fire and ambulance work as people who schedule and dispatch workers, work crews, equipment or service vehicles, including for normal installation, service or emergency repairs carried out away from the place of business. A dispatch history is the trail that work leaves. For one job it typically runs through six stages:
- Call. A customer, a contract or a maintenance schedule creates the request, with a priority and a promised window.
- Assign. A dispatcher picks a technician by skill, location and availability.
- Reassign. Plans change: an emergency jumps the queue, a part is missing, a customer cancels.
- Visit. The technician arrives, diagnoses, works and writes notes.
- Close-out. Parts, hours and the outcome are booked, and the job is invoiced or claimed under warranty.
- Return. If the fix fails, someone books a second visit.
The reasoning sits in stages 3 and 6, and those are the stages most likely to be missing. SourceX's field service guide notes that the scheduling board records where technicians went but rarely why a dispatcher changed the plan, that reassignments made by phone and skill judgments kept in a dispatcher's head go unrecorded, and that many systems book a return trip as a brand-new work order. A history can look complete and still hide its most useful decisions.
Four desks, four partial accounts
Each role sees the job through its own screen, and each would describe the history differently if you asked.
| Role | Stages it knows firsthand | What it usually cannot tell you |
|---|---|---|
| Dispatcher | Call, assign, reassign | What the technician found, and whether the fix lasted |
| Technician | Visit, close-out notes | Why the job was routed to them, or what happened after they left |
| Billing or warranty desk | Close-out, return | The reasoning behind either visit |
| Service operations director | All six, at a summary level | Rights in contracts, and whether the company wants to talk |
| CEO | None in detail | The CEO never needs to narrate the history; the CEO decides whether the company talks |
The last row matters most. In this program the yes to a licensing discussion, and the signature, belong to the CEO. A sponsor who can tell the whole story is valuable precisely because the CEO does not have to know it.
The dispatch-context sponsor interview
Ten questions, asked of the person most likely to know the whole chain. Write down the date and who answered. Nothing in it needs an export, a screenshot or a login.
| # | Question | Why you ask it | Answer that supports an introduction | Answer that narrows or pauses it |
|---|---|---|---|---|
| 1 | Walk me through one ordinary job from call to invoice. Who touches it? | Tests whether this person really knows the chain | Names a role and a system at every stage | Skips stages or guesses |
| 2 | Where does the reason for a reassignment get written down? | Stage 3 holds the dispatcher's judgment | A required field or note in the dispatch system | "In my head" or "on the phone" |
| 3 | How is a return visit tied to the first one? | Stage 6 shows whether fixes held | Linked to the original job number | Booked as an unrelated new job |
| 4 | Which system holds each stage, and since which year? | History depth and gaps | One system, or two with a dated migration | Nobody knows what happened to the old system |
| 5 | Who administers each system today? | Finds the custodian | An internal administrator | A vendor or a client runs it |
| 6 | Which jobs are dispatched or performed by someone else? | Separates outside work | Few, and they are identifiable | Warranty portals, subcontractors or a call center hold a large share |
| 7 | Do any jobs live in a customer's own work order system? | Client-owned records are usually not a fit | No | Yes, for some key accounts |
| 8 | Have these records ever been licensed for AI training? | Data already licensed for that purpose is not eligible | No | Yes: stop here |
| 9 | Does the CEO know this conversation is happening? | Introductions without the decision maker's knowledge are usually not a fit | Yes, or the sponsor will raise it | The sponsor wants to keep it quiet |
| 10 | Has the company already applied to, or corresponded with, SourceX? | Earlier contact makes a company a duplicate under section 3 of the terms | Not that anyone knows | Yes: SourceX already knows the company |
Score each of the six stages on what the interview produced: narrated, owner named; narrated, owner unknown; or nobody can narrate. A history worth introducing has the company's own reasoning stages, reassignment and return, narrated with an owner named, and a sponsor who will take the idea to the CEO. Question 8 or a "keep it quiet" answer to question 9 ends the exercise whatever the other scores say.
Original work, mixed crews and an unclear owner (Illustrative)
Illustrative. Three generic service companies with invented details; no outcome is implied.
A. The company's own story. A 260-person commercial HVAC service company employs its own dispatchers and technicians and has run one field service platform since 2016. Since 2019 a reassignment cannot be saved without a reason code, and returns link to the original job. The director of service operations narrates all six stages and names the system administrator. Every stage scores "narrated, owner named". The director briefs the CEO, and if the CEO wants the conversation, the company applies through your partner link.
B. Mixed third-party content. A 180-person appliance repair network takes about 40% of its jobs from manufacturers' warranty programs, which dispatch through each manufacturer's own portal, and uses subcontracted technicians in rural areas who file notes in their own apps. The in-house jobs, dispatched and performed by the company and recorded in its own system, are its operating history. The warranty-portal jobs and the subcontractors' notes are not simply its own, and the sponsor says so up front. That candor matters downstream too: subcategory MAP 4.1 of NIST's AI Risk Management Framework calls for "Approaches for mapping AI technology and legal risks of its components – including the use of third-party data or software" to be in place, followed and documented. Describing the outside share at the start saves everyone a later surprise.
C. An uncertain owner. A 340-person facilities maintenance company dispatched its own daytime work but used an outside answering service for nights and weekends from 2017 to 2022. The night calls, priorities and first assignments sit in the answering service's software, and nobody at the company knows what the contract says about those records. Daytime stages score well; the night share scores "nobody can narrate" on ownership. If the CEO wants to explore it, the introduction goes ahead with the open question written down, and counsel and SourceX's rights review answer it.
Who owns each part, and where it came from
The interview gives you names; the company decides what they mean. The sponsor narrates and sponsors internally. System administrators confirm fields, years and migrations but answer no rights question. Counsel reads warranty program agreements, subcontractor contracts, answering-service terms and key-account service contracts. The CEO decides whether the company talks about licensing and signs for it.
SourceX's screening guidance counts a company as holding rights when it owns the material, or can license it without breaking a client's confidence, an employee's privacy or a contract with someone else. Dispatch histories touch all three: customers' addresses and access notes, technicians' names and locations, and the terms of the programs that feed the company work. Note where each appears; preparation and review deal with them later.
The fit facts sit in front of the story. The company needs 50 or more full-time employees at its peak, counting its own staff and leaving out subcontracted technicians, along with a documented operating history, rights to license and a CEO who agrees to talk. 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. Whether a dispatch history matches what a current SourceX program wants is decided in review, not in the interview. For the record types themselves, see field service histories and the guide to assessing field service records and resolution notes.
The note you send the sponsor, and what it leaves out
A short message before the interview keeps it bounded. Something like:
I'd like 30 minutes to understand how a job moves through your dispatch, from the call to the invoice, and who keeps each part of the record. I won't ask to see any jobs, screens or exports. If it looks relevant, the next step is for you to raise it with your CEO, and only if they want to talk.
Then keep to it:
- Ask for counts and years, not samples: roughly how many jobs a year, and since when.
- Ask which system holds each stage, not for access to any of them.
- Ask who did the work, not who the customers were.
- Write down any outside share (warranty programs, subcontractors, answering services, customer systems) as a fact about the history, not a problem to solve.
- If the sponsor offers a file anyway, say no and keep talking; the description is the deliverable.
When the company is mid-migration between dispatch platforms, timing changes the conversation; the dispatch platform change guide covers that moment, and AI dispatching explains which dispatcher decisions AI developers learn from.
When a fluent narrator is the wrong guide
- The storyteller who never owned the stage. A long-serving dispatcher can describe the warranty desk vividly and still be wrong about what it records. Confirm each stage with the role that keeps it.
- Memory instead of records. A sponsor may describe how jobs should flow. Question 2 and question 3 test whether the reasoning was actually written down.
- Only the current system. People remember the platform they use now. Ask directly about what came before and whether it was migrated, archived or switched off.
- Demand is not in the interview. A perfectly narrated history can still fall outside what SourceX needs right now; that is a review question.
- Nothing to benchmark against. SourceX publishes no rate at which dispatch histories turn into introductions or licenses, so keep a tally of your own: interviews held, stages scored "narrated, owner named" and CEOs who agreed. Figures across the program are not yet published.
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 sponsor can narrate the reassignment and return stages with an owner named and the CEO wants to talk, open a partner account, check the company once more against who qualifies and read the program terms, including the requirement to sign the Channel Partner Agreement before you submit. More sector material sits on the construction and field services page and in the guides hub.