Stop Losing Home Service Jobs Because Your Follow-Up Takes Four
The Core Problem
Home service leads have a half-life of about 15 minutes. After that, they've already called three competitors. Most small shops rely on a shared Gmail inbox or a clipboard by the phone. That's not a process — that's hope.
What Actually Works
1. Webhook every lead source into one queue
Forms, Facebook Lead Ads, Google Local Services, Angi, HomeAdvisor, phone call tracking (CallRail/Twilio) — all push JSON to a single endpoint. I use n8n self-hosted on a $6 DigitalOcean droplet, but Zapier/Make work fine if you'd rather not maintain infra.
{
"lead_id": "lsvc_7f2k9",
"source": "google_lsa",
"service_type": "ac_repair",
"urgency": "emergency",
"contact": {
"name": "Maria Chen",
"phone": "+15553439201",
"email": "[email protected]"
},
"payload": {...}
}2. Immediate multi-channel acknowledgment
Within 30 seconds the lead gets:
- SMS: "Hi Maria, this is Jake from Arctic Air. Got your AC emergency request — tech dispatching now. ETA 90 min. Reply STOP to opt out."
- Email with the same info + tracking link
- Internal Slack/Teams alert with one-click "Claim" button for technicians
Twilio Messaging Service handles the SMS side. Cost: ~$0.0075 per segment. Negligible.
3. Escalation ladder if no human claims in 3 minutes
| Tier | Action | Channel |
|------|--------|---------|
| T+3m | Re-alert on-call tech + manager | SMS + push |
| T+8m | Auto-call lead with IVR: "Press 1 for emergency dispatch, 2 to schedule" | Voice (Twilio) |
| T+15m | Owner gets notified | Phone call |
The IVR is a 12-node Twilio Studio flow. Takes 20 minutes to build once.
4. Appointment confirmation & reminder sequence
Once booked:
- T-24h: SMS + email reminder
- T-2h: SMS with tech photo/bio + live tracking link
- T+30m post-job: Review request (Google Maps deep link)
The Stack That Costs <$200/mo
- n8n (self-hosted): $6 VPS
- Twilio: ~$40-80 depending on volume
- Google Sheets / Airtable as lightweight CRM: free tier
- Slack webhook for team alerts: free
- UptimeRobot monitoring the webhook endpoint: free
No HubSpot. No Salesforce. No $500/mo field service platforms.
What Broke the First Week
Duplicate leads — same person submits form, calls, and chats. Solution: dedupe by phone+email+service_type within 4-hour window using a Redis set with TTL.
Carrier filtering — AT&T blocked our SMS after 200 sends/day. Fix: register a 10DLC campaign (takes 3 business days), use a toll-free number for higher throughput, rotate messaging service SIDs.
Tech adoption — two techs ignored Slack alerts. Fix: added PagerDuty escalation to their personal phones. Compliance hit 98% overnight.
Metrics Worth Tracking
- Speed-to-first-contact (target: <60s)
- Claim rate (% of leads a tech accepts within 5m)
- Booked rate (claimed → scheduled)
- No-show rate (customer ghosts after booking)
- Cost per booked job (total stack spend / booked jobs)
Last month: $1,840 stack cost / 47 booked jobs = $39.15 CAC. Their previous Google Ads CAC was $180+.
One Thing I'd Do Differently
Start with a simpler CRM. Airtable's API rate limits bit us at 50+ leads/day. Switched to Postgres on the same VPS — zero issues since. If you're under 20 leads/day, Airtable's fine. Above that, just spin up a real database.
The code for the n8n workflows and Twilio Studio flow is on my GitHub if anyone wants the starter templates. Happy to walk through the dedupe logic or IVR structure in the comments.