FIELD NOTE 004 · LEAD HANDOFFS
A new lead needs one owner.
A new lead is not a shared task. Until one person or system owns the first response, it is a handoff waiting to be missed.
A call comes in while the team is on a job. A text arrives after hours. A website form reaches the inbox just as an estimate is being sent. The loss usually starts one step later, when everyone can see the lead but nobody is clearly responsible for moving it.
Shared visibility is not shared responsibility.
Many service businesses treat a new lead as a message that the whole team should notice. The office sees the form submission. A manager hears the voicemail. A technician gets copied on the text. That can feel collaborative, but it creates a gap at the exact moment the prospect is deciding whether the business is responsive.
The issue is not that several people have access to the information. The issue is that several people can reasonably assume someone else has acted. The lead becomes present in the business, but absent from any one person’s list.
A handoff needs a record and a return path.
A good handoff carries the information the next person needs to act without reopening the entire conversation. At a minimum, the record should show where the lead came from, what they asked for, what has already been promised, and what the next owner is expected to do.
It also needs a return path. If the first call goes unanswered, if a scheduler is unavailable, or if the job is outside the service area, the lead should not simply fall out of view. The process should state what happens next, who takes over, and when that decision is checked.
The first response is an operating promise.
The first response does not have to solve the customer’s whole problem. It does need to remove uncertainty. The prospect should know that the request reached a real business, what will happen next, and when they can expect that next step.
A response system should be designed around continuity, not just speed. The owner can acknowledge the request, confirm the relevant details, and either advance the conversation or set a specific next step. The business then has a record it can audit. The prospect has a reason to stay engaged.
Name the owner at arrival.
The most useful control point is the moment the lead enters the business. Assign an owner there, not after someone has time to look through the inbox. The assignment can be made by a person, by a schedule, or by a workflow rule. What matters is that it is visible and that it produces a next action.
A dependable lead handoff captures the source and request, identifies one current owner, states the next action with a time expectation, and defines what happens if that action cannot occur. Automation can reinforce this discipline. It cannot repair a business that has never decided who owns the response.
Turn the note into a build plan.
Use the assessment to map the handoffs, messages, and exception paths in your operation before you decide what to automate.
Request Assessment