How to Automate Missed Call Text-Backs for Local Businesses (2026)
An automated missed call text-back sends an SMS to a caller within 60 seconds of an unanswered call — before they dial a competitor. Built with n8n and Twilio, the setup takes under 20 minutes and costs approximately $1.63/month to run. Businesses that respond within 5 minutes are 100 times more likely to make contact and convert leads than those who wait 30 minutes.
How many calls does the average local business actually miss?
Small local service businesses miss approximately 62% of their inbound calls. Only 37.8% are answered by a live person. The rest hit voicemail — and 80–85% of callers who reach voicemail hang up without leaving a message.
What happens next is the real problem: 62% of those missed callers immediately contact a competitor. Without an automated text-back, the majority of missed calls are permanently lost within minutes of the hang-up.
The gap widens after hours. Missed call rates reach 71% for healthcare practices and 73% for legal services outside standard business hours — exactly when people are making urgent decisions about which plumber to call, which dentist to book, or which lawyer to contact.
What does a missed call actually cost your business?
The average small business loses approximately $126,000 per year in revenue due to missed calls. The per-call cost varies sharply by industry:
| Industry | Revenue Lost Per Missed Call | Annual Loss (est.) |
|---|---|---|
| Home Services (HVAC, Plumbing) | $275 – $1,200 | $45,000 – $120,000 |
| Dental Practices | ~$850 per new patient call | $100,000 – $150,000+ |
| Law Firms | $5,000+ per case inquiry | $60,000 – $200,000+ |
| Automotive Service Departments | $853 – $1,170 per appointment call | $853,000 – $1.17M |
| All SMBs (average) | ~$200 per missed call | ~$126,000 |
These figures assume the caller never comes back. With an automated text-back that responds in under 60 seconds, a meaningful portion of those calls — and that revenue — can be recovered.
Why does text-back outperform voicemail for recovering missed calls?
Speed determines whether you get the lead or your competitor does. Research from Harvard Business Review found that businesses responding within 5 minutes are 100 times more likely to make contact and 21 times more likely to qualify the lead than those who wait 30 minutes. Responding within 60 seconds can increase conversion rates by up to 391%.
The channel matters too. Voicemail has an effective response rate close to zero — 80–85% of callers hang up before leaving one. SMS is the opposite: text messages have a 98% open rate and 90% are read within 3 minutes. The moment your automated text arrives, the caller knows you saw their call, you care about their business, and you're available to help — even though you couldn't answer the phone.
That instant acknowledgment keeps the lead warm and gives the customer a clear next step, removing the friction that sends them to a competitor.
How do you set up missed call text-back with n8n and Twilio?
You will need: an n8n instance running (see the free n8n setup guide) and a Twilio account (free trial covers testing). The full setup takes under 20 minutes.
Sign up at twilio.com — the free trial includes credit for testing. Buy a local phone number in your area code ($1/month). You do NOT need to change your existing business number. Instead, configure call forwarding on your phone carrier to forward unanswered calls to the Twilio number after 4–5 rings. Clients call your real number; Twilio catches the overflow.
In the Twilio Console, go to Phone Numbers > Active Numbers > your number. Under Voice Configuration, paste your n8n webhook URL into the "A call comes in" field AND the "Call status changes" field. This ensures Twilio fires a POST to n8n when a call is not answered. Copy your Account SID and Auth Token from the Console dashboard — you will need both.
In n8n, create a new workflow. Add a Webhook node, set the method to POST, and copy the production URL. Paste this URL into both Twilio webhook fields from Step 2. Activate the workflow so n8n is listening.
Add a Set node to extract callerPhone from {{ $json.From }} and callStatus from {{ $json.CallStatus }}. Then add an IF node: only continue if callStatus equals no-answer or failed. This stops the workflow from sending text-backs on completed calls.
Add an HTTP Request node. Set method to POST and URL to:
https://api.twilio.com/2010-04-01/Accounts/{AccountSID}/Messages.jsonReplace {AccountSID} with your actual SID. Enable Basic Auth using Account SID as username and Auth Token as password. In the request body (form-encoded), set: From = your Twilio number, To = {{ $json.callerPhone }}, Body = your text message.
Add a Wait node set to Wait for Webhook. Create a second Twilio webhook for inbound SMS (set the SMS URL in your Twilio phone number settings to a second n8n webhook path). When the customer texts back, it resumes this wait. Set a timeout of 15 minutes — if no reply arrives, log to Sheets as "No reply" and end.
Add an IF node that checks if the reply body contains urgency keywords: emergency, urgent, leak, broken, no heat, no AC, today. Customize these for your industry. If any match, go to the Urgent branch; otherwise go to the Routine branch.
Add another HTTP Request node (same Twilio SMS API call). Send to the owner's personal mobile number: "URGENT: [callerPhone] texted: '[their reply]'. Call back now." This gets the owner's attention within seconds for high-value emergency calls — the type of call that can be worth $500–$5,000 in a single job.
Add a Google Sheets node to append a row: caller phone number, their message, timestamp, and status "Needs callback". The front desk reviews this list each morning and works through it systematically. No more sticky notes, no more lost numbers on scraps of paper.
What should the text-back message actually say?
The first message should be short, warm, and open-ended. The goal is to get the caller to reply — not to hard-sell them. A proven template:
"Hi, this is [Business Name] — sorry we missed your call! What can we help you with today?"
Why this works: it is personalised (uses your business name), apologetic (not pushy), and ends with an open question that invites the customer to describe their need. That reply is then used by your IF node to classify urgency — so the message is doing double duty as both a recovery tool and a triage input.
For after-hours missed calls, add a qualifier: "We're closed right now but will call you back first thing tomorrow — what do you need help with?" This sets expectations and still captures the job type for prioritisation.
How do you build this with Make.com instead of n8n?
Make.com has a native Twilio module that handles both inbound webhooks and SMS sends without an HTTP Request node. Create a scenario with a Twilio Watch Calls module filtered to status "no-answer", chain it to a Twilio Send an SMS module, then use Text Parser to check for urgency keywords.
Make.com's free tier covers 1,000 operations/month — enough for approximately 110 missed calls/month on this workflow. If you are already using Make.com for other automations (like appointment reminders), you can add this as a second scenario at no extra cost. Not sure whether to use n8n or Make.com? See the full comparison.
How much does this cost to run per month?
At 20 missed calls/week (80/month), the cost breakdown is:
| Item | Monthly Cost |
|---|---|
| Twilio phone number | $1.00 |
| Twilio SMS (80 texts @ $0.0079) | $0.63 |
| n8n hosting (shared VPS) | $5.00 – $10.00 |
| Google Sheets | $0.00 |
| Total | $6.63 – $11.63/month |
If recovering just one previously-missed lead per month generates a $200 job — a conservative estimate for any home services or professional service business — the automation pays for itself 17–30 times over every month it runs.
If you are building out automated client communication — missed call text-back, appointment reminders, and lead follow-up — the Peak Automations templates give you pre-built, tested workflows for each step of the journey.
Appointment Reminder Automation — $47 one-time
Get the Template — $47 →Browse all 5 templates →
Frequently asked questions
Approximately 62% of inbound calls to small local businesses go unanswered. Of those callers who reach voicemail, 80–85% hang up without leaving a message. And 62% of all missed callers immediately call a competitor. Without an automated text-back, most missed calls become permanently lost revenue.
The average small business loses approximately $126,000 per year due to missed calls. Industry-specific losses: home services (HVAC, plumbing) $275–$1,200 per missed call; dental practices ~$850 per missed new-patient call; law firms $5,000+ per missed case inquiry. Automotive service departments can lose over $1 million annually in missed appointment calls.
Within 5 minutes, businesses are 100 times more likely to make contact and 21 times more likely to qualify the lead than those who wait 30 minutes. Responding within 60 seconds increases conversion rates by up to 391%. 78% of customers buy from the first company that responds — which is why the automation sends within seconds, not minutes.
No. You keep your existing business number. Configure call forwarding on your phone carrier to forward unanswered calls to your Twilio number after 4–5 rings. Clients call your real number as usual. Twilio only activates when a call goes unanswered, then fires the webhook and sends the text-back.
A Twilio phone number costs $1/month. Each SMS in the US costs $0.0079. At 80 missed calls/month (20/week), the monthly SMS cost is approximately $0.63. Total Twilio cost: ~$1.63/month — compared to $126,000/year in missed-call revenue losses. Twilio offers a free trial with sufficient credit to test the full workflow.
Yes. Make.com has a native Twilio module that handles call webhooks and SMS sending. The workflow logic is identical — no-answer trigger, send SMS, wait for reply, keyword IF check, route urgent or log to Sheets. Make.com free tier covers ~110 missed calls/month. For higher volumes, the Core plan at $9/month handles 10,000 operations.
Keep it short and end with an open question. Proven template: "Hi, this is [Business Name] — sorry we missed your call! What can we help you with today?" This prompts the caller to describe their need, which your IF node then classifies for urgency. Avoid hard-sell language in the first message — the goal is to get a reply, not to pitch.