Every phone call ends in a status: answered, rang out, busy, or abandoned before voicemail. On an ordinary line that status vanishes the moment it happens. This system exists because the status can instead be caught, and something useful can fire from it.
What fires, and when
The build places a programmable number in front of the business's published line. Calls forward straight through to the shop phone or the owner's cell, so nothing changes about how a call feels. But when a call ends, the carrier platform reports how it ended — completed, no answer, busy, failed, or abandoned. Any outcome except "completed" triggers a webhook, a small message carrying the caller's number, the time, and the status, to a workflow that decides what happens next. When the decision is yes, a text is on its way within seconds. Five to thirty seconds to delivery is typical, and most of that is carrier time, not code.
The checks between the hang-up and the send
The deciding step is where careful implementations separate from lazy ones. Before anything sends, the workflow checks whether the number is a mobile line at all, because landlines swallow text messages silently — the message dies, the caller never sees it, and the owner assumes the lead was covered. It checks whether this number already received a text today, so a customer who calls twice is not messaged twice. It checks whether the number is a known robocall source, which deserves nothing. It checks whether the call landed during business hours, after hours, or on a holiday, which changes the wording. Skip these checks and the system texts fax lines and autodialers while the owner believes every missed call is handled.
What the customer receives
A short message, from the business by name, arriving while the phone is still in their hand: the business is sorry it missed them, a reply to this thread will reach a person, and if the matter is urgent, here is a number that will be answered. The naming is not a courtesy — identifying the sender is required in business texting — and the immediate call path matters because a text is not an adequate answer for someone with water coming through a ceiling. The message's job is narrow: keep the enquiry alive for the minutes it takes a human to get free, before the caller dials the next name on their list.
Where the reply lands
The most common failure of these systems is not technical. The text goes out, the customer replies, and the reply sits in a dashboard nobody opens. The build routes replies to a place the owner already looks — their own phone, or an inbox that is part of someone's actual day — and logs every thread with its source and timestamp. The log is not bureaucracy. It is how, at month three, you can count what the system caught instead of guessing.
What the evidence says about waiting
Two recent, large sources are worth citing plainly. CallRail's 2025 survey of 1,000 US consumers found 78 percent abandon a business after an unanswered call, and 82 percent say they would call a competitor next. Invoca's 2025 analysis across more than 60 million calls found 61 percent of callers reach a person, meaning roughly two in five do not. The exact share varies by trade and season. The mechanism does not vary: a caller with a real problem treats your voicemail as a busy signal and keeps dialing.
The paperwork comes first
US carriers block application-generated texting from unregistered numbers. Launching this legitimately means registering the business and its messaging use case through The Campaign Registry — legal name, EIN, sample messages — and the review takes days to weeks, not hours. Week one is paperwork, and anyone promising a Monday launch on a Friday handshake is planning to send unregistered traffic, which carriers do not merely block but filter silently: messages report as sent and never arrive. There is also a consent line that must never be crossed. A text replying to someone who called you minutes ago is transactional and defensible. Using those same numbers later for promotions is marketing, which requires prior express written consent under federal law. The rules for texting customers are their own subject, worth reading before anyone proposes a blast.
What it recovers, honestly
Enquiries, not jobs. The system converts a dead end into an open thread, and a human still has to answer the thread, quote the work, and win it. It does nothing for callers on landlines. It is not an emergency answer by itself, which is why the message always carries a call path. If replies go unanswered, it becomes an accurate record of losses rather than a recovery system. The running cost is small — programmable-SMS platforms publish US rates under a cent per message segment (Twilio's public price list is representative), so a hundred missed calls cost a few dollars in messages — but the value depends entirely on what a recovered enquiry is worth in your shop, computed from your own call volume, close rate, and average ticket, not from anyone's industry statistic.
Where to start
Open your phone's call log for last week and count the inbound calls with no matching outbound call the same day. Write down how many were probably work. That count, against your average ticket, is the size of the problem — and it is a number you can produce without buying anything.