How to Hand a Lead From the Office to the Field

Why this matters

The best intake in the world is wasted if half of it never reaches the tech. A lead handed off badly shows up as a tech calling in from the driveway for the gate code, arriving without the likely part, or blindsided by a customer the office already knew was upset. The handoff is a translation job: the office turns a phone conversation into a record a tech can act on without calling back. Do it as a procedure and the field runs on rails. Skip it and every job starts with a scramble.

Step 1: Assemble the complete job record

Before the job leaves the office, the record should carry everything the tech needs and nothing they have to hunt for:

• The customer name, the service address, and a reachable number.
• The symptom in the customer's own words, plus what the system or item is and its rough age.
• Any history: prior visits, a recurring issue, work another shop touched.

If the office knows it, the record shows it. A fact that lives only in the dispatcher's head is a fact the tech does not have.

Step 2: Translate the complaint into an actionable scope

A customer's words are not a work order. "It is making a noise" needs to become "intermittent noise under load, customer thinks it started after the storm, unit is older." You are not diagnosing. You are shaping the raw complaint into something the tech can plan around, so they roll with the right tools and the right amount of time.

Step 3: Flag the landmines

The items that wreck a visit are rarely technical. Call them out explicitly:

• Access: gate code, dog, which door, parking, who will be home.
• Temperament: an already-frustrated customer, a prior complaint, a warranty situation.
• Money: whether a fee was quoted, whether there is a past-due balance, deposit status.

A tech who knows the customer is upset before knocking handles the door completely differently than one who finds out cold.

Step 4: Name the expected outcome

Tell the tech what a good result looks like on this job: a diagnosis and a quote, a specific repair, an estimate for a replacement. A tech who knows the goal manages the visit toward it. A tech handed only a symptom guesses at what the office promised, and often guesses wrong.

Step 5: Deliver it where the tech actually reads

The best record helps no one if it sits somewhere the tech does not look. Put the handoff in the one place your field uses, the job on their device or the dispatch note, not split across a text, a voicemail, and memory. Consistency of location is what makes the handoff reliable on a busy morning.

Step 6: Confirm receipt on anything unusual

For a routine job, the record is enough. For anything with a wrinkle - a hard access situation, an upset customer, a tight window - get a quick acknowledgment that the tech saw it. Silence is not confirmation. A ten-second "got it, I see the gate code" closes the gap that otherwise opens at the door.

Step 7: Close the loop back

The handoff is not one-way. When the tech finds that the job was not what the office described - bigger scope, wrong symptom, an access surprise - that comes back into the record. That feedback is how the next handoff gets better, and how the office learns which intake questions it is missing.

References

• See related: The Pre-Visit Call That Sets Up Success
• See related: Dispatching the Right Tech to the Right Job Decision Tree
• U.S. Small Business Administration, operations and communication guidance
• Trade-standard practice for dispatch-to-field handoff