The 60-second lead-reply SLA — how we set it up end to end

There is one piece of inbound-marketing research that almost everyone in lead-response sales has cited at some point: the 2007 Harvard / InsideSales study (later popularized by Lead Connect) showing that the odds of qualifying a lead drop dramatically as response time stretches past five minutes.

The specific finding varies by re-telling, but the direction is consistent across follow-up research: replying inside 5 minutes versus inside 30 minutes makes you roughly 10x more likely to actually connect with the lead, and 4–6x more likely to qualify them for a sale.

The 60-second SLA, defined

First-touch under 60 seconds means: from the moment a lead clicks submit on the form, the lead receives a real-feeling SMS in their pocket within 60 seconds. Not an email. Not a call. An SMS. The reason is delivery latency: emails sit in inboxes, calls require the operator to be at their desk, but an SMS hits the lock screen of a phone the lead is still holding.

The four-webhook contract

Webhook 1: Form submit → CRM

The form posts to a serverless endpoint (Vercel Functions, Cloudflare Workers, whatever). The endpoint validates the payload (Zod or similar), assigns a UUID, and writes a row to the CRM. The CRM is whatever you already use. The endpoint does NOT wait for the CRM to confirm — it fires the next webhook in parallel.

Webhook 2: Form submit → SMS

Same trigger, parallel path. Twilio Programmable Messaging fires an SMS to the lead's phone within ~2–4 seconds of submit. The message is short and signed: "Hi [first name] — this is [owner name] at [business]. Got your inquiry about [service]. I'll text you back within 5 minutes — what's the best number to reach you on?"

The signed-by-a-real-name part matters. Per BrightLocal 2024, 71% of consumers say a personalized response in a local-business interaction makes them more likely to continue the conversation. "Thanks for your interest! A representative will be in touch shortly" reads as a bot. "Hi Sarah, this is Mike" reads as a person.

Webhook 3: Form submit → owner/operator notification

Same trigger, third parallel path. A push notification to the operator's phone (via Slack, ntfy.sh, or just an SMS to the operator's number) with the lead details, formatted as a single tap-to-call link.

Webhook 4: Form submit → calendar

Optional but valuable. The SMS in webhook 2 includes a calendar link ("or book a 15-min consult here: [link]"). The link is a pre-configured Cal.com or Calendly with 15-minute slots. Some leads will self-serve, which means the operator never even has to make the first call.

Tooling cost

All-in monthly cost to run this for a small operator: Twilio ($20–$60/mo depending on volume), Make.com ($16/mo on the entry plan, $29/mo on Core), Cal.com or Calendly ($10–$15/mo). Call it $50–$100/mo total. The recovered revenue from leads that would otherwise have gone cold is consistently 20–40x that in audits we've run.