Speed-to-Lead Automation A personal reply to every lead in under two minutes, in your voice
Every new lead gets a personal reply in under two minutes, in your voice, day or night within your hours.
- Installed for you · one-time$249
- Run for you$197/month
- Custom build · this process$2,000–3,500 one-time
- Starts whenNew lead (portal email, site form, the CRM)
Per agent or small team, up to 500 leads a month, one CRM. Conversational qualification over several turns by SMS, a voice agent for missed calls, or lead routing across a team are a custom build. Custom builds start at $2,000 site-wide; this band is for this process and its integrations.
Speed-to-Lead Automation is an automation Agentmelt installs in Twilio. The free template is a file you import yourself; the kit ($49) adds the setup guide and prompts. Installed for you costs $249 one-time and is live within two working days of access, with a recorded walkthrough and 30 days of fixes. Run for you costs $197/month, with setup and maintenance included. A custom build of this process is $2,000–3,500 one-time; custom builds start at $2,000 site-wide. No call is needed for any option. Written by Max Zeshut; last revised 2026-09-21.
Reference stack: Claude + n8n. Node names are on each step; the file is under the template.
Founder at Agentmelt
Reviews every build before it goes live; the workflow escalates to a person, never past one.
What is speed-to-lead?
Speed-to-lead automation answers the lead before the lead has moved on: a new enquiry from a portal, the website or the CRM is looked up, qualified from what it says, and answered within two minutes with a two-sentence reply in the agent’s voice and one qualifying question — from the agent’s own address, inside quiet hours and consent rules — then logged in the CRM, handed to the agent with the context, and followed up on silence. Leads contacted within five minutes convert many times more often than leads contacted the next morning, and nobody who works alone can do that all day. Built for real-estate agents first; the same pattern serves any practice that sells by enquiry.
- A Zillow lead came in at 9 pm and got a reply at 9 am, after they had booked with someone else.
- Replies stop for the afternoon during showings and the leads pile up.
- The first message is a form letter and the lead can tell.
- Follow-up after a silence never happens.
- The ‘AI ISA’ we tried texted a client at 3 am.
If two of these are yours, this is the process to look at first. Free audit — or read on.
What it looks like once it runs.
Leads contacted within five minutes convert many times more often than leads contacted the next morning, and almost nobody who works alone can reply within five minutes all day. The workflow takes each new lead from the portal, the site or the CRM, looks up what is already known, qualifies from the enquiry text, drafts a two-sentence reply in the agent's voice with one question, holds it until quiet hours end, sends it from the agent's own address, logs the exchange to the CRM, and texts the agent a three-line summary when the lead answers. A quiet lead gets one nudge; a reply stops the automation and hands the conversation to the agent.
- 9:40 pm A lead arrives from the portal: “Interested in 42 Maple Ave.” Their record is looked up — a past client is not treated like a stranger.
- 9:40 pm A two-sentence reply in your voice, with one question, is drafted; it waits because it is after your quiet hours.
- 8:00 am The reply goes out from your own address.
- 8:35 am They answer “three months, pre-approved.” Tagged hot; you get a text with the summary and the number.
- Day 3, silence One nudge with two showing slots. Any reply stops the automation and hands you the thread.
The first reply goes out between appointments, hours later, and a third of leads never get one. The ones who do get a template. By the time the agent is free, the lead has heard from someone faster.
Every lead gets a personal first reply in under two minutes, day or night within your hours; the answers land in the CRM; the agent only picks up conversations that have started.
Trigger, then 8 steps.
All eight steps run without anyone; a person sees only what the guardrails escalate.
New lead (portal email, site form, the CRM)
Receive the lead
Name, email, phone, source, the property or page they enquired from, and their message. Portal emails are parsed for the same fields.
Look up the lead in the CRM
Existing record, past conversations, stage, and any notes — so the reply does not treat a past client like a stranger.
Qualify
Timeline, pre-approval, price band and intent from the enquiry text; 'hot' only when the timeline is near and something specific is named. Nothing is inferred beyond the text.
Draft the first reply
Two to four sentences in the agent's voice, referencing the property or page, with exactly one question. Fair-housing wordlist applied.
Check quiet hours and consent
Holds the message until quiet hours end in the lead's time zone; checks that a phone number came with consent before any SMS; skips leads who opted out.
Send the reply
From the agent's own address, threaded to the lead's email where there is one; SMS as an optional second channel.
Log and hand off
Note and stage written to the CRM; hot leads text the agent a three-line summary with the number to call.
Follow up on silence
Two days without a reply: one nudge that offers two showing slots or asks what they are after. A reply at any point stops everything and forwards the thread to the agent.
No step waits for a person.
What the workflow hands to someone, by rule:
- Approval mode for the first week: drafts go to the agent for a tap before sending.
Every lead gets a personal first reply in under two minutes, day or night within your hours; the answers land in the CRM; the agent only picks up conversations that have started
Every lead gets a personal first reply in under two minutes, day or night within your hours; the answers land in the CRM; the agent only picks up conversations that have started.
No decisions needed. Anything the guardrails flag is handed to a person; the rest ran alone.
Each pattern page explains it in plain words and lists every automation that uses it.
The template is built on n8n (how the n8n AI Agent node works); the same steps run on Make, Zapier or plain code. The tool is chosen to fit your accounts, you own the result, and the template comes in all three formats.
Data it touches
- Portal lead emails or site form
- CRM (Follow Up Boss, kvCORE, HubSpot)
- Agent voice samples
- Calendar for showing slots
- Consent and opt-out records
Guardrails
- Quiet hours: nothing sent 9 pm–8 am in the lead's time zone; messages queue until morning.
- One question per message; the second message asks the next question, never both at once.
- SMS only with a number the lead gave on a form; STOP honoured on the first word and written to the CRM.
- Fair-housing language check on every draft; flagged drafts cannot be sent.
- Approval mode for the first week: drafts go to the agent for a tap before sending.
Two minutes is the whole product
Everything else in the workflow exists to make a two-minute personal reply safe: the CRM lookup so past clients are recognised, the quiet-hours hold so nobody gets a message at 2 am, the consent check so no text goes to someone who did not give a number, the one-question rule so the reply reads like a person. Speed without those is a spam machine; those without speed is what the agent already has.
The reply is written from the agent's own messages
Three past messages the agent actually sent are the voice sample. The draft borrows their length, their greeting, whether they use the lead's first name, and whether they write 'Hi' or 'Hello'. The result is not indistinguishable from the agent — it does not need to be — but it is recognisably theirs, which is what a lead is comparing it against.
Hand off on reply, not on schedule
The workflow's last job is to get out of the way. Any reply from the lead stops the sequence, forwards the thread and texts the agent a three-line summary — timeline, pre-approval, what they asked. From there the agent is talking to a person who has already answered the first question, which is a better start than most first calls.
What it connects to.
| Tool | Role in this workflow |
|---|---|
| n8n | Intake, lookup, timing, sending, logging |
| Claude | Qualification and the reply in the agent's voice |
| Follow Up Boss / kvCORE / HubSpot | Lead record, notes, stage |
| Gmail / Outlook | Sending from the agent's address; reply detection |
| Twilio | Optional SMS to the lead; the hand-off text to the agent |
Want this running without building it?
$197/month
We set it up in your tools, run it on our servershost it on our n8n cloud (or deploy it to your own n8n, Make or Zapier), watch it, and fix it when something changes. Setup included, cancel monthly; the automation stays yours if you leave.
$2,000–3,500 one-time
Your systems, your rules, your edge cases. A one-off build delivered into your accounts to keepon Claude and n8n, delivered into your accounts to keep, with documentation and a recorded walkthrough.
Per agent or small team, up to 500 leads a month, one CRM. Conversational qualification over several turns by SMS, a voice agent for missed calls, or lead routing across a team are a custom build.
Also sold one-time, installed in your own accounts, as part of the real-estate agents package and the sales reps package and the small business owners package — do it yourself $49 · installed for you $249 · done for you $490.
When this becomes a custom build.
The subscription covers the standard version — $197/month, setup and maintenance included. Three things move it to a custom build ($2,000–3,500 one-time), delivered into your accounts to keep. If one of them is you, say so on the audit and the plan prices both.
A voice agent that answers missed calls during showings and books the appointment.
Conversational qualification over several turns by SMS, with the consent records that requires.
A team or brokerage with lead routing, round-robin and a voice per agent.
Running the standard version first is the usual path: the exceptions it logs in the first month are the scope of the custom build, with your own numbers. How custom builds work.
Frequently asked questions.
Does it reply from my address?
Yes. Email goes out through your Gmail or Outlook, threaded to the lead's message. SMS, if you switch it on, goes from your Twilio number with your name.
What if the lead replies at night?
Nothing goes back until 8 am in their time zone. The reply itself is forwarded to you immediately, so you can answer by hand if you want to.
How is this different from inbound lead qualification?
That blueprint is for a sales team: it enriches, scores and routes to a rep. This one is for a person who is the rep: it replies to the lead, holds the conversation until they answer, and hands it to you.
Does speed-to-lead automation reply from my own address?
Yes — the reply goes from the agent’s email or number, in the agent’s voice from a voice guide, and the conversation continues in the agent’s inbox. The lead never sees a bot address; the agent takes over the thread with the context already logged.
What if the lead writes at night?
Quiet hours are a rule: the reply is sent at the start of the next allowed window, and the lead still gets an answer before the competing agent has had coffee. A voice agent that answers missed calls during showings and books the appointment is a custom build on the same record.
How is this different from inbound lead qualification?
Inbound lead qualification is the company version: enrichment, an ICP score, routing to a rep by territory. Speed-to-lead is the solo version — one agent, portal enquiries, a reply in seconds around the clock, qualification by conversation rather than by firmographics. Same pattern, different first minute.
What this blueprint is built on.
Vendor documentation the steps rely on, and the rules the guardrails are written against.
- Follow Up Boss — API documentation docs.followupboss.com/
- FCC — Telemarketing and robocalls (TCPA) www.fcc.gov/general/telemarketing-and-robocalls
- Twilio — Programmable Messaging docs www.twilio.com/docs/messaging