Measurement guide · Lead response
Speed-to-lead for home services
Faster response only matters when the right person receives a useful answer and the operating record shows what happened next.
Measure six clocks and outcomes
Lead-created time
The timestamp from the original source—not the later CRM import. Preserve source, service requested, location, and consent context.
First automated acknowledgement
The first system message that confirms receipt and sets a truthful expectation. It is not a meaningful human response.
First meaningful human response
The first two-way attempt by a person who can answer, qualify, schedule, or escalate the request.
Contact attempts
Timestamp, channel, disposition, owner, and next action for each permissible attempt.
Booking time
When the customer accepts a valid appointment—not when a placeholder is created.
Disqualification
A reasoned outcome such as out of area, unsupported service, duplicate, spam, no capacity, or customer declined.
Build the instrumentation before the sequence
- Define eligibility. Separate serviceable homeowner requests from recruiting, vendor, spam, duplicate, and out-of-area traffic.
- Preserve timestamps. Retain source creation time, ingestion time, acknowledgement time, first human attempt, booking, and final outcome.
- Choose segments. Compare business-hours and after-hours response, channel, service line, urgency, geography, and lead source.
- Reconcile outcomes. Connect the response record to booking, dispatch, completion, completed revenue, and gross profit where the data permits.
A bounded response path
Receive
Validate required fields, remove obvious abuse, retain the original timestamp, and create one record.
Acknowledge
Confirm receipt through an approved channel and state what will happen next. Do not pretend the message is human.
Route
Assign by service area, trade, hours, urgency, and current capacity. Surface missing context rather than inventing it.
Respond
A human qualifies or books, handles exceptions, and records the result.
Human escalation and stop conditions
Human escalation is required for emergencies, safety or health language, complaints, vulnerable customers, uncertain serviceability, pricing or financing questions, unusual access, scheduling conflicts, and low-confidence model output. The human owner decides; the system queues context.
Stop conditions should halt automated outreach after an opt-out, reply, booking, disqualification, duplicate confirmation, complaint, explicit decline, invalid contact, manual hold, or the approved attempt limit. Capacity constraints should pause promises the operation cannot keep.
Evaluate change against the baseline
Compare like periods and segments. Track acknowledgement time, meaningful human response time, contact rate, booking rate, disqualification mix, cancellations, completed jobs, gross profit, complaints, and opt-outs. A faster median with worse completed-job outcomes is not an improvement.
Use the revenue leak checklist to check the surrounding handoffs, see the HVAC implementation boundaries, and model the opportunity with your own inputs.