Service Business Lead Handoff SOP
A free standard operating procedure for moving leads from receptionist, dispatcher, or AI intake into the right human owner quickly and cleanly.
sop resource
SOP
Owners, GMs, dispatch leads, office managers, and operators
thequietprotocol.com
A business can answer fast and still lose the lead if handoff is messy. Context disappears. Notes are incomplete. The team double-contacts the prospect or fails to contact them at all.
Service Business Lead Handoff SOP
A free standard operating procedure for moving leads from receptionist, dispatcher, or AI intake into the right human owner quickly and cleanly.
What This Asset Covers
- A minimal SOP for who owns the lead at each stage
- Required fields before handoff
- Escalation rules for urgent, high-value, or poor-fit inquiries
Use this when
- Leads are getting answered but not converted
- Multiple people touch the same inquiry
- You are adding AI or automation and need clean human ownership
Working Asset
Lead Handoff SOP
Use this SOP to keep leads from disappearing between intake, dispatch, scheduling, estimating, and follow-up.
Handoff Contract
A lead is not considered handed off until:
- one owner is named
- the next action is defined
- the due time is visible
- the receiving person confirms acceptance
If one of those four conditions is missing, the lead still belongs to intake.
Required Record Fields
- full name
- primary phone
- service address or market
- service/problem type
- urgency level
- source
- summary notes
- promised next step
- assigned owner
- due time for the next action
Intake-to-Owner Workflow
- Intake captures the lead in the system before the conversation ends.
- Intake tags urgency, service type, and fit.
- Intake assigns one receiving owner based on the routing rule.
- Receiving owner acknowledges the handoff.
- If acknowledgment does not happen inside the expected window, the lead escalates.
Ownership Rules
- Emergency work cannot sit unowned.
- Estimate leads need both an owner and a target follow-up date.
- Recovered missed calls do not go back into a generic pool.
- Referral-source leads should preserve the referral context in the notes.
- Once a lead is accepted, responsibility does not bounce back informally.
Escalation Rules
0-5 minutes: emergency, active-loss, or premium opportunities escalate to dispatch/on-call immediately15 minutes: unaccepted standard inbound lead escalates to office lead or manager60 minutes: warm estimate or consult lead without movement escalates to sales ownerEnd of day: any lead without a recorded next action gets reviewed before close
Acceptance Standards
The receiving owner should confirm:
- they saw the notes
- they understand the promised next step
- they know the deadline
- the record contains enough context to move without re-asking basic questions
If the record is incomplete, the owner rejects it with a missing-data reason instead of silently sitting on it.
QA Review
Review at least five handoffs per week and check:
- Was the owner assignment correct?
- Were the notes sufficient?
- Did the lead wait too long before action?
- Did the customer have to repeat themselves?
- Did the final outcome match the urgency and source quality?
Use the PDF for internal circulation, keep the source file if your team wants the editable working version, and use the live guide when you want the TQP framing around the asset.