Missed call text back: the smallest automation with the biggest bill attached

A missed call is not a lost job yet. It becomes one somewhere between forty seconds and four minutes later, when the caller has gone back to the search results, dialled the next number down, and somebody there has picked up.

Missed call text back is the automation that occupies that gap. It costs almost nothing to run, it takes five minutes to switch on, and in a trade where a single job is worth a few hundred dollars it is the line item that most often covers the price of the whole crate inside the first month.

It is also the automation most often left half-built.

What it is, and what it is not

Missed call text back sends an SMS automatically the moment an inbound call ends without being answered. That is the whole mechanism. It is not voicemail transcription, it is not a callback queue, and it is not an answering service.

The reason it works is not clever. The person who rang you chose to ring you. They had a problem, they picked your number out of a list, and thirty seconds later they are still holding the phone. A text that arrives in that window is read. A voicemail notification in the same window is ignored, because almost nobody listens to voicemail from a business they have not bought from yet.

It is worth being precise about where this sits in a stocked crate. Every crate in the depot ships with an AI Receptionist as component one, and a receptionist that answers around the clock should mean very few calls go unanswered at all. Missed call text back is the floor underneath it: the calls that never reach the receptionist because a mobile was diverted, because a technician’s own line rang out, because a transfer to a human failed, or because the business routes to a person first and only falls back to the AI. Every one of those is still a missed call, and every one of them still needs a text.

The toggle, and the workflow

There are two ways to run it, and most accounts should end up on the second.

The built-in version lives in Settings, under Business Profile. Scroll to Missed Call Text Back, switch it on, write the message, save. One message, sent to everybody, every time, no conditions. It takes five minutes and it is genuinely worth doing on day one, because a plain message running today beats a clever one you will build next month.

The workflow version is a normal automation: Automations, then Workflows, then a new workflow with an Inbound Call trigger filtered to a missed call status. From there you can branch, which is the entire reason to graduate.

You graduate the moment any of these becomes true. You want a different message inside business hours and outside them. You want a different message on the sales number and the service number. You want existing customers treated differently from strangers. You want the contact written into a pipeline stage so the miss is visible on a board rather than buried in a conversation thread. The toggle does none of that. The workflow does all of it, and it takes about twenty minutes.

The copy is the product

Almost every underperforming missed call text back is a message problem, not a wiring problem. The message has four jobs, in this order: identify the business, say why the message arrived, ask exactly one question, and be answerable in four words or fewer.

Three worked examples, written the way a crate ships them, with the business name pulled from a custom value so the same message fits any account on the aisle.

“{{custom_values.business_name}} here, sorry we missed you. Is this a no heat call or a quote? Reply NO HEAT or QUOTE.”

That one is doing routing before a human is involved. An HVAC company treats an emergency and an estimate completely differently, and the difference decides whether somebody gets woken up. The reply is one word, which is why it comes back. It is the wording that ships in the HVAC contractor crate, and the same shape carries across most of the home and trade aisle.

“Hi, this is {{custom_values.business_name}}. We were with a client. Want us to book you in? Reply with a day and we will send times.”

That one explains the miss in a way that reflects well on the business. A salon that was with a client is busy and good, not disorganised. The question has a one word answer (a day of the week), and the promise made in return is small enough to keep. That is the register the salon and barbershop crate uses.

“{{custom_values.business_name}} here. We missed your call. Is this a new matter or an existing one? Reply NEW or EXISTING.”

That one sorts intake from client service, which in a firm are two different queues staffed by two different people. Sorting it in the first message saves the intake coordinator a call, and it is why the law firm crate branches on that answer rather than routing everything to one inbox.

What none of them do is say “we will get back to you as soon as possible”. A message that asks nothing gets nothing back, and “as soon as possible” is a promise with no time attached, which reads as a hedge. Keep links out of the first message too where you can. A link asks the caller to do more work than a reply does, and links in a first outbound SMS are the kind of thing carriers look at twice.

Five ways it goes quiet

• It fires on your own outbound calls. Somebody on your team rings a customer, the customer does not answer, and the customer receives a text apologising for missing their call. Filter the trigger to inbound only.
• It fires again, and again. A caller who rings three times in ten minutes gets three identical apologies. Set the workflow to run once per contact, or add a wait so the same number cannot retrigger inside a sensible window.
• It fires at 2am. A text at two in the morning is not a nice surprise. Branch on business hours and send a different message overnight, one that sets the hour you will actually reply.
• It fires to a landline. Nothing arrives, nothing bounces, and the record looks identical to a successful send. Nothing to fix here, just do not read the send count as a delivery count.
• It fires before the number is registered to send. This is the expensive one. In the US, unregistered application-to-person traffic is filtered or dropped by the carriers, silently, and the account shows the message as sent. Get the registration submitted before you need it, which is the whole argument in getting a snapshot approved to send.

The reply needs an owner

This is where most setups stop, and stopping here is what turns a good automation into a slightly worse missed call.

Somebody replies “QUOTE”. Now what. If the answer is “it sits in the conversations inbox until somebody notices”, the caller has been asked a question and ignored, which is a worse experience than never being texted at all.

Give the reply an owner in the workflow itself. Hand it to the AI Chatbot so the qualification continues in the same thread, notify a human on the numbers that warrant one, move the contact into a named pipeline stage so the miss is countable, and put a stop condition on every nurture sequence the contact might be sitting in so nothing talks over a live conversation. The AI receptionist fit-out service exists mostly because this half is the half that gets skipped.

What it is worth, on your numbers

Take a two-van shop with nobody permanently on the desk. If it takes 60 calls a week and misses 15 of them, and the text brings one in five of those callers back into a conversation, that is three recovered conversations a week. If one in three of those books, at an average job value of $450, the automation is worth around $450 a week on those assumptions.

Every number in that sentence is an assumption, including the miss rate. Change the job value to $180 and it looks very different. Change the miss rate to one in three and it looks better. Run it with your own four numbers before you believe any version of it, including this one.

The next decision

Switch the toggle on this afternoon, because a plain message running now beats a branched one running in three weeks. Then decide whether your account needs the workflow version, and the test is simple: if you have more than one number, more than one enquiry type, or hours outside which you cannot answer, you do.

After that the next gap worth closing is the one on the other side of the calendar, which is the hour after a missed appointment. Every crate in the catalog ships with both already wired, and the five-station walkthrough shows where each one sits on the line.