Missed call automation: what to do when nobody answers

A plumber under a sink cannot answer the phone. A roofer on a ladder should not try. A salon with three clients in chairs will let it ring. This is not negligence, it is physics. The work and the phone compete for the same pair of hands, and the work wins because the work is already paid for.

The cost lands later. Someone rang because their boiler had stopped or their gutter was overflowing or they wanted a colour appointment on Saturday. They did not leave a voicemail. Nobody leaves voicemails. They rang the next number on the list instead, and by the time the phone is free the job has already gone somewhere else.

Missed call automation is the least glamorous fix in this whole category and probably the most valuable. It does one thing: when a call is not answered, something happens automatically, immediately, without anyone remembering to do it.

What actually triggers it

The trigger is a call that ends without being answered. That sounds obvious, but the detail matters, because a badly configured trigger is how businesses end up texting people they just spoke to.

You want to fire on:

• An inbound call that rang out and was not picked up.
• An inbound call that went to voicemail, whether or not a message was left.
• An inbound call that was answered by a person and then dropped inside a few seconds, which usually means a bad line rather than a rejection.

You do not want to fire on:

• Calls the business made outbound.
• Withheld or clearly invalid numbers, because there is nowhere to send a message.
• Repeat calls from the same number inside a short window. One caller trying three times in ninety seconds should generate one follow-up, not three.
• Numbers already in an active conversation. If a customer is mid-thread with the office and rings, gets no answer, and rings again, an automated "sorry we missed you" makes the business look like it is not paying attention.

That last one is worth building in properly. A suppression rule that checks whether the number has had a human message in the last day or two prevents most of the embarrassing failures.

Timing: fast, but not instant

Speed is the entire point. The caller is still holding their phone. They have not yet dialled the next number, or if they have, they have not yet had a conversation with them. That window is short and it does not come back. It is the same dynamic that governs how quickly a web enquiry needs answering.

Send the first message within about a minute of the missed call. Not two seconds - a text that arrives while the phone is still going to voicemail feels automated in a way that undermines it, and occasionally arrives before the caller has hung up. A short delay of thirty to sixty seconds reads as somebody noticing.

Some businesses set it much longer, five or ten minutes, on the theory that they might be able to ring back themselves first. In practice that theory rarely survives a busy week. If you are worried about doubling up, the better fix is a rule that cancels the automated message if an outbound call is made to that number first.

What the message should actually say

Short. Identified. One clear next step. That is the whole recipe.

Hi, this is Dan at Fairfield Plumbing - sorry we missed your call, we're on a job. Reply here and tell me what you need and I'll come back to you shortly. Reply STOP to opt out.

Look at what that does. It names a person and a business, so the recipient knows who is texting an unknown number. It gives a plain reason for not answering, which is more reassuring than an apology on its own. It asks for a reply in the channel the message arrived in, which is the lowest-friction option for someone standing in a kitchen holding a phone. And it carries an opt-out, which is not optional.

Things to avoid:

• Corporate framing. "Your call is important to us" is the phrase people associate with being ignored.
• Asking them to ring back. They just rang. They did not get through. Asking them to repeat the thing that failed is a poor ask.
• A form link as the only option. Links are fine as a secondary path. As the primary one they lose people.
• Pretending to be human when you are not. If replies land in an inbox that nobody reads until evening, do not write "I'll come back to you shortly". Write something honest about when.

Adjusting for the trade

An emergency trade and an appointment trade need different wording. A plumber or a locksmith should acknowledge urgency directly and give a route for genuine emergencies, because someone with water coming through a ceiling will not wait politely. A salon, a driving instructor or a dental practice is usually dealing with a booking request, so the useful message offers the next step towards a booking rather than a reassurance about response time.

An estate agent gets a mix and benefits from a first message that asks a sorting question - whether the caller is buying, selling or letting - because the answer routes the enquiry to the right person without a human doing the triage. The same split between urgent trades and appointment trades shapes how trades handle their calls more generally.

The sequence, and where it ends

One message is the core of it. Most of the value is in the first message and businesses that stop there are already ahead of where they were.

If you add a follow-up, keep it to one, and space it properly. A second message a few hours later, or the following morning if the miss was late in the day, catches people who saw the first one, meant to reply, and got distracted. After that, stop. A third and fourth message to someone who has not replied twice is not persistence, it is nuisance, and the person on the receiving end will remember the business for the wrong reason.

Stop conditions should be explicit in the build:

1. They reply. Everything else in the sequence cancels.
2. They are called back and answered by a human.
3. They opt out. This must be honoured immediately and permanently.
4. The sequence runs out. Two messages, then silence.

The temptation to keep chasing is strong because chasing feels like effort. But a lead that ignored two messages has told you something, and the businesses that respect that answer have better reputations than the ones that do not.

Rules you have to follow

UK electronic marketing rules apply to SMS and email, and a missed call text-back sits close enough to the line that it is worth being careful. A reply to someone who has just rung you is responsive rather than unsolicited, which is a materially different thing from texting a list of numbers you obtained somewhere else. Do not do the second one.

Practical requirements: every message carries a clear opt-out, opt-outs are processed automatically and permanently rather than filed for someone to deal with later, the business identifies itself in the message, and you never message a number that did not contact you first. If you are unsure whether a particular sequence is marketing or service communication, treat it as marketing and give it the stricter handling.

There is also a cost. SMS is charged per message, and per segment once a message runs long. It is not much per message and it adds up across a busy month, particularly if you have built a two-message sequence on a number that gets a lot of missed calls. Price it in from the start rather than discovering it on a bill. Some businesses reduce the volume by routing to WhatsApp or by tightening the trigger rules. Our pricing page covers how message costs are handled.

How this fits with everything else

Missed call text-back is a patch over a gap. It is a good patch. But it is worth being clear that it does not answer the phone, and for some businesses the better answer is that something does. An AI receptionist picks up, takes the details and passes on a structured message, which is a different proposition from a text saying somebody will get back to you. Businesses with high call volume often want both: the receptionist handles the calls, the text-back handles overflow and out-of-hours.

The same logic applies on the website. Someone who lands on a site at nine in the evening is not going to ring, and an AI chatbot captures that enquiry in the moment rather than hoping they come back tomorrow. Different entry point, same principle: respond while the person is still there.

How it fails

Three failure modes come up repeatedly.

Nobody reads the replies. This is the worst one. The automation invites a reply, the reply arrives, and it sits unread in a system the business owner does not check. The customer has now been ignored twice and has evidence of it in writing. Whoever builds this must make sure replies land somewhere a human will actually see, with a notification, on the phone. Spotting that in advance is a matter of judgement rather than engineering, and judgement is most of the skill this work requires.

It fires when it should not. Existing customers get "sorry we missed your call" texts from a business they spoke to an hour ago. Suppliers get them. The owner's own family gets them. Every one of these is a small credibility loss and all of them are preventable with suppression rules.

It sounds like a machine. Overlong messages, three links, a footer, formal language. The message is competing with the other businesses the caller is about to ring, and the ones that sound like a person doing their job win.

None of this is complicated to build. It is a trigger, a delay, a message, a stop condition and a set of exclusions. The complexity is in getting the details right, and the details are what separate a system that recovers work from one that generates complaints. If you want to see how the pieces fit together across a full setup, the automation overview covers the wider set, and how it works explains the build process.