Key takeaways
- A web or IDX inquiry can text the lead and hit your phone in single-digit seconds; the slowest leg in my stack is IDX, up to 60 seconds, because the vendor has no webhooks.
- The variable cost is two text messages per lead, about three cents at Twilio's published US rates; the fixed cost is a $1.15-a-month number plus carrier registration.
- The "78% of leads go to the first responder" stat has no primary source I could find; the HBR audit of 2,241 companies does, and it found responders inside an hour were about 7x as likely to qualify the lead.
- Step one of a multi-step form should already create the lead. Everyone who quits on step two still has a phone number in your hand.
- Never silently delete spam. Tag it, email it, and let the human decide. The one time a filter is wrong, it ate a commission.
The short answer: under 60 seconds, a few cents of texting per lead, and no ISA
Under 60 seconds is not a goal; it is what the pipeline does once the first step is code. On the broker site I shipped this month in Alexandria, every inquiry hits one Netlify function, which sends four messages before anyone has opened an inbox:
- A push notification to her phone with the lead's name, what they want (buy, sell, home value) and a tap-to-call button. This is the one she sees first.
- A text message to her cell with the same details, for the days the push app is muted.
- An email with every field, the page they were on, and tel: and sms: links, copied to me.
- An auto-reply to the lead, by text and by email, in her name, promising a real reply within the hour.
When I submit a test lead, the push lands first, the text a few seconds behind, the email last, all well inside the headline number, and the lead's phone buzzes in the same breath. The one slow leg is IDX: her search vendor has no webhooks, so a listing-page lead can sit up to a minute before my poller picks it up. Still under a minute. Still no ISA.
There is no CRM login in that chain and no Zapier. The same function, with different words, runs the snow-plowing sign-up for Revisions Unlimited: a homeowner submits the form and appears as a prospect in my route app, with a push to my phone, before closing the tab. It is the lead engine I now ship inside every custom agent site I build.
What the speed-to-lead stats actually say (and which ones have no source)
Every vendor page recycles the same two numbers, so before I built anything I read where they come from.
The number with a real source
Harvard Business Review, March 2011, "The Short Life of Online Sales Leads" (hbr.org/2011/03/the-short-life-of-online-sales-leads). The authors audited 2,241 US companies by submitting a web lead and timing the response: average first response 42 hours, 23% never responded, and companies that reached out within an hour were nearly seven times as likely to qualify the lead as those that waited even one more hour. It is B2B and fifteen years old, but it has a method and a sample size.
The "21x" number
The line about the odds of qualifying a lead dropping 21-fold between 5 and 30 minutes comes from the Lead Response Management study, InsideSales data analysed with an MIT professor (leadresponsemanagement.org/lrm_study). Vendor blogs date it to 2007. When I opened the study page this week it showed no year, described the first-hour drop two different ways, and was padded with casino ads. Use the direction of the finding, not the decimal places.
The number with no source
"78% of buyers go with the first agent who responds" appears on dozens of pages and I could not trace it to a study. Every citation points to another vendor blog, and one stats page links an NAR report that does not contain the figure. The published "average agent response time" numbers ranged from a couple of hours to two days, none with a method. If a salesperson quotes any of it, ask for the PDF.
So I used a stopwatch. The honest claim is not "you will convert 21x more." It is "your lead hears from you in seconds, and your phone has their number before they have finished scrolling." That is measurable from a friend's phone, and it is the only claim in this post or in the calculator below, which runs on hours, not probabilities.
The stack: one function, four messages, nothing to log into
One serverless function and four free or near-free services underneath it. No CRM login, no Zapier.
- Every form posts to one Netlify function. Contact page, buyer form, home-value funnel: all submit to one endpoint with the page, the source and the intent.
- The function validates, then fans out in parallel. Resend sends the email, Twilio the text to her cell, ntfy the push with a tel: link. If the auto-reply flag is on, the lead gets their copy from the same two services. Each provider has its own timeout, so a slow email API cannot hold up the text.
- A ledger entry is written to Netlify Blobs, so there is a record even if her phone is dead.
- Staging never texts the client. Previews and branch builds route every lead to me. Only the production build sends to her, because a test lead at 11 p.m. should wake me up, not her.
Two design rules matter more than the vendor names. First, delivery never waits on the database. In October one build shipped without a dependency and the ledger and rate-limit writes failed silently for days; the texts, pushes and emails kept delivering because they never waited on that write. I would rather lose a log line than a lead.
Second, nothing lives in the browser. The texting number, API keys and push topic are environment variables with no fallbacks. If one is missing, the function stops instead of quietly sending leads to a dead address.
The message copy that doesn't read like a bot
The automation is only as good as the words, and most auto-replies sound like a vending machine. Here is what goes out, with the broker's details swapped for placeholders. Edit it, do not copy it; your lead can tell.
To the lead, by text, within a few seconds:
Hi {first name}, this is {agent} with {brokerage}. I got your message about {the property, or "your home's value"} and I'll reach out shortly. Call or text me anytime at {agent's cell}.
To the lead, by email: the same two sentences and her signature. No listing carousel, no buyer guide. Its only job is to prove a human is on the other end.
To the agent, by text and push:
New {buy / sell / home value} lead: {name} {phone}, {city}. "{first 80 characters of their message}" Reply or call now.
My rules:
- First name, real agent name, real cell number. Anonymous "our team" replies get ignored.
- Promise a time you will beat. Her site says replies within the hour, seven days a week, so the auto-reply says "shortly" and she calls in ten minutes.
- One next step, no links; a link in a first text from an unknown number looks like phishing.
- Put a consent line under every phone field (you agree to receive a text reply; reply STOP to opt out) and honour STOP. An inbound-SMS function records the opt-out so the auto-reply skips that number.
- It is a reply to something the person just did, not a drip campaign, and I do not bolt one on.
IDX leads arrive late, and the multi-step form trick
Why IDX leads arrive late, and how I poll them every minute
The listing search on most agent sites is a hosted IDX product on a subdomain, not part of the site. When a buyer asks about a listing there, the lead lands in the vendor's dashboard and the vendor emails the agent. Her vendor offers no webhooks, so it cannot call my function the way the site forms do.
The fix is boring: a scheduled function asks the vendor's API for new leads once a minute, and anything new goes down the same fan-out as a site form. The worst case is a lead sitting sixty seconds. If you are choosing an IDX vendor, ask one question before price: "Do you have lead webhooks?" The one I shortlisted that does cuts that minute to seconds.
Step one already creates the lead
Her home-value and buyer forms are three steps. Most multi-step forms wait until the last step to submit, so everyone who bails on step two never existed. On her site, step one asks only for a name, a phone or email, and what they want, and it posts immediately. The lead exists, the push has fired, the auto-reply is out.
Steps two and three gather the address, timeline and price range, then the function sends one grouped email instead of three alerts for one person. The step state lives in session storage, so a refresh does not lose the form. On every single-page form I have run, the people who started and quit were invisible to me. Now that leak is a lead with a phone number.
Rate limits, no PII in logs, and the spam you still have to route
A public endpoint that sends text messages is a target. Here is what the function does that form plugins do not.
- Honeypot field. A hidden input humans never fill in. If it has a value, the submission is flagged.
- Conservative spam heuristics. Non-Latin scripts with no local words, three or more links, adult or crypto terms. Flagged, not dropped: the lead is still stored and emailed with a "[possible spam]" tag so a human decides. I tightened my own agency site's filter this month after four bot leads got through; borderline still gets emailed. A wrong filter eats a real buyer.
- Rate limits on hashed keys. An hourly per-address bucket and a site-wide hourly cap, keyed by hashes so the ledger never stores an IP address.
- No personal information in logs. The function logs that a lead arrived, which channels succeeded and how long each took. Names, phones and messages go to the agent and the ledger, never to the host's log stream.
- Provider timeouts. Every outbound call has a deadline; one slow vendor cannot fail the whole lead.
- Secrets only in environment variables. That includes the push topic: a free push topic is a bearer secret, and anyone who learns the string can subscribe. I rotated mine more than once this fall after older sites shipped it in client-side JavaScript; the browser never talks to the push service now.
- Origin checks. The function only accepts posts from the site's own domain, so a copied form on someone else's page cannot spend your texting budget.
None of this is exotic. It is a page of code, but it is the page missing from every "connect your form to Zapier" tutorial, and it is the difference between a lead engine and a liability. It is most of what I mean by automation for a small office: not a chatbot, a pipe that never drops anything.
What the texting layer costs, what an ISA or a $300 CRM costs, and the 10-minute human call
What the vendors underneath charge for the texting and alerting layer, at published list prices, for a solo agent handling about forty inquiries a month:
- Texts: two per lead, one to the agent and one auto-reply. Twilio's published US rate is $0.0083 per message plus a carrier fee under half a cent (twilio.com/en-us/sms/pricing/us). Call it three cents a lead, about $1.20 a month.
- Phone number: $1.15 a month, plus the one-time A2P 10DLC business registration and a small monthly campaign fee US carriers require before they deliver business texts. Start that paperwork first; mine meant identity verification and days of waiting, and the auto-reply stays off until it clears.
- Email, push, hosting: Resend's free tier, the free ntfy app and Netlify's free function tier cover this volume. Zero.
Those are the vendors' charges, not a price for the system. The outsourced ISA quotes I have looked at start in the four figures per month, and a real-estate CRM at two or three hundred a month still relies on you opening the app. Our side is a set price for the build, as part of a site we are building or standalone on one you already have, then a monthly plan for only the services you use, priced to compete with those CRMs; here is how we scope it.
The calculator above uses hours, not probabilities, on purpose: what you get back is the time spent checking inboxes, copying numbers into your phone and typing the same first text, plus the leads that went cold during a showing.
The 10-minute human call: what the automation hands you
Nothing here closes a deal. The lead got a text proving someone is awake, and your phone has their name, intent, city, first sentence and a button that dials them. Use it in the next ten minutes: call, open with their own words ("you asked about the lake place on Darling"), and set one next step. The auto-reply bought the window; beating the time it promised earns the trust.
Setup checklist for a solo agent
- Pick the one phone that gets every alert and install a push app on it.
- List every place a lead can arrive (site forms, IDX, portal emails, Facebook lead ads); each needs a path into the same function.
- Register your texting number (A2P 10DLC) before you need it.
- Write the auto-reply in your own words and promise a time you will beat.
- Add the consent line under phone fields and handle STOP.
- Make step one of every form create the lead.
- Tag spam, never delete it.
- Test from a friend's phone with a stopwatch, on a weekend.
Frequently asked questions
Inside five minutes is the number everyone quotes, but the practical answer is two-part: the lead should hear from you automatically in under a minute, and from a human within whatever time your auto-reply promised. On the stack I run, the automatic part takes seconds and the human part is a ten-minute call.
The 78% and 74% figures you see on vendor pages have no primary source I could find. The best-documented number is the 2011 HBR audit of 2,241 companies: those that responded within an hour were about seven times as likely to qualify the lead as those that waited even one more hour. Treat the direction as true and the percentage as marketing.
One server function receives every form and IDX lead, then emails you, texts you, pushes to your phone with a tap-to-call button, and sends the lead a short auto-reply by text and email. IDX leads are pulled by polling the vendor's API every minute when the vendor has no webhooks. No CRM is required, and the texting runs about three cents a lead at Twilio's rates.
Their first name, your name and brokerage, what they asked about, a promise you will beat, and your cell number. Two sentences, no links, no emojis. Then call within ten minutes and open with their own words.
A single reply to something the person just did does not annoy anyone; a drip of five texts does. Keep it to one honest acknowledgement, put a consent line under the phone field, honour STOP, and let the human call do the rest.
Yes. If your IDX vendor offers webhooks, the lead posts to your function instantly. If not, a scheduled job polls the vendor's lead API every minute and anything new goes through the same text-and-push pipeline, so the worst case is about a sixty-second delay.
Want your leads answered in under a minute?
Tell me where your leads come from today and which phone should buzz. I'll come back with a clear scope, a set price for building the whole alert-and-reply stack, and a monthly plan for only the services you need, priced to compete with the CRMs. Our development team builds it around how you work your leads.
Founder, Style Marking · owner, Revisions Unlimited. Jacob builds custom websites, apps and operations systems for small-business owners — and runs a remodeling company on the same tools he builds for clients. Every post here comes from systems he has actually shipped.