Capture Before Handoff: Stop Losing the Demand You Already Earned

A study of 2,241 companies and more than 100,000 leads found that the cost of a late reply isn't the late reply. It's the silence that comes first.

The enquiry that waits for a human

A booking enquiry lands while you're mid-job or the whole team is heads-down. Nobody is ignoring it. There is just no one free right now, so it sits in the inbox, the booking form, the missed-call log, or the support queue until someone surfaces.

By then the customer has gone quiet or booked elsewhere. That gap has a name, and naming it changes what you do about it.

Demand leaks across whichever channels you run

Call this the first-response gap: the stretch between an enquiry arriving and a person actually working it. Every channel you run has one. Calls hit voicemail, the contact form sits, the DM goes unread, the support ticket waits its turn.

The leak isn't loud. It's quiet, and it spreads across all of them at once, which is exactly what you can check on your own inbound before you assume it's small.

Why "I can't answer it all" turns into "I do nothing"

Here's the trap. You assume a fix has to fully resolve the request to count, decide you can't possibly answer every enquiry the second it arrives, and so you capture nothing. The held belief is the leak, not the busy team.

The cost lives in the silence before the answer, and the numbers are blunt about how fast that silence does damage. In the largest study of its kind, Oldroyd, McElheran, and Elkington (Harvard Business Review, 2011) tracked 2,241 US companies and over 100,000 leads.

A lead contacted within five minutes is 21 times more likely to qualify than one contacted after thirty. — Oldroyd, McElheran & Elkington, Harvard Business Review, 2011

That same lead is roughly 100 times more likely to be reached at all. Yet only about 7% of companies respond inside five minutes, and the average first response runs near 42 hours. On the phones it's worse: when a caller hits voicemail, about 80% hang up without leaving a message (Hiya State of the Call), and most just dial the next business on their list. Demand does not wait. It moves to whoever responds first.

Capture before handoff: what a good-enough holding response does

None of that requires the human to be instant. It requires the demand not to leak before the human arrives. A holding response does four jobs without resolving anything: it acknowledges who and what, qualifies urgency and fit, routes to the right person, and sets a next step the customer can count on.

That's the reframe. Stop measuring a first-response fix by whether it resolves the request. Measure it by whether it keeps the demand from leaking. AI is one practical way to run those four jobs while the team is unavailable, but the job comes first and the tool is just how you do it.

There's a deeper read here, and it's the part most operators miss. Your first-response gap reveals how the business actually grew. It scaled on people being available, and demand quietly started leaking the moment availability ran out. That isn't a team failure. It's the seam every growing operation hits, and it's a far smaller fix than answering everything instantly. Find the one channel and the one thing worth capturing before a human takes over, and you've already plugged the most expensive leak in the building: the demand you paid to earn.