A plumber under a sink cannot answer the phone. Neither can a roofer on a ladder or an HVAC tech in an attic in August. The calls still come in, and most of them land in voicemail or ring out. A missed call is not a lost job yet. It becomes one when nobody calls back, or when somebody calls back after the customer has already booked a competitor.
This note is about the part after the miss: what the business does next, who does it, and what it should not do.
The short answer
Follow up on every missed call, but let a person own the follow-up. Use an automatic text only for callers who ask for one, send one confirmation per call, and say honestly when someone will call back. Track how long it takes a human to respond, because that number, not the text, decides whether the job is saved.
Why texting every hang-up is the wrong default
The common pitch is simple: someone calls, nobody answers, and a text goes out automatically to the number that called. It sounds harmless. In practice it causes three problems.
- It texts people who did not ask. Some callers dialed the wrong number. Some are vendors, robocallers, or customers who will just call again. A text they never asked for reads as marketing, and people report it that way.
- It can break your texting setup. In the United States, businesses that text from a regular ten digit number go through carrier registration for that use, known as A2P 10DLC (Twilio's overview of the requirement). Messages that do not match the registered use, or that draw complaints, can be filtered or blocked. That puts the texts you actually need, like appointment confirmations, at risk.
- It replaces the callback instead of starting it. A text that says "Sorry we missed you!" with no plan behind it just moves the unanswered message from voicemail to a text thread nobody is watching.
The follow-up path that holds up
The version we set up for clients, described on our missed-call text back page, has five parts.
- Catch the miss. The phone system flags every call that rang out or went to voicemail, so none of them disappear into a call log nobody reads.
- Ask before texting. Before the voicemail, the caller hears a short message and can press 1 to get a text. Nobody gets a text without that yes.
- Confirm once. A caller who pressed 1 and left a voicemail gets one text confirming the message arrived and when to expect a call back. A retried call event never sends a second copy.
- Hand it to a person. The call, the voicemail, and any reply land in one shared inbox or the CRM, with a named person responsible. The automation opens the conversation. A person finishes it.
- Keep a path for everyone else. Callers who do not press 1, or whose number cannot receive texts, still show up in the same inbox for a normal callback.
Who owns the callback
This is the part most setups skip. Before anything is switched on, write down three things:
- The person. One name per shift or per day, not "the office."
- The hours. When missed calls are reviewed, and what happens after hours and on weekends.
- The promise. What the confirmation text tells the caller. "We will call you back within the hour" is only safe if someone can keep it at 4:30 on a Friday. "We got your message and will call you back today" may be the honest version.
If nobody can own the callback, the text makes things worse, because it raises an expectation the business then misses.
What the confirmation should say
Keep it short, name the business, say what happens next, and include how to stop. An example, which should be reviewed against your own registration and hours before use:
Thanks for calling Bayou Plumbing. We got your voicemail and someone will call you back today. Reply here if it is urgent. Reply STOP to opt out.
Leave out offers, links to a booking page the team cannot honor, and anything that reads like an ad. The caller asked for one confirmation, so send one confirmation.
Test it before customers do
Run each of these with a real phone before launch, and again after any change to the phone system:
- A call that is answered (no text should go out)
- A caller who presses 1 and leaves a voicemail
- A caller who does not press 1
- A caller who hangs up before the voicemail
- The same caller calling twice in a row
- A call after hours
- A reply to the confirmation, and a reply of STOP, HELP, and START
- A number that cannot receive texts
Write down who checks delivery failures and unanswered replies each week. Those are the places a working setup quietly stops working.
What to measure
Four numbers tell you whether this is doing its job:
- Missed calls per week, so you know the size of the problem
- Callers who asked for a text, which shows whether the prompt is clear
- Time from missed call to first human response, the number that matters most
- Missed calls that became a booked appointment or estimate
If the response time is long, the fix is staffing or routing, not a better text. If very few callers press 1, the prompt is too long or unclear.
When it is not worth setting up
If the business already answers nearly every call live, or calls every voicemail back within minutes, an automatic text adds little. The same goes for a business whose texting registration is not approved yet: wait for the approval rather than texting from an unregistered number.
For everyone else, the missed call is one of the easiest leads to save, because the customer already chose you. The work is making sure someone calls them back. If you want a second set of eyes on how calls move through your business today, a free systems review walks through one current process and ends with written next steps.