The Remote Triage Call SOP

Purpose

To run a structured remote diagnostic contact when a site visit is not the assumed outcome, so that every such call ends in one of five defined dispositions with a stated confidence tier, and so that whatever is learned survives the call in writing. This SOP exists because remote contacts otherwise default to one of two failure states: a truck rolled that did not need to roll, or a customer talked out of a visit they did need.

Scope

Applies to any contact where the customer or their representative is at the equipment and no technician is, and where the outcome is genuinely open: unreachable or out-of-area properties, seasonal sites with only a caretaker present, landlord or property-manager calls with a tenant on site, warranty and support calls, and any call where the customer is asking whether they need a visit at all.

Does not apply to anything with an immediate life-safety signal. A smell of gas or fuel, smoke, fire, a shock, water reaching electrical equipment, or a person injured moves straight to the emergency protocol. Nothing in this SOP is run while any of those is live.

Also does not apply to a call that is purely booking. If the customer knows what they want and a visit is already agreed, take the duty-cycle intake questions and book it. Do not run a full triage on a job that is already scoped.

Roles and responsibilities

Response standards

Set these as concrete defaults and tune them to your shop.

• Safety-flagged contact: handled immediately at intake, no callback delay, no hold queue.
• Routine remote contact: a technician on the line within 60 minutes during business hours, and within 4 hours otherwise.
• Single contact length: cap at 20 minutes. Past that, assign observations and schedule the next contact rather than pushing on with a tired customer.
• Observation window: 30 minutes is the working default for any accumulation or leak observation. Shorter windows produce false negatives.
• Remote rounds before booking: two. If two rounds of designed observations have not reached a usable disposition, book the visit. A third round is almost always the shop avoiding a truck roll it has already earned.
• Loop closed: within 2 business days of the field outcome being known.

Procedure

Step 1: Run the safety screen before anything else

Ask, in this order, before any diagnostic conversation: any smell of gas or fuel, any smoke or burning smell, any water near electrical equipment, has anyone had a shock, is anyone hurt.

A yes to fuel or gas: everyone leaves the building immediately, no switches touched, no lights, no phone use inside, call the gas supplier or emergency services from outside. The triage call ends there.

A yes to water plus electricity: nobody touches the equipment or nearby metalwork, power is isolated at the panel only by someone competent to do it, otherwise not at all.

A yes to smoke, burning smell, or a shock: stop using the equipment, isolate if it can be done safely from a distance, and this becomes a visit, not a triage.

Record the screen result in the record even when everything is a no. A screen that was run and documented is what protects the shop later.

Step 2: Open the remote record

One record per fault, not per call. It carries: who is at the site and their relationship to the equipment, the best contact method and hours, the complaint verbatim, every observation with its timestamp and who made it, what each observation eliminated, the current tier, and the current disposition.

Remote work runs across days and often across people. Anything not in the record does not exist.

Step 3: Capture the complaint in the customer's own words

Write the sentence they actually said before anyone translates it. Then write your translation on the next line, marked as yours. When a case later stops making sense, the raw sentence is what you go back to, and shops that only keep the translation have nothing to return to.

Step 4: Establish the baseline

Request, in this order: a photograph of the whole unit from a step back, the data plate, the immediate surroundings, and anything connected. Then have the customer describe what is connected to it in their own words.

Do this before fault questions. Without a picture of the installation, later answers about location and connection are uninterpretable.

Step 5: Run the timing and duty-cycle questions

When it comes on and when it stops for the day. How often it starts and how long a run lasts. How long after starting the trouble appears. How long before it works again and whether anyone has to touch anything. What changed in the last few months.

These five convert a story into a duty cycle, an incubation time, and a recovery pattern, which are the three numbers that decide whether a visit even can find the fault and how long that visit has to be.

Step 6: Assign observations rather than asking questions

Each round, assign no more than three observations. Every one must return a binary, a count, a duration, or a comparison, and every one must be performable standing on the floor with the covers on, nothing hot or live touched.

Sequence them so each one eliminates as much as possible. The standard opening split is whether the system attempts to operate and fails, or does not attempt at all.

Confirm each assignment back before ending the contact: what they will do, when, and how they will report it.

Step 7: Grade the conclusion tier

Before choosing a disposition, write the tier in the record.

Grading is not optional and it is not a formality. The tier, not the technician's confidence, governs step 8.

Step 8: Choose one of five dispositions

Step 9: Deliver the conclusion in writing

Four elements, every time: what you believe, how sure you are and at what tier, what you are recommending, and the single thing that would change your mind. Send it, do not just say it.

Add explicitly what you did not check and cannot know from a distance, including that remote reasoning finds one explanation and cannot rule out a second fault.

Step 10: Build the dispatch packet

When the disposition is a visit, the packet carries: the complaint verbatim, the duty cycle as a number, the incubation time, the recovery pattern, the family concluded and the families eliminated with the observation that eliminated each, the required test duration at 1.5 times the incubation time of actual run time, and the parts implied by the family.

The test-duration line is the one that gets skipped and it is the one that prevents the clean short visit that finds nothing.

Step 11: Close the loop

Within 2 business days of the field outcome, the field technician records what was actually found, and the remote record is updated with whether the family was correct. This is the only mechanism that makes remote work more accurate over time, and it is the first thing a busy shop drops.

A pass through the procedure

A property manager calls about a tenant reporting that a heating appliance runs and then stops, repeatedly, and the property is a long drive out.

Safety screen: no fuel smell, no smoke, no water, no shock. Recorded.

Complaint verbatim: "it comes on, runs a bit, then quits, and it keeps doing that all evening."

Baseline photographs came back showing the unit and its data plate, plus the room it sits in.

Timing questions produced the numbers. Energized all day. The tenant counted the stops: 6 starts in one hour during the evening, each run lasting around 5 minutes, so roughly 30 minutes of run in the hour, about 50 percent duty. The trouble is not a single failure after a long run, it is the pattern itself. Recovery is immediate, nothing gets touched, it just goes again. Nothing changed in the last few months except the season.

Observations assigned, three of them. First, does the room reach the setting on the control, or does it stay below it: it stays below. Second, with a hand held near the outlet while running, is it warm the whole time it runs or does it fade: it is warm the whole run. Third, count the starts again in the middle of the day rather than the evening: 2 starts in the hour, not 6.

What that eliminated. The unit produces output the whole time it runs, which pushes against an output fault. The cycling rate scales with demand, twice in a mild hour against six times in a cold evening, which is exactly what a system that is cycling on a limit rather than satisfying a setpoint looks like, and it is also what an under-capacity system looks like. Those two remained.

Tier reached: family, not member. Disposition: book a scoped visit, with a packet that named both surviving explanations, the observations that eliminated the others, and a required test duration long enough to see several full cycles rather than one. No part ordered, because the two surviving explanations imply entirely different parts.

Loop closed four days later with the field finding recorded against the remote family. That single line is what lets the next person running this SOP trust the method.

Records and retention

Keep the remote record attached to the job, with the photographs, for the same period as any other service record. Keep the safety screen result permanently with the job. Where a stop-use instruction was given, keep the written version of it, because that document is the shop's protection if the customer keeps using the equipment anyway.

Common failures of this SOP

Grading the tier after choosing the disposition. People decide to ship a part and then write Member in the box. Grade first, in the record, then read the disposition off the table.

Skipping the loop close. Accuracy stops improving immediately and nobody notices for a year.

Running a third and fourth remote round. Each extra round costs the customer's patience and rarely adds a tier. Two rounds, then book.

Letting the safety screen become a formality. Read the questions, do not summarize them, and record the answers. A screen that is assumed rather than asked is worth nothing when it matters.

References

• OSHA guidance on hazardous energy control and stop-work authority when a hazard is suspected
• Manufacturer documentation on normal operating behavior, cycling, and shutdown procedures
• Trade-standard practice for service triage, dispatch documentation, and record retention
• See related: What You Can and Cannot Conclude Without Being On Site
• See related: The Duty-Cycle Questions to Ask Before You Drive Out