NZLeads Support
Auto-Respond Team publishes practical lead response resources for service businesses. Auto-Respond supports configured workflows for Yelp, Thumbtack, Facebook, Google Local Services Ads, Instagram, Angi, and Nextdoor.
The Thumbtack response lag fieldbook
A practical workbook for measuring delay, finding the bottleneck, and handing leads off safely
For service team operators
Start with one clock
Record five moments for every lead
- Lead received
- Alert delivered
- First review
- First reply
- Human owner assigned
Do not collapse these into one "response time" number. Each gap points to a different fix.
The lag ladder
| Segment | Calculation | What it tests |
|---|---|---|
| Alert lag | alert delivered - lead received | Notification path |
| Review lag | first review - alert delivered | Coverage and attention |
| Reply lag | first reply - first review | Decision and drafting |
| Handoff lag | owner assigned - first reply | Ownership clarity |
Use timestamps from one system of record. Keep time zones explicit.
The shift log
Copy this row for each lead
| Field | Entry |
|---|---|
| Lead ID | |
| Received at | |
| Alert at | |
| Reviewed at | |
| Replied at | |
| Assigned at | |
| Route | automated / human / mixed |
| Exception | |
| Outcome |
Measure the workflow, not the person.
Separate normal work from exceptions
Tag before you compare
- New inquiry
- Duplicate or spam
- Outside service area
- Missing job details
- Safety or compliance concern
- Price or scope exception
- Existing customer follow-up
Averages become misleading when exceptions sit in the same bucket as routine leads.
Read the pattern
Fast alert, slow review
Coverage gap. Check who owns the notification window.
Fast review, slow reply
Decision gap. Check missing rules, prices, or job details.
Fast reply, slow assignment
Handoff gap. Check ownership and acceptance.
Every stage slow
System or staffing issue. Test delivery before changing scripts.
The safe handoff card
A handoff is complete only when the next owner has:
- Lead ID and contact channel
- Customer request in plain language
- What was already sent
- Missing facts and open questions
- Agreed next action
- Acceptance timestamp
No named owner means the handoff is still open.
Daily review, ten minutes
- Count leads with all five timestamps.
- Find the slowest segment by median.
- Review the three longest delays.
- Check whether exception tags explain them.
- Pick one workflow change for tomorrow.
- Set a date to judge the change.
Do not rewrite the whole process after one unusual lead.
Change log
| Date | Bottleneck | Change | Expected signal | Review date |
|---|---|---|---|---|
Stop rule
Keep the change only if the intended lag segment improves without creating missed handoffs or inaccurate replies.
One clean operating rule
Measure each gap. Tag exceptions. Require acceptance.
This workbook was prepared by the Auto-Respond Team. Auto-Respond supports configured lead-response workflows for Thumbtack and other supported lead channels.
For workflow context, see Thumbtack auto responder.
The Thumbtack response lag fieldbook
By NZLeads Support
The Thumbtack response lag fieldbook
A 10-slide operator workbook for separating alert, review, reply, and handoff lag in Thumbtack lead response. Includes a timestamp log, exception tags, handoff card, daily review, and stop rule.
- 11
