Pre-Diagnosing From a Customer's Photo Before You Roll a Truck (Decision Tree)

Why this matters

A photo lands in the intake inbox before the truck even leaves the yard, and the decision you make from it, roll now with a guess, ask for more first, or just schedule and diagnose on arrival, decides whether this is a one-trip job or a two-trip job. Guess wrong from a bad photo and you show up with the wrong part and a customer who now doubts you before you have said a word. This tree walks the call from "photo arrived" to "truck rolls with a plan."

Start here: is there a safety flag in the frame

Before you read the photo for diagnostic value, scan it for danger. This overrides everything else below.

• If the photo shows scorching, melted material, active smoke, sparking, standing water near an electrical panel, or anything the customer describes as smelling like gas or burning, stop pre-diagnosing. Give the safety instruction now (de-energize, evacuate, call emergency services as the hazard requires) and treat this as an emergency dispatch, not a scheduling decision. See related: Smell of Gas or Burning: Response Decision Tree.
• If the photo shows a routine mechanical or cosmetic issue with no hazard signs, continue below.

Step 1: is the photo actually usable

A blurry, dark, or too-close photo tells you nothing. Judge it honestly before you build a plan on it.

• If the nameplate or unit type is unreadable and the failure area is out of focus, do not guess. Text back a specific request: a wide shot, a nameplate shot, and a close focused shot of the problem. Two extra minutes of the customer's time saves you a second trip.
• If the photo is clear enough to identify the unit type and see the failure area, move to step 2.

Step 2: does the photo show a defined, known failure pattern

Some visual patterns are close to conclusive on their own; others are only suggestive.

• If the photo shows a component that is clearly cracked, melted, corroded through, or physically separated, that is a strong lead. Note the type and stage the likely replacement part, but still confirm the surrounding cause on site (a cracked part is a symptom too; ask what stressed it).
• If the photo shows discoloration, staining, or wear that is consistent with several different causes (a scorch mark that could be a loose connection or an overloaded circuit, a stain that could come from several sources), do not commit to one part. Note the candidates and plan to bring general diagnostic tools rather than a single guessed part.
• If the photo shows nothing visibly wrong at all and the complaint is behavioral (a noise, an intermittent failure, something that "just stopped working"), the photo is not going to pre-diagnose this one. Skip to step 4.

Step 3: does the photo tell you enough about access and logistics

Even a diagnostically weak photo can save you time on logistics.

• If the wide shot shows a tight, high, or otherwise awkward access point, block extra time and bring a helper or the right ladder, regardless of what the fault turns out to be.
• If the photo shows the unit's general condition (very old, clearly neglected, clearly well maintained), let that adjust your expectation of what else might be found, without letting it become the diagnosis itself.

Step 4: decide what actually happens next

Weigh what steps 1 through 3 gave you and land on one of three outcomes.

• Confident pre-diagnosis: the photo clearly shows a known failure pattern with no ambiguity. Stage the likely part, quote a scope that is explicitly "pending on-site confirmation," and roll.
• Partial pre-diagnosis: the photo narrows the field but does not name one clear cause. Bring the top two or three likely parts and general test equipment, and set the customer's expectation that you are diagnosing on arrival, not just installing.
• No pre-diagnosis possible: the photo showed access or context only, or was unusable and the customer could not get a better one. Schedule normally and diagnose fresh on site. This is a fine, honest outcome. A photo that does not conclude anything did not fail; it told you the truth, which is that this one needs eyes in person.

The recap

1. Scan for a hazard first. If present, this is not a scheduling decision.
2. Reject an unusable photo and ask for a specific re-shoot.
3. Read the failure pattern: conclusive, suggestive, or absent.
4. Read the access and context separately from the fault itself.
5. Land on confident, partial, or no pre-diagnosis, and never promise a fixed price off a photo alone.

References

• Trade-standard practice for service-call triage and parts staging
• See related: Reading the Customer's Photos Before Arrival; The Questions That Get a Useful Video From a Customer; Remote Triage: Send a Tech Now or Schedule Later