Setting up missed-call text-back without annoying anyone

A missed call at a service business is a customer deciding whether to try you again or try the next name on the list. Most of them do not try again. Missed-call text-back turns that dead end into a conversation, and it is one of the few automations where the payback is obvious within a week.

It is also easy to do badly. Here is what separates the version people reply to from the version that gets you a STOP.

Why it works at all

A voicemail asks someone to listen, wait for a beep, speak, and hope. A text asks them to read eight words and tap a reply. The person who just called you is the warmest lead you will get all day: they had a need, they chose you, and they got nothing.

The window is short. Somebody who rings a dentist about a broken crown is not waiting an hour; they are working down search results.

Step 1: it has to come from the number they dialled

This is the one that quietly ruins otherwise-good setups.

If a customer calls (555) 123-4567 and gets a text from (555) 987-6543, three things go wrong. It reads like a wrong number or a scam. Their reply goes to whichever number they have saved, which is the one they called. And your caller ID in their phone now shows two entries for you.

Text back from the number they rang. If that number is a landline, text-enable it rather than buying a second one.

Step 2: what the text should actually say

Four things, in this order:

1. Who you are, in the first few words, before they decide it is spam.
2. That you noticed: you missed their call, not "thanks for contacting us".
3. One question they can answer in three words.
4. How to stop: required, and it costs you nine characters.

A version that works:

Hi, it's Bright Smile Dental. Sorry we missed your call. What can we help with? Reply STOP to opt out.

A version that does not:

Thank you for contacting Bright Smile Dental. Your call is important to us. Our team is currently assisting other customers. Please visit our website at brightsmiledental.example.com/contact to submit an enquiry and a representative will respond within 1-2 business days.

The second one is longer, says nothing, asks for more work than the phone call they already made, and costs you two message segments to send.

Keep it under 160 characters and it sends as one segment. Past that it splits, and on some handsets arrives as two.

Step 3: seconds, not minutes

The text should land while the phone is still in their hand. A delay of a few seconds reads as "someone noticed". A delay of five minutes arrives after they have already called somebody else.

This has an architectural consequence worth knowing when you evaluate software: a text-back that depends on a scheduler running every minute cannot promise "within seconds". Ask how it is triggered.

Step 4: after hours is a different message

The worst version of this feature is the one that texts "how can we help?" at 11pm, gets a reply, and then says nothing until Tuesday.

After hours, say when you will be back:

Hi, it's Bright Smile Dental. Sorry we missed you. We're closed now and open at 8am. Reply here and we'll pick it up first thing. Reply STOP to opt out.

That is a promise you can keep. "How can we help?" at 11pm is not.

Quiet hours matter here too. Because the person contacted you first, a reply to them is conversational rather than marketing, but a practice that texts at 2am still looks like a practice that texts at 2am.

Step 5: somebody has to read the replies

The text is not the feature. The conversation is. If replies land in a system nobody watches, you have built a slightly more polite way to ignore people.

Test it properly: call your own number from a phone that is not in your contacts, let it ring out, and reply to the text. Time how long until a human answers. That number is your actual feature.

The compliance question everybody asks

"Do I need consent to text someone who called me?"

The useful distinction is what the message is for, not merely that they rang you. A reply to somebody who just contacted you is conversational: they started it, and answering is the thing they were trying to make happen. A promotional blast to everyone who ever called you is marketing, and marketing needs a marketing consent basis that a phone call does not provide.

Practical consequences:

• Answer the call they made. Do not use the missed-call list as a marketing list later.
• Honour STOP immediately, and record it against the number rather than against that one conversation. Otherwise the same person is still reachable on WhatsApp, or in a thread opened next month.
• Keep the record. "They called us once in March" is a weak answer if challenged, and a far weaker one if the message you sent was promotional.

Not legal advice. TCPA and state rules carry real penalties and turn on specifics. Have counsel review your templates and your opt-in language.

What Frontiva does today, precisely

Being straight about this, because a guide that sells you something it cannot deliver is a worse guide.

Built and tested: a record of every call written the moment it arrives, not when it ends, which loses exactly the calls whose final callback never comes. Forwarding rules per location that read the same opening hours your booking calendar uses, so a lunch break and a bank holiday mean the same thing to the phone as to the calendar. An automatic text back within seconds when nobody picks up, sent inline rather than waiting for a scheduler tick. Call recording off by default, and impossible to switch on without an announcement playing first.

Three refusals are deliberate: it will not forward a call to the number it arrived on (a loop that bills you for every lap), will not ring anybody after hours unless you ask it to, and will never hang up on a customer, because a call that reaches nothing still reaches voicemail and still earns a text back.

Not yet: a phone number to ring. Provisioning and A2P 10DLC registration need a carrier account we do not have, so today you would bring your own. Built is not the same as available, and we would rather say so here than let you find out during a trial.

When the reply comes in, it lands in the unified inbox as an ordinary conversation, and automations can follow up if nobody answers, stopping the moment the customer replies or books.