Home-services lead routing is not the same as lead generation. It begins after a request arrives and answers an operational question: what does the office or dispatcher need to know, and who owns the next action?
The checklist is designed for HVAC, plumbing, electrical, roofing and multi-trade operators. It does not replace emergency procedures, licensed judgment or the company's field-service platform.
Separate service intent before prioritizing
Capture service address or ZIP code, service line, repair or replacement intent, equipment or property context, requested timing, preferred contact method and the original message. For multi-trade companies, record the routing reason so dispatch can verify it.
Do not turn emotional wording into a safety conclusion. The company should define phrases that trigger a prominent operator alert and the approved instruction shown to the customer. A human owns the safety-sensitive decision.
Apply territory and capacity rules visibly
Territory checks can use ZIP code, county, radius, licensed state or branch coverage. Capacity may depend on service line, business hours, on-call coverage or appointment type. Record the rule that matched instead of hiding it inside an automation history.
If several branches or technicians could own the request, use an agreed queue or review step. A guessed assignment is worse than a visible unassigned exception.
Design for duplicate and integration failure
A customer may submit a form, call and reply to the acknowledgement. Match those events conservatively so one request does not create three opportunities while unrelated household members are not merged by assumption.
If the CRM or field-service write fails, preserve the source event and alert an owner. Retrying should create the intended state once, not duplicate the job every time a webhook is delivered.
Measure the hand-off before the booking outcome
Track captured, acknowledged, assigned, contacted, booked or closed, plus the reason for no-fit or loss. Start with missing-owner rate, overdue next actions, failed writes and routing corrections.
Booking or revenue change can be evaluated later from the operator's own records. The intake checklist proves that the process is observable; it does not by itself prove a commercial result.