A missed call in a service business is not a neutral event. It is a customer with a problem, a phone in their hand, and a list of three more numbers. The window in which you can still win that job is measured in minutes, and it closes whether or not anyone on your team knows the call happened.
Missed-call text-back is the automation that closes it. When a call goes unanswered, the caller receives an SMS within seconds — before they have finished dialling the next company.
Why it works better than calling back
Returning the call feels more attentive, and it is worse. A callback demands the customer be free at the exact moment you are, and it arrives as an unknown number they will probably ignore. A text is asynchronous. They read it in the next thirty seconds, from the same phone, and can reply without stopping what they are doing.
It also does something a callback cannot: it puts your name in their message history. Even when they book someone else this week, you are now a saved thread rather than a number they do not recognise.
What the message should actually say
The default template most systems ship with — "Sorry we missed your call, we will get back to you shortly" — is close to worthless. It is indistinguishable from an away message and it asks the customer for nothing. Three properties separate a message that recovers jobs from one that does not:
- It names the work. "Is this about the AC?" gets a reply. "How can we help?" gets silence. Specificity signals a human read it, even when one did not.
- It offers a next step, not an apology. Give them something to say yes to: today, tomorrow morning, a callback in ten minutes.
- It sounds like the person who would have answered. Contractions, no title case, no "Dear valued customer." The bar is: would a customer be surprised to learn this was automatic?
The legal and deliverability basics
This is not legal advice, but three things are worth knowing before you switch it on:
- A reply to an inbound call is generally treated very differently from cold outreach — the customer initiated contact. That is the whole basis on which this is reasonable to send.
- Include an opt-out on the first message of any ongoing sequence, and honour it immediately and permanently. One ignored STOP is a much bigger problem than a hundred lost leads.
- Send from a number the customer can call back and reach a human. A no-reply shortcode undoes most of the trust the message just built.
Where it usually breaks
Three failure modes account for nearly all the disappointing rollouts we see:
- Nobody watches the replies. The text fires, the customer answers in ninety seconds, and the answer lands in an inbox that gets checked at 6pm. You have now automated the appearance of responsiveness, which is worse than not sending it.
- It fires on internal calls. Suppliers, your own crew, the accountant. Exclude known numbers or the team will start ignoring the whole channel.
- It does not stop. If the customer replies and the sequence keeps sending, you have built a machine for annoying people who already said yes. Any sequence behind this must pause on reply.
A missed call answers itself in 90 seconds — while she is still holding the phone.
Built on the truck, sent before you pull away, with the chase already scheduled.
Photos and notes land on the customer record, not in someone's camera roll.
Invoice, review request, and next spring's tune-up — all without a Monday to-do list.
What to expect
Pull your call log for last month and count unanswered inbound calls from unknown numbers. For most 3–20 person service businesses that number lands somewhere between 40 and 150. If a fifth of those reply, and you close a third of the replies at your average ticket, you can size the recovery in about two minutes with a calculator.
The reason this is the first automation worth turning on is not that it is clever. It is that the demand already exists, you already paid to create it, and right now it is walking out the door in silence.
Common questions
What should a missed call text back say?
Name your business and a real person, reference the likely job so it reads as human, and offer a concrete next step — same-day service, a time window, or a callback. Avoid generic "we will get back to you" wording; it reads as an away message and gets no reply.
How fast should the text send?
Within sixty to ninety seconds. The value comes from reaching the caller before they dial the next company, so a delay of even five minutes gives most of the benefit away.
Is missed call text back legal?
Replying to someone who just called you is materially different from cold outreach, since the customer initiated contact. Include an opt-out on any ongoing sequence, honour opt-outs immediately, and send from a number that reaches a human. Check your local rules — this is general guidance, not legal advice.
What happens if the customer replies?
The reply has to land somewhere a person actually watches, and any follow-up sequence must stop the moment they respond. A system that keeps sending scheduled messages after someone has replied does more damage than sending nothing.