Contents
At a glance
- Category
- Voice and messaging
- Trigger
- A telephony webhook on a no-answer, busy or voicemail call status
- Speed target
- Seconds, while the caller still has the phone in their hand
- Message rules
- Identify yourself, say why, ask one easy question, set an expectation
- Where AI helps
- Reading the reply, extracting need and timing, drafting a response for approval
- Measure
- Reply rate, replies that become jobs, and time to first human response
What missed-call text-back is
Missed-call text-back is the automation that detects an unanswered inbound call and immediately texts the caller. It is the single most commonly deployed automation in service businesses, and it is popular for an unglamorous reason: for a trades business, a salon or a clinic, an unanswered call is usually a customer who is now ringing your competitor.
The mechanism is simple - a call ends without being answered, so a text goes out - and the value comes entirely from speed. A text that arrives while the caller is still holding the phone converts far better than one sent an hour later, which is the whole argument of speed to lead.
How it is built
Five steps. Your phone system fires a webhook when a call ends with a no-answer, busy or voicemail status. The workflow filters out the cases you do not want to text - internal numbers, withheld numbers, existing customers mid-job, anyone on the suppression list. It looks the number up in the CRM to decide whether this is a new enquiry or an existing customer.
It sends the text, with the wording chosen for that case. And it creates or updates a record so the missed call and the reply are visible to whoever picks it up. The full build guide walks through it in n8n; the same shape works on any platform with a telephony webhook.
What to actually say
Four rules that make the difference between a text that gets a reply and one that gets ignored. Identify yourself immediately - the recipient is looking at an unknown number and has two seconds of patience. Say why you are texting: "sorry we missed your call". Ask one specific question that is easy to answer by thumb, such as what they need and roughly when.
And set the expectation - when a human will follow up. Keep it short enough to read in a notification preview, and include an opt-out where required. Avoid the temptation to sell; the job of this message is to keep the conversation alive, not to close.
Where AI helps, and where it does not
The basic text-back needs no model at all - it is a filter and a send. AI earns its place at the second step: reading the customer's reply, extracting what they need and when, classifying urgency, and drafting a suitable response for a human to approve. That is a textbook agentic workflow, and it is where the time saving actually appears.
Be careful about full autonomy. An agent that books directly from a text conversation is achievable and requires real guardrails: check availability properly, never promise a price, and hand off on anything that reads as a complaint or an emergency.
Compliance and what you should know
Texting someone who just rang you is generally on solid ground as a response to their own contact, but it is still a business text: in the US it is subject to A2P 10DLC registration, and STOP handling applies everywhere. Register before you launch, because approval is the long pole.
Then measure it properly. Reply rate, the share of replies that become booked jobs, and time to first human response are the three numbers that tell you whether it is working - and they are the inputs to cost per booked job, which is what makes the case for keeping it.
Missed-call text-back FAQ
What is missed-call text-back?
An automation that texts anyone whose call you did not answer, usually within seconds. It turns a call that would have gone to voicemail and disappeared into a live text conversation, which is why it is the most commonly deployed automation in service businesses.
How quickly should the text go out?
Within seconds, while the caller still has the phone in their hand. The entire value is speed - a text that arrives an hour later reaches someone who has already rung a competitor, and the reply rate falls off sharply with delay.
What should the text say?
Identify your business immediately, apologise for missing the call, ask one specific question that is easy to answer by thumb, and say when a human will follow up. Keep it short enough to read in a notification preview and do not try to sell.
Do I need AI for missed-call text-back?
Not for the text itself - that is a filter and a send. AI earns its place on the reply: reading what the customer wrote, extracting what they need and when, judging urgency, and drafting a response for a human to approve. That is where the time saving actually appears.
Is it legal to text someone who called me?
Responding to someone's own contact is generally on solid ground, but it is still a business text. In the US it falls under A2P 10DLC registration, and opt-out handling applies everywhere. Register before launch, because carrier approval takes days and is the long pole.
How do I know if it is working?
Three numbers: what share of texts get a reply, what share of replies become booked jobs, and how long until a human responds to the reply. Those feed straight into cost per booked job, which is the figure that justifies keeping it running.
Primary source
Twilio - A2P 10DLC compliance for business texting
Checked August 2026. Anything priced or rate-limited moves, so verify against the source before you budget.
Want this built rather than explained?
Knowing what missed-call text-back means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.
