Service dispatch histories: who knows the full operating story? Rarely one person, so a ten-question sponsor interview maps which role holds each stage of a job before anyone asks the CEO

Short answer

Usually nobody holds the whole story. The dispatcher knows why a job moved, the technician knows what was found on site, and billing or warranty staff know whether the fix held. The person to find first is a sponsor who can walk one job from call to invoice and name who owns every stage, often a service operations director or dispatch manager. That sponsor narrates; the CEO decides whether the company discusses licensing its records. Run the conversation at metadata level and leave every record where it is.

Visual briefFull-size diagram
A six-stage dispatched job, from call to return visit, with coverage bars showing that the dispatcher, the technician and billing staff each know only part of it, a dashed sponsor bar spanning all six stages, a warning that reassignment reasons often go unwritten, and a separate box saying the CEO authorizes.
Illustrative coverage of one dispatched job by role; real companies split the stages differently.

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:

  1. Call. A customer, a contract or a maintenance schedule creates the request, with a priority and a promised window.
  2. Assign. A dispatcher picks a technician by skill, location and availability.
  3. Reassign. Plans change: an emergency jumps the queue, a part is missing, a customer cancels.
  4. Visit. The technician arrives, diagnoses, works and writes notes.
  5. Close-out. Parts, hours and the outcome are booked, and the job is invoiced or claimed under warranty.
  6. 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.

RoleStages it knows firsthandWhat it usually cannot tell you
DispatcherCall, assign, reassignWhat the technician found, and whether the fix lasted
TechnicianVisit, close-out notesWhy the job was routed to them, or what happened after they left
Billing or warranty deskClose-out, returnThe reasoning behind either visit
Service operations directorAll six, at a summary levelRights in contracts, and whether the company wants to talk
CEONone in detailThe 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.

#QuestionWhy you ask itAnswer that supports an introductionAnswer that narrows or pauses it
1Walk me through one ordinary job from call to invoice. Who touches it?Tests whether this person really knows the chainNames a role and a system at every stageSkips stages or guesses
2Where does the reason for a reassignment get written down?Stage 3 holds the dispatcher's judgmentA required field or note in the dispatch system"In my head" or "on the phone"
3How is a return visit tied to the first one?Stage 6 shows whether fixes heldLinked to the original job numberBooked as an unrelated new job
4Which system holds each stage, and since which year?History depth and gapsOne system, or two with a dated migrationNobody knows what happened to the old system
5Who administers each system today?Finds the custodianAn internal administratorA vendor or a client runs it
6Which jobs are dispatched or performed by someone else?Separates outside workFew, and they are identifiableWarranty portals, subcontractors or a call center hold a large share
7Do any jobs live in a customer's own work order system?Client-owned records are usually not a fitNoYes, for some key accounts
8Have these records ever been licensed for AI training?Data already licensed for that purpose is not eligibleNoYes: stop here
9Does the CEO know this conversation is happening?Introductions without the decision maker's knowledge are usually not a fitYes, or the sponsor will raise itThe sponsor wants to keep it quiet
10Has the company already applied to, or corresponded with, SourceX?Earlier contact makes a company a duplicate under section 3 of the termsNot that anyone knowsYes: 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:

  1. Ask for counts and years, not samples: roughly how many jobs a year, and since when.
  2. Ask which system holds each stage, not for access to any of them.
  3. Ask who did the work, not who the customers were.
  4. Write down any outside share (warranty programs, subcontractors, answering services, customer systems) as a fact about the history, not a problem to solve.
  5. 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.

  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

Can a former dispatch manager who left the company act as the sponsor?

They can explain how the work used to run, which helps you decide whether a conversation is worth asking for. They cannot speak for the company today, so someone currently inside it has to confirm the systems and years, and the current CEO decides whether to talk.

Do dispatch histories need GPS traces or call recordings to be interesting?

No. The interview is about the sequence of decisions on a job and who recorded them. Location traces and recordings raise their own privacy and consent questions, so note whether they exist and leave them for the company and SourceX's review to scope.

What if the sponsor wants to show me the scheduling board to prove the history is rich?

Thank them and ask for a verbal description instead: which stages are written down, since when and in which system. A partner who has seen a client's live board has seen technician and customer details that were never meant to leave the company.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. bls.gov/oes/2023/may/oes435032.htm
  4. sourcex.si/insights/ai-for-field-service-companies-disp…
  5. nvlpubs.nist.gov/nistpubs/ai/nist.ai.100-1.pdf
  6. sourcex.si/how-it-works

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