The Quote Request That Waited Two Hours

Four providers got the same email

A shipper needs a reefer load out of Atlanta covered by Thursday. At 9:12 she fills out your quote form. Then she does what standard industry guidance tells every shipper to do with a spot RFQ: she sends the identical request to three or four other providers at the same time. Four inboxes. One load.

Your quote went out at 11:05. Nobody was lazy about it. The form dumps into a shared inbox, the one person who prices reefer out of Georgia was on a rate call until 10:40, and somebody had to notice the request before anyone could price it. Honestly, two hours is a respectable showing for that setup. Plenty of company sites promise exactly that on the homepage: "a quote within two hours," presented as a selling point.

The trouble is everything that happened between 9:12 and 11:05. One of the other four acknowledged the request in under a minute, priced it, and called to talk it through. By the time your number landed, the shortlist already existed and you weren't on it. The first usable quote back tends to frame the whole decision. It sets the anchor price, and it starts a conversation every later quote has to interrupt.

What the speed-to-lead statistics actually show

The research on quote response time has a strange shape: the canonical study is nearly two decades old and nobody has dethroned it. Back in 2007, a Lead Response Management study run with MIT-affiliated researchers found sales teams were about 21 times as likely to qualify a lead when they called within five minutes versus half an hour. The odds of even making contact fell roughly a hundredfold as the minutes passed. Old data. Still the reference point.

Harvard Business Review ran its own audit in 2011 across 2,241 US companies. Average response to a web lead: 42 hours. Twenty-three percent never responded at all, and only 37 percent answered within the hour. Firms that got back inside an hour qualified leads about seven times as often as the ones an hour behind them.

Freight specifically? Be suspicious of anyone quoting a tidy "the first responder wins X percent of spot quotes" number, because no rigorous published study has measured that. What does exist: when Freightos mystery-shopped top global forwarders in 2016 and 2017, they averaged around 90 hours to answer an online quote request, and a majority of requests never got a quote at all. Domestic spot freight moves much quicker than that world, obviously. But the arithmetic carries the point without a study. Four recipients, one winner, and response order is the only tiebreaker that costs you nothing to control.

The HVAC version of the same morning

Swap the reefer load for a dead AC unit in July and the mechanics are identical. Hatch analyzed 132,188 HVAC speed-to-lead campaigns in 2024 and found only 12 percent of contractors respond to a new lead within five minutes. The single most common response time, covering 37 percent of contractors, was a full day. A day. For a homeowner sitting in a hot house who filled out three other contact forms while she waited.

Phones aren't the safety net people assume, either. Invoca's call benchmarks report, built on tens of millions of home-services calls, found only about half of callers ever reach a live person. A 411 Locals study that dialed businesses across dozens of industries got a live answer under 40 percent of the time. And industry data consistently puts inbound home-service calls arriving outside business hours at around a third, which is precisely when nobody owns the inbox.

So the competitor whose site quotes instantly isn't necessarily smarter or better staffed. They just decided response time was a system problem instead of an effort problem, and built accordingly.

Where your quote response time actually goes

Run the uncomfortable audit. A quote request can reach you at least four ways, and each channel has a different owner, a different notification, and a different failure mode. Which means response time comes down to staffing luck: who happens to be at a desk, whose phone buzzes, who last checked the shared inbox. We wrote about the capture half of this separately, the mess of every lead living in a different inbox. This is what it does to the clock.

How it arrives	Who sees it	What acknowledges it	After hours
Web form	Whoever checks the shared inbox	Nothing, or a generic autoresponder	Waits until morning
Phone call	Whoever is near a desk	A human, if the call gets answered	Voicemail
Email	The person it was addressed to, eventually	Nothing	Waits, sometimes days
Text	One person's cell phone	That one person, if they're on shift	Depends entirely on them

No single row here is broken. Together, though, they guarantee that some requests wait, and you never get to pick which ones. The reefer RFQ waits because it hit the form on the morning your dispatcher was out. The system-replacement lead waits because it came in by text to a tech on a roof.

One queue, instant acknowledgment, routed to whoever can price it

Nobody expects a full reefer rate or a system-replacement price in ninety seconds. What the requester wants in the first minute is different: proof a human is on it, and an honest timeframe for the real number. That message holds your place in line while pricing happens at whatever speed pricing genuinely takes.

An acknowledgment isn't a quote, and nobody expects it to be. It just tells the requester which of the four open tabs to keep open.

The structure that gets you there:

1. One queue for every channel. Form, phone, email, and text all land in the same place, timestamped, visible to more than one person.
2. Instant acknowledgment with a real timeframe. Not "we value your business." Something like "Got it, you'll have a number from us by end of day," sent the moment the request arrives.
3. A routing rule to whoever can price it. The reefer request goes to the person who prices reefer, not to whoever opened the inbox first.
4. An after-hours answer other than voicemail. An answering service, an on-call rotation, or at minimum an auto-reply naming when a human will call back.

Getting the quote out is half the job. The follow-up call afterward is its own discipline, and it's the step most operators quietly skip; we covered why following up feels harder than it should and how to schedule it instead of moodwalking it. A unified queue also produces something you've probably never had: an honest record of your own response times per channel. Most operators guess wrong about theirs, usually in the flattering direction. Mapping that reality is the first thing we do in our process, before anything gets built.

What speed won't rescue

Fair warning about the research: some of that qualification gap is probably selection effect. Companies answering in five minutes tend to be the ones with their act together generally, and the studies can't fully untangle cause from correlation. The practical takeaway survives anyway, because response order is cheap to control and the downside of controlling it is zero.

Speed gets you into the conversation. Winning it still takes a real price, a real plan, and a customer worth winning. If half your inbound requests are tire-kickers, answering them in thirty seconds just means wasting time on quotes that never close at a brisker pace. And rushing complex work out the door with a sloppy number creates its own bill later; that one shows up as free quote revisions that cost more than lost bids.

The two-hour promise on your site was written for a world where the request came to you alone. It didn't. It went to four providers, and one of them answered before your team knew it existed.