The bottleneck
When the owner is on a job, calls go to voicemail. Most callers don't leave one. They call the next business on the list.
The recipe
- Connect your business line to a provider that can trigger on missed calls.
- Send one short, approved text that names the business and asks what they need.
- Capture the reply, the service requested and a callback window in one place.
- Route anything urgent, angry or unclear to a human immediately.
- Offer the booking link only for services you can actually schedule; log every outcome.
Starter prompt · copy and adapt
Write the text message sent automatically when a call to [BUSINESS] is missed. Requirements: under 300 characters, names the business, apologizes briefly, asks what they need help with, offers the booking link [LINK], says a person will follow up during business hours, and ends with "Reply STOP to opt out." Then write two variants: one for after-hours calls, and one for a caller who has already replied with a service request. Do not quote prices, promise arrival times or confirm availability.
Where it breaks
Keep texts transactional and only to people who called you, with clear opt-out language, and check local texting rules with your provider. Never let the automation promise a price, an arrival time or emergency service it cannot guarantee. If the text-back is the only follow-up, urgent calls will still slip: a human escalation path is part of the design, not an extra.
DIY vs. production
The free version genuinely works for the simple case. Here's what a production build adds.
| What you get | This free playbook | 14-Day Sprint |
|---|---|---|
| Workflow logic + starter prompt | ✓ Complete | ✓ |
| Works for the simple case | ✓ | ✓ |
| Human approval gates, built and tested | You design them | ✓ Included |
| Exception handling + safe fallbacks | — | ✓ Included |
| Access + data-security review | — | ✓ Included |
| Team training + operating runbook | — | ✓ Included |
| Baseline + 60-day measured result | Self-serve worksheet | ✓ Included |