Missed call text-back: what it is and how to do it legally
A text within seconds of an unanswered call, the five US rules that decide whether you may send it, the four numbers you must never text back, and why counting sends as recoveries is marking your own homework.
Sohail Safdar · · 6 min read
A missed call is a customer who tried. Missed call text-back is the practice of texting them within seconds, so the attempt does not evaporate into a voicemail nobody checks.
Why a text beats a callback
For a local service business an unanswered call is usually the end of that customer's effort. They ring the next result, and the window to recover them is minutes rather than hours.
A text works better than a callback for a structural reason rather than a stylistic one: it is asynchronous. The customer can answer it from a meeting, a job site, or while putting a child to bed. A returned call demands that both people be free at the same instant, which is the condition that produced the missed call in the first place.
How it works mechanically
- Somebody rings your business number and nobody picks up.
- The telephony provider reports the missed call.
- The system texts that number: who you are, one apology with a human reason, and one question.
- The reply lands in your inbox, where a person or an assistant answers it.
Step 4 is the whole difference between an auto-responder and something that books work. "Sorry we missed you, we will call back" moves the problem. "Sorry we missed you. What can we help with? We have openings Thursday" starts the conversation the call was for.
The scripts post has seven ready texts with their character counts.
The four numbers you must not text back
This is the part most descriptions skip, and it costs money and goodwill in both directions.
A two-second call. That is a misdial, and texting somebody who dialled by accident is the product being creepy. There needs to be a minimum call length below which nothing is sent.
A number that has already opted out. An opt-out applies to the business rather than to one feature of it. A missed call is not a fresh invitation.
The same number ringing four times in a minute. That is an auto-dialler, not a customer, and texting it pays the carrier for the privilege of answering a robot.
A withheld number. Nothing to text.
And one more worth excluding by configuration: anyone already in your contacts as a supplier or staff. The parts rep who rings twice a week does not need a booking link twice a week.
The compliance part, which a lot of tools are quiet about
Somebody calling you is generally treated as an invitation to respond. You are answering a contact they initiated, which is a meaningfully different posture from texting a purchased list. It does not exempt you from what follows.
Carrier registration. In the US, business texting over a standard 10-digit number goes through A2P 10DLC registration: you register the brand and the campaign, meaning what you send and why. Unregistered traffic is filtered rather than rejected, which is the failure that looks like success: your software reports the message as sent, no error appears anywhere, and the customer receives nothing. It takes days to weeks, so start before you need it. The 10DLC guide covers the process.
STOP means stop, immediately, and for the whole business. Enforced in the send path rather than by anybody remembering. The variants carriers treat identically: STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT. START and UNSTOP reverse it. And a plain sentence like "please stop texting me" counts too, which a keyword list alone will miss.
HELP must return something useful: who you are and a real way to reach a person.
Quiet hours, in the recipient's local time rather than yours. Some states regulate this directly and all of them regulate your reputation.
Marketing is a different category from a service reply. Texting somebody back about the call they just made is responsive. Adding an offer to that text, or adding them to a promotional send later, is marketing and needs marketing consent. Keep the two separate technically and not only in policy, because the technical separation is the one that holds on a busy Friday.
Nothing here is legal advice. TCPA exposure is real and the details depend on your state and your practices. Have counsel review your consent wording and your templates before you scale sending.
What good looks like
Hold any vendor, including us, to this list:
- Sends within seconds, not minutes. At five minutes the customer is talking to somebody else.
- Texts from the same number the customer dialled. A reply from an unfamiliar number reads as a scam, and it splits the thread: the customer answers the second number while your voicemails are on the first.
- Has a minimum call length, so a misdial gets nothing.
- Only answers inbound calls. A business ringing a customer and getting no answer has not missed a call; they are the one who called.
- Honours opt-outs automatically and permanently, against the number rather than the conversation.
- Respects quiet hours in the customer's timezone.
- Puts the reply in the same inbox as every other channel, so nobody watches a separate app.
- Records what was sent and why, in case anybody ever asks.
Measuring it honestly
Three numbers, and only the third means anything:
- Missed calls a week. Your baseline, and usually higher than anybody thinks.
- Replies to the text. Low means the text is too long or asks too much. Shorten it before changing anything else.
- Bookings that followed a reply. The one that counts.
The trap is reporting the second as the result. A text nobody answered recovered nobody, and a business that counts sends as recoveries is marking its own homework.
Where Frontiva is on this today
Being straight about it: missed call text-back is built and tested, and no practice can use it yet.
The product side shipped. Call events recorded when a call arrives rather than when it ends, because a final callback that never comes would otherwise lose the record entirely. Forwarding rules that read the same opening hours the booking calendar does. The text back itself, with both guards from the section above: a five second minimum, so a misdial gets nothing, and an inbound-only check that sits in the service rather than at the webhook so no future caller can bypass it. The minimum lives on the call record itself, which means the automation that sends and the dashboard that counts cannot disagree about what a missed call was.
What is missing is a number for calls to arrive on.
One thing worth being exact about, because it decides what you have to arrange: the phone account is yours, not ours. You connect your own Twilio or Telnyx account and the carrier charges land on your bill. So we cannot hand you a number and cannot register one for you, and a vendor telling you otherwise is describing a different arrangement with different costs and a number you do not own.
What is live is the foundation underneath: SMS send and receive, STOP and START enforced in the send path, one contact record across channels, and an assistant that answers from your approved knowledge. The missed-call half plugs into that rather than being bolted on beside it.
The missed call text back page sets out the intended behaviour, and the setup guide covers what you can prepare now, which is most of it.