The problem with voicemail
Voicemail asks the caller to do work. They have to decide whether to leave a message, choose what to say without knowing who will hear it, and then wait. Most do not. And when they do, you receive a message you usually cannot reach immediately anyway.
Text-back inverts it. Instead of asking the caller to act, you send them a text while their phone is still in their hand.
The sequence, with timings
| When | What happens | Why the timing matters |
|---|---|---|
| 0s | The call rings out, forward, or hits after-hours | Detected from the call event, not from a human noticing |
| ~2s | A text goes out: the business name, one question | The caller is still holding the phone. This is the whole window. |
| On reply | The agent asks one qualifying question | One. Each extra question costs a reply. |
| Same thread | A concrete slot is offered — "2–4pm tomorrow?" | A specific option converts; an open invitation does not |
| On booking | Confirmation, address, and a reminder is set | Reminders are where no-show reduction actually happens |
Five seconds in, the conversation exists. By the time your competitor is listening to their voicemail, you are holding a thread.
Where implementations break
1. The text arrives from a number the caller does not recognise
A text from a random long number, minutes after a call, reads as spam. The message has to establish who it is in the first four words: "Smith Heating — you just rang us." Without that, you have converted a lead into an opt-out.
2. The reply does not escalate
The most common failure is a text-back that opens a conversation nobody is watching. The caller replies with their address and their problem, gets silence, and calls someone else. Routing the reply to a person — or to an agent with the authority to book — is the part that determines whether this is a lead-capture tool or a lead-destruction tool.
What to check before you trust it
- Does it fire on every path? Rings out, busy, after-hours, voicemail — all four. Deployments that cover only "ring out" miss the busiest failure mode, which is after-hours.
- What happens at 2am? A text is fine at any hour; it is the caller who decides when to read it. A call at 2am is not fine. Confirm which your setup does.
- Is the opt-out honoured on the thread? When someone replies "stop", that has to write to the record immediately.
- Can you prove it ran? You should be able to pull the log: call received at this time, text sent at this time, reply at this time, booking at this time.
You can watch the behaviour on the demo on our home page, and book 15 minutes to test it against your own call log.