Automation
Missed-Call Text-Back: The Highest-Return Automation You Can Build
One workflow, about an hour to build, and it usually recovers more revenue than everything else in the account combined.

Why this one earns its keep immediately
Every other automation works on leads you still have to attract. This one works on calls you already paid for and did not answer. For a home services company spending on local ads, a missed call is a wasted click, a wasted impression and a lost job all at once. Recovering even a third of them changes the month, and unlike most marketing work the effect shows up within days.
What the workflow does
The logic is simple and the discipline is in the details.
- Trigger on a call event with status missed, no-answer, busy or voicemail
- Wait a short delay, twenty to forty seconds, so a fast human callback does not collide with the text
- Check the contact has not already been texted in the last few hours, to avoid double-sending on repeat dials
- Send an SMS from the same number they dialled, which matters more than anything else here
- On reply, stop the automation and route to a shared inbox with a notification
- On silence at ninety minutes, send one follow-up, then hand to a short nurture rather than dropping the lead
Send from the number they called
This is the most common implementation mistake and it halves performance on its own. If someone dials your main line and gets a text from a different number, it reads as spam and gets ignored. The text must come from the number they just dialled, which means your inbound number and your messaging number have to be the same registered number.
What the first message should say
Two lines, one job. Name the business so they know who this is, acknowledge that you missed them, and give exactly one action. Something like: "Hi, this is Ellery Home Services. Sorry we missed your call. Reply here and we will get straight back to you, or book a slot: [link]". No paragraph about your values, no three options, no emoji. The message needs to look like a person typed it in a hurry, because that is the register that gets answered.
The mistakes that kill it
The workflow itself rarely fails. The surrounding conditions do.
- Sending before A2P registration is approved, so the texts are filtered and you conclude the tactic does not work
- No suppression window, so a customer who dials three times in a row receives three identical texts
- Nobody watching the reply inbox, which is worse than not sending at all because you have now promised a response
- Firing on internal or known-contact calls, so your own staff and existing customers get the new-enquiry message
- A booking link that lands on a homepage rather than a calendar with real availability
What to expect from the numbers
Reply rates on the first message commonly land between 30 and 45 percent, which is unusually high because the recipient initiated contact minutes earlier. Of those replies, the share that converts to a booked job depends entirely on how fast a human picks up the thread. The automation buys you the conversation; it does not close it.
Where to go next
Once this is running and someone is genuinely watching the inbox, the natural extensions are after-hours handling with an AI agent that can book directly, and applying the same pattern to unanswered web form submissions. Both build on the same principle: the response has to happen at the moment of intent, not at the moment you get round to it.


