The manual lead rescue SOP for when the bot fails
Automation should never be the reason a good homeowner gets lost. Bots fail. Workflows stall. Messages get weird. A lead says something the system does not understand.
The difference between a clean operation and a leaky one is whether a human can rescue the lead quickly. This is the manual rescue SOP for when a bot gets stuck, disqualifies incorrectly, or fails to transfer a good foundation, waterproofing, or crawlspace lead.
The problem
The bot stalls while a real homeowner waits.
The outcome
Lead saved, handed off clean, failure logged.
The asset
The 8-step rescue SOP with scripts.
The mental model
Stop the bad automation
→ save the active lead
→ collect the missing info
→ hand off cleanly
→ document the failure
→ fix the system later
Do not debug the whole CRM while a homeowner is waiting.
Step 1. Decide if the lead needs rescue
- Bot did not respond
- Bot repeated itself
- Bot asked the wrong question
- Bot gave a bad answer
- Bot disqualified a lead that looks like a fit
- Lead gave phone / zip / project but the fields are empty
- Lead is asking for a human
- Lead is clearly urgent
- Lead is stuck in Needs Review
- Lead looks like a real structural, waterproofing, or crawlspace inspection but the bot stalled
If the lead is active and could still book, rescue first. Diagnose later.
Step 2. Pause the bot for that contact
- Stop AI for the contact
- Remove from active nurture if needed
- Check that no duplicate follow-up is about to send
- Add a note: "Manual rescue started — [date/time]"
The homeowner should not get a human message and a bot message at the same time.
Step 3. Send the rescue message
Use a calm handoff. Do not apologize for the whole system.
Hey [First Name], jumping in here so we can make sure this gets handled correctly.
Can you send me the best phone number and the zip code for the property?
If they already gave details:
Got it — thanks. I have [project type] in [city/zip]. Let me get this to the right person so they can help with the next step.
Step 4. Collect the minimum required info
Do not run a full intake if you only need a few fields.
- Name
- Phone
- Zip code
- City
- Project type
- Short project note
- Urgency
- Best time to call
- Homeowner / decision-maker status
- Inside service area
If they will not give a phone number, ask once more. If they still refuse, move them to review instead of forcing it.
Step 5. Transfer the lead cleanly
- Contact fields updated
- Conversation notes cleaned up
- Lead marked as qualified / review / disqualified
- Office or setter notified
- Task created if someone must call
- Booking link sent if appropriate
- Source and campaign left intact
- Estimator brief includes symptom, location, urgency, and next step
Use this handoff note:
Manual rescue: homeowner asked about [project type] in [city/zip]. Phone: [phone]. Notes: [plain-English summary]. Recommended next step: [call / book / review / disqualify].
Step 6. Use the bad-fit path when needed
Not every rescue should become a transfer.
- Out of service area
- Wrong service
- Renter with no owner approval
- Spam
- No phone after two asks
- Commercial job if the account only wants residential
- Cosmetic-only issue below the account's threshold
- Duplicate lead already in the CRM
- Price-shopping with no real project
Bad-fit leads still get logged. They teach the system what to filter next time.
Step 7. Document the failure
The rescue is not done until the failure is logged.
FAILURE LOG
Date/time:
Client/account:
Lead source:
What the bot did:
What the homeowner said:
What field was missing or wrong:
Manual action taken:
Was the lead saved? yes / no
Fix needed:
Do not write "bot failed." Write the exact failure.
Step 8. Fix the pattern, not just the lead
After the active lead is safe, look for the repeated pattern.
- Prompt issue
- Missing custom value
- Missing service-area rule
- Broken workflow trigger
- Bad field mapping
- Bot should have stopped earlier
- Human handoff rule is unclear
- Lead source is creating bad-fit traffic
One rescued lead is service. Three similar rescued leads is a system problem.
The rescue system is ready when this sentence is true: a human can stop the bot, save the lead, collect the missing info, transfer the opportunity, and log the exact failure without breaking the rest of the workflow. That is how automation stays useful instead of risky.
Go deeper
This SOP is the safety net inside the Booking Engine Kit — the fields, tags, automations, QA gate, and rescue path that turn leads into booked inspections.
Get the Booking Engine Kit →