How Fast Should You Reply to a Website Enquiry?

Reply in under five minutes. Ideally under sixty seconds. That is the practical target if you want website enquiries to convert instead of cooling into cold outreach. Everything longer trades conversion for convenience, and the data across large lead samples is consistent on the direction even when exact multipliers differ by study.

Most teams still miss it. Average response among companies that bother to reply sits near forty-two to forty-seven hours. A large share never reply at all. Speed is not a soft preference. It is one of the few levers that moves qualification and close rates without rewriting your offer.

What the studies actually measure

The classic InsideSales / MIT lead response work (Oldroyd and collaborators, analyzing tens of thousands of leads and later larger XANT samples) found leads contacted within five minutes were about twenty-one times more likely to qualify than those contacted after thirty minutes. Reach and connect odds versus a thirty-minute delay ran far higher still in the early analyses. Qualification odds fell sharply inside the first hour. Later multi-million-lead samples still showed roughly an eight-times conversion advantage inside five minutes versus slower contact.

Harvard Business Review’s 2011 audit of more than two thousand US firms reported average response near forty-two hours among responders. Only about thirty-seven percent replied within an hour. Roughly a quarter never responded. Firms that responded within an hour were nearly seven times more likely to qualify a lead than those that waited one more hour, and more than sixty times more likely than those waiting a day or longer.

Velocify’s analysis of millions of leads pushed the peak earlier: contact inside one minute (the so-called platinum minute) produced about a 391 percent higher conversion rate than waiting two minutes or more. The curve drops steeply after that first minute.

Other repeated findings line up:

• Lead Connect–style surveys: about seventy-eight percent of buyers say they buy from the first company that responds; a large share of sales go to the first vendor, not the “best.”
• Drift mystery shops of hundreds of B2B and SaaS companies: only about seven percent responded within five minutes; many took days or never replied.
• RevenueHero’s 2024 look at roughly one thousand B2B companies: average around one day five hours, with a majority never responding in the audit window.
• Optifai’s 2026 pipeline study (N=939 B2B SaaS firms with CRM timestamps): average B2B response about forty-seven hours; only twenty-three percent inside five minutes. Close rates in that set: under five minutes 32 percent, under one hour 24 percent, under twenty-four hours 15 percent, over twenty-four hours 12 percent. Form fills averaged about twenty-eight hours; best-in-class near three minutes with close rates lifting into the high thirties from the mid-teens. Live chat averaged about eight hours; phone was faster.
• Hennessey Digital’s 2025 law-firm lead-form study: twenty-five percent under five minutes (up from thirteen percent prior), median about thirteen minutes, fifty-six percent within an hour, twenty-six percent never or after seven days.
• SetSmart’s 2026 AI DM analysis across hundreds of thousands of conversations: AI responses under five seconds versus multi-hour human averages, with full coverage inside five minutes.
• Auto retail (Pied Piper–style scoring): top performers far more likely to respond within thirty minutes and sold substantially more vehicles from the same web lead volume.
• Home services and contractor audits: averages often forty-two minutes to several hours; evenings and weekends commonly delayed; first responder wins a large majority of hires.

Composite decay is ugly and familiar: under one minute is the peak; one to five minutes remains strong; five to thirty minutes loses most of the qualification advantage; thirty to sixty minutes decays further; one to twenty-four hours sits in mid-single-digit closes in several modern CRM sets; beyond a day is near cold. Never-respond is zero.

Exact multipliers vary by sample, lead quality, and whether the metric is contact, qualify, SQL, or close. Direction does not. Waiting is expensive.

How industries differ

Urgency and competition set the real window. High-intent form fills, demo requests, and emergency service demand the tightest SLAs. Longer-cycle B2B still loses when the research session ends and a competitor answers first.

Local and urgent verticals feel the first-responder effect hardest. B2B SaaS has longer sales cycles but still shows multi-x close lifts when first touch moves from days to minutes. Off-hours matter everywhere: a large share of home-service and many web leads arrive outside nine-to-five.

Hormozi’s operating point (and what the numbers support)

Alex Hormozi repeatedly frames speed-to-lead as one of the highest-ROI ops changes available. His common citation matches the Velocify-style finding: contact within sixty seconds of opt-in can produce on the order of a 391 percent lift in conversions; past five minutes, likelihood drops hard (he often cites an ~80 percent drop). He has described home-services operators who assigned a dedicated person whose only job was to stop and call every lead immediately, driving close rates far above industry norms on paid leads. The mechanism is operational, not motivational: someone (or something) must act the moment the lead lands.

A circulating paraphrase that “three minutes yields thirty percent” does not match his primary repeated claims or the underlying studies. Use the sixty-second / five-minute research and treat dedicated coverage as the real constraint.

Build a system that can actually hit the clock

Speed fails in the handoff, not in the slogan. You need lead data in the CRM and in a human or AI queue in seconds, without copy-paste.

Capture. Native CRM web-to-lead (HubSpot, Salesforce, Pipedrive, and peers), reliable form tools with webhooks, live chat, ad lead forms with native connectors, and phone. Prefer direct API or webhook on submit over batch imports.

Pipe instantly. Form submit should create or update the lead with source, page, campaign, and custom fields in under a second. Middleware (Zapier, Make, or custom webhooks) works for moderate volume if you watch failure queues. High volume wants direct integration and dedupe by email or phone. Enrich only if it does not add delay before first touch.

Alert and assign. Round-robin or skills-based assignment in the CRM. Real-time push: SMS, mobile push, Slack, or Teams to the on-call rep. Score high-intent actions (pricing, demo, emergency service) above content downloads. Track SLA timestamps (sixty seconds or five minutes) on a dashboard people actually see. Tie part of comp or review to first-response time if volume justifies it.

Engage immediately. Auto-acknowledge by SMS or email with a booking link so the lead is not staring at a void. Prefer phone for highest-intent leads when a human is available; SMS for open rates and after-hours. Run multi-touch follow-up (most teams quit after one or two attempts). Cover nights and weekends with rotation, outsourced answering, or AI agents. Measure median and p90 response from CRM created-at to first outbound, by channel.

What usually breaks. Manual assignment, wrong owner, reps not watching notifications, email-only alerts, no after-hours path, and forms that email a shared inbox instead of creating a CRM record. Fix those before buying another lead source.

Where ClerkChat fits

If the bottleneck is “someone has to notice and type,” an AI support and sales agent layer removes the idle time. ClerkChat trains agents on your own site, docs, and knowledge, then deploys them on a help page, embeddable widget, and messaging channels teams already use. For speed-to-lead specifically, the useful pieces are instant first response on web and messaging, qualification against your real content, handoff and inbox takeover when a human should take over, and CRM-oriented workflows so the conversation does not live in a silo.

In practice that means a form or chat enquiry can get a grounded answer in seconds, intent can be scored, a hot lead can be routed to calendar or a rep, and context can move with the handoff instead of forcing the prospect to repeat themselves. Voice and messaging coverage matters for off-hours construction, real estate, and services traffic where half the leads never hit business hours. ClerkChat is not a generic ticket chatbot bolted on after the fact; it is built for answers tied to your content plus the channel and takeover paths ops teams need when speed is the SLA.

Use it where human coverage cannot honestly hold a five-minute (or sixty-second) bar twenty-four seven, or where you want the first touch automated and the CRM updated without manual entry. Keep humans on high-value closes and exceptions.

Decision framework

1. Pull last ninety days of web form, chat, and phone leads. Measure median and p90 time to first human or automated meaningful reply. If you cannot measure it, you are slower than you think.
2. Segment by intent. Demo, quote, emergency, and “call me” get a five-minute hard SLA (sixty seconds if volume and margin support dedicated coverage). Content leads can tolerate longer sequenced follow-up.
3. Fix the pipe before the script. Webhook or native CRM create on submit, real-time alert, named owner, after-hours path.
4. Compare your industry row above. If you are a contractor averaging hours while competitors answer in minutes, creative messaging will not save the lead. If you are B2B SaaS at two days, moving to under five minutes is still one of the cheapest conversion lifts available.
5. Choose coverage: dedicated caller for low volume high ticket, on-call rotation plus automation for medium volume, AI-first response with human takeover for twenty-four seven and multi-channel.

Next step: pick one high-intent form, wire it so submit creates the CRM record and fires a mobile alert within a second, and run a two-week test with a five-minute SLA on that path only. Compare connect and qualified rates against the prior baseline. Expand only after the timestamps prove the process holds.