The lead was not lost. It was never answered.
Somebody asked for a price, abandoned a form halfway, or booked an appointment and did not turn up — and then waited. By the time anyone works down the list, the reason they were interested has passed. We build the follow-up that goes out while it has not.
One recovered lead, end to end
IllustrationTrigger · Quote form abandoned at the pricing step.
Sent
Hi — you were pricing a job with us earlier and didn’t get to the end. Want me to send the number, or is a quick call easier?
Reply
send the number
Handoff · Quote sent. Thread and full history handed to the rep who owns the account.
Interest has a shelf life.
The gap between somebody asking and somebody answering is where the revenue leaks out, and it is almost never a sales problem — it is a queue problem. Nobody decided to ignore that lead. It arrived on a Friday afternoon, behind forty others, and the person who would have called was doing something else. That gap is a schedule, and a schedule is the kind of thing you can automate honestly.
What actually happens when a lead goes quiet
The whole argument for this is in the machinery, so here is the machinery.
The trigger.
A form abandoned before it was submitted, a quote nobody replied to, a booking nobody showed up for, a thread that has been silent too long. You decide which events count and how long the silence has to be. Nothing fires on a guess about intent.
The message.
Written from what the record already holds — what they asked about, where they stopped, what your team would have said next. It reads like your business rather than a template with a first name dropped into it, because the wording is yours and you sign it off before anything sends.
The checks before it sends.
Opt-outs, suppression lists, duplicates, the hours you are willing to contact people, and anyone already mid-conversation with a human. Anything that fails a check is held rather than sent, and the reason it was held is on the record.
The reply.
It answers what it is allowed to answer — the price, the link, the next opening in the calendar — and nothing else. Negotiation, complaints, anything clinical or contractual, and anyone who sounds unhappy goes straight to a person with the thread attached.
The stop.
It stops on an opt-out, on a booking, on a handoff, and after the number of attempts you set. Follow-up that does not know how to stop is the reason people distrust this category, so the stop conditions are written down before the first message goes out.
The record.
Every message, every check, every handoff, with the reason attached and written back to the same CRM record your team already works in. If somebody asks why a particular person heard from you, the answer is a query rather than an investigation.
This is a pipeline, not an agent.
It is the same question we ask about every workflow, and for lead recovery the answer is not the fashionable one. Contacting your customers is not the place for a system that improvises.
Same input, same output
The same trigger has to produce the same message every time. That is ordinary code making the decision, with a model doing the part only a model can do — reading what the lead actually said.
Auditable line by line
Why this person was contacted, on which basis, and why the one next to them was not. A deterministic path answers that; a model deciding on its own each time cannot, and this is exactly the workflow where somebody will eventually ask.
The judgement is at the edge
Where real judgement is needed — an unhappy reply, an unusual question, a negotiation — the pipeline stops and a person takes it. That handoff is the design, not the failure case.
SMS and email
Which one, in which order, is a decision we make with you — not a default we ship.
SMS.
Where a short question gets a short answer the same afternoon instead of at the end of the week. It is the strongest channel for recovery and the one with the tightest rules around it, which is precisely why it is a decision rather than an assumption.
Email.
Room for the quote, the document, the calendar link, the thing that needs a paragraph. Slower to get an answer, and the right call whenever you do not hold a phone number or the permission to use one.
About permission
We message people who gave you a way to reach them, about the thing they gave it for. Opt-out is honoured on the first request, applied everywhere rather than per channel, and recorded. Where it is not clear what your list agreed to, that is a finding we hand you in the audit — not an obstacle we route around.
What you get
The map first, then the thing that runs on it.
The map of where leads stop.
Before anything sends: a written pass over your funnel showing where people drop, how long they sit there, who is supposed to pick them up and what happens instead. You keep that document whether or not we build the rest.
Connected to what already holds the lead.
Your CRM, your forms, your booking tool, your shared inbox. Follow-up writes back to the same record your team works in, so nobody ends up reconciling two versions of the same conversation.
Someone watching it in production.
Deliverability drops, a form changes shape, a provider starts filtering, a template quietly stops landing. Drift and silent failures are caught on our side rather than by you noticing it went quiet a fortnight ago.
Scheduled review of what it got wrong.
We read the conversations that went badly and change the thing that caused them. It improves because somebody is paying attention, not because it gets cleverer on its own.
How we start
The same four steps as any other engagement, in this order.
Audit.
A working session on how leads reach you and where they stop, and a written map of the gaps. It stands on its own as a deliverable, and it is what tells us whether this is worth building at all.
Scoped proposal.
Which triggers, which channel, what the messages say, what the stop conditions are, and what it connects to. Nothing goes out that you have not read first.
Built and connected.
We build it against your CRM and your forms, load your wording, and run it against real traffic under supervision before anybody calls it finished.
Continuous improvement.
Scheduled review of the replies, correction of the messages that are not working, and adjustment as your funnel and your tools change. Someone owns it after launch, and that someone is us.
How it is paid for
You pay on what is recovered. The specifics are scoped with the rest of the engagement rather than published here, but the shape of it is this: what we are paid comes out of revenue that was not going to arrive.
Questions about lead recovery
Start with the audit.
A working session on how leads reach you, and a written map of where they stop, how long they wait, and which of those gaps is worth closing. You keep it either way.