Which first-visit failure recovery records help a company explain how exceptions were handled?
The records that matter show the misdiagnosis and the correction together. One closed work order says a job was done; a pair of linked jobs, with notes and parts on both, says what the first technician thought, why it was wrong and how the company caught it.
A first-visit failure is not always a mistake. Sometimes the part was not on the van, the customer was not on site, or the fault was intermittent. The exception that teaches the most is the one where everything needed was available and the diagnosis was still wrong, because the second visit records why.
Worked example: the right part was on the van, the wrong fault was diagnosed
Illustrative. A 260-person commercial HVAC service company maintains rooftop units for retail sites. Each van carries common motors, capacitors and contactors.
- Day 1, first visit. Ticket: "Store too warm, unit running." The technician's note reads "weak run capacitor, replaced, unit cooling at departure." Part history: one capacitor consumed from the van. Work order closed.
- Day 3, callback. The store reports the unit tripping again in the afternoon heat. The service desk opens a new ticket against the same site.
- Day 4, second visit. A senior technician notes "condenser fan motor overheating and cutting out; capacitor was a symptom." Part history: one fan motor consumed from the same van, which had carried a matching motor on day 1.
- Day 4, follow-up completion. The repair is marked complete, the store manager signs off, and the supervisor recodes the original job from "complete" to "failed first visit, misdiagnosis."
- Day 34, outcome check. No repeat call on the unit in 30 days.
The value is in steps 3 and 4: a written reason the first diagnosis was wrong, the part that proved it, and a supervisor's classification. That is an exception with an authorized action and a checked result, the same shape the exception workflows guide describes for purchasing. General work order assessment is covered in field service records and resolution notes; this page is only about the missed-fix pair.
Four kinds of first-visit failure, and what each record shows
Not every callback is the same exception. Asking the service director which kinds the company records, and how, says more about the history than any total.
| Failure kind | What the first visit shows | What the recovery adds | Strongest record |
|---|---|---|---|
| Misdiagnosis, part on hand | A part consumed, job closed | Corrected note, second part, supervisor recode | Paired technician notes |
| Part not on the van | Job left open or rescheduled | Part order, receipt, return visit | Part history and order record |
| Access or customer issue | Visit attempted, no work done | Rebooked visit, contact log | Scheduling history |
| Intermittent fault | Nothing found, job closed | Callback, monitoring, eventual fix | Repeat calls on one asset |
The first row is the one in the worked example, and it is the rarest to find well documented: it depends on the supervisor writing down that the first job failed, not just opening a second one.
How platforms hold the pair
Platforms differ in how they keep a missed fix and its recovery together, which is why the service director should be asked how callbacks were logged in each year rather than assuming one method.
- Work order status. In Microsoft Dynamics 365 Field Service, a work order is set to Completed by default when its booking is completed; the booking status setting "Status completes work order" can be turned off so follow-up work keeps the work order open. A company that turned it off may hold both visits on one record.
- Follow-up fields. The Dynamics work order table lists its follow-up fields (Follow Up Required, Is Follow-Up) as deprecated, so a company that relied on them may have changed how it flags callbacks partway through its history.
- Coded resolutions. Dynamics resolutions can be linked to incident types and suggested on work orders, so a coded diagnosis and a coded resolution may sit side by side. Free-text notes still carry most of the reasoning.
- Parts consumed. In Salesforce Field Service, a products consumed record on a work order reduces the stock of the linked product item, which can be a product at a location such as a van. That is how the part history on both visits can be tied to one van.
Microsoft Dynamics 365
SalesforceNone of this needs a partner to open a system. The service director can say which method applied in which years, and roughly how many callbacks were linked to an original job.
Does the company qualify, and what stays unknown?
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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. Subcontracted technicians do not count toward headcount.
What stays unknown until SourceX reviews it: what customer and site details must be removed, whether service contracts limit reuse, SourceX's current data needs for this record type, and any offer. The data rights explainer covers the review, and the field service histories page describes the record type in general.
Go deeper on first-visit failure recovery
- Reconstructing first-visit failures across systems: a system map of the links between work orders, part histories and callbacks.
- Who can license first-visit failure records: a short answer on which service and executive roles to introduce.
- Preserving first-visit failure history before a platform migration: an inventory checklist for the months before cutover.
- First-visit failure referral brief template: a fill-in template for the one-page introduction.
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 a client's callbacks still link back to the first visit with notes and parts on both, register as a partner, check the company against who qualifies, and read the program terms before the service director forwards your one-page note.