Ask a marketing lead how long it takes their company to reply to a new inquiry and you will get an estimate. Ask them to prove it and the conversation changes. Almost nobody measures this. It is the only number in the entire funnel that is both easy to move and nearly free to fix, and it is sitting unmeasured in most businesses.
This is about that first hour. What it costs, why every company underestimates it, and how to close the gap inside two weeks without buying software.
The estimate is always wrong in the same direction
When people estimate their own response time, they think of a good day. They picture the inquiry that came in at ten on a Tuesday when someone was at their desk. That one was answered in nine minutes and it is the one that comes to mind.
The average is not made of Tuesday mornings. It is made of Friday at five, Saturday, the week someone was on leave, the fortnight when the person who normally watches the inbox was covering something else. Those inquiries do not get answered in nine minutes. Some of them do not get answered at all, and because nobody counted them arriving, nobody notices them not being answered.
Here is the test. Take your last forty inquiries. Not a sample you choose, the last forty in order. For each one write down the timestamp it arrived and the timestamp of the first human reply. Then sort by the gap.
Two things will happen. The median will be worse than the estimate, usually by a multiple rather than a margin. And there will be a tail: a handful with no second timestamp at all. That tail is the part worth caring about, because those are not slow responses. They are inquiries that arrived, were paid for, and were never answered by anyone.
Why it decays so fast
A buyer who sends an inquiry has just done the hardest thing they will do in the whole process. They have admitted, to themselves and to a stranger, that they have a problem they cannot solve internally. That admission has a short shelf life.
In the hours after they send it, one of three things happens. You reply and the conversation starts while the problem still feels urgent. Or you do not reply, the urgency fades, and they get on with their week, which is the most common outcome and the one that looks like nothing at all in your data. Or you do not reply and somebody else does, in which case you have paid to generate a lead for a competitor.
The third case gets all the attention because it stings. The second one costs more, because it happens far more often and leaves no trace. There is no lost-to-competitor note in the CRM. There is just a thread that stops.
Putting a number on it
You do not need industry benchmarks for this. You need your own numbers, and you already have them.
Take the forty inquiries from the test. Split them into two groups: those answered within an hour, and those that took longer. Now look at how many in each group reached a real conversation, meaning a call, a meeting, or a substantive back-and-forth.
In most businesses that run this the gap is not subtle. If it is not, that is genuinely useful information: your buyers are not time-sensitive, response time is not your leak, and you should stop reading this and go look at qualification instead.
If it is, the arithmetic is simple. Take the difference in conversion rate between the two groups. Apply it to the number of slow-answered inquiries you get in a year. Multiply by your average deal value. That is what the first hour is costing you annually, and it is almost always a larger number than whatever you were about to spend on more traffic.
The four reasons it is slow
Every slow response traces back to one of four causes, and they need different fixes.
Nobody owns it. The inquiry lands in a shared inbox that three people can see and none of them is responsible for. Shared responsibility is no responsibility. This is the most common cause and the easiest to fix.
It lands somewhere nobody watches. A form that emails an address created in 2019. A social channel someone set up and forgot. A phone number on a page nobody has opened in a year. These produce the tail of unanswered inquiries, and you find them by auditing routes rather than by watching the inbox.
The person who could answer is not the person who saw it. The inquiry arrives, someone reads it, decides they cannot answer properly, and waits for whoever can. The wait is the leak. The buyer does not know a good answer is coming, only that no answer has come.
Answering well takes too long. Every reply is written from scratch, so replying properly costs twenty minutes of focused work, so it waits for a gap that never arrives. This one masquerades as a quality problem and is actually a preparation problem.
The two-week fix
None of this needs new software. Most companies that fix response time do it with what they already have.
Days one and two: find every route in. List every way an inquiry can physically reach you. Website form, email addresses, each social channel, phone, WhatsApp, the contact detail on the invoice template, the address on a two-year-old brochure still circulating. Send a test inquiry down every single one. Some will not arrive. Those are your tail.
Day three: give each route one owner by name. Not a team. A person, with a named backup for when they are away. Write it down somewhere both of them can see it. If a route cannot be given an owner, close the route.
Days four and five: write the first reply once. Look at the last twenty inquiries and count how many distinct things people actually asked. It is rarely more than five. Write a good reply to each. Not a template that reads like a template: a real answer to the real question, ending with a specific next step and two times to take it. Now replying well takes ninety seconds instead of twenty minutes, and the quality problem disappears with the speed problem.
Week two: set the standard and measure against it. Pick a number. One hour during working hours is a reasonable place to start. Then measure it weekly, in public, as one line: inquiries received, median time to first reply, number that waited more than a day. Three numbers. If it takes more than five minutes a week to produce, simplify it until it does.
What to put in the reply
The preparation step is the one people skip, so it is worth being specific about what a good first reply contains. Three things, in this order.
The answer to what they actually asked. Not an acknowledgement that they asked. Buyers can tell the difference between a reply that engages with their question and one that confirms receipt of it, and the second reads as a delay wearing a politeness costume.
One question that moves it forward. Something that either qualifies or clarifies, and that they can answer in a sentence. Asking six questions in a first reply reads as a form. Asking none leaves them to work out the next move themselves, which they will not.
A specific next step with two times attached. Not "let me know if you would like to discuss further". Two concrete slots. The reply-to-scheduling gap is where a startling number of interested buyers quietly fall out.
Write five of these. Keep them in a document everyone answering inquiries can reach. The point is not to automate the reply, it is to remove the twenty minutes of blank-page work that makes replying feel expensive.
Why it usually does not stick
Most companies have fixed this before. Response time improved for six weeks and then drifted back. That is worth understanding, because the drift is predictable.
It happens when the fix lives in someone's intentions rather than in the system. If being fast depends on a person remembering to be fast, it survives exactly as long as that person's attention does, which is until the first genuinely busy week.
Two things make it survive. The first is that the owner is named, in writing, with a named backup, so that being away is planned for rather than discovered. The second is that the number is reported weekly to someone other than the person responsible for it. Not as a performance measure and not to anyone's manager. Just visible, every week, in the same place.
Anything measured weekly and seen by two people holds. Anything measured occasionally and seen by one person does not. That is most of what there is to know about making operational fixes permanent.
The cost of getting this wrong in the other direction
There is a failure mode worth naming. Some companies read this, set a one-hour standard, and start sending fast, empty replies to protect the number.
That is worse than being slow. A quick reply that says nothing spends the buyer's attention without giving them anything, and the second reply now arrives to someone who has already been disappointed once. If you have to choose, a considered reply in four hours beats an empty one in four minutes.
You should not have to choose. That is what the prepared replies are for.
How to know it worked
The median will move first, within a fortnight, because the owner change alone does most of that work. The tail takes longer, because it is a routing problem rather than a behaviour problem, and you only find those inquiries by testing the routes.
The number that matters is neither of those. It is the share of inquiries that reach a real conversation. Watch it for a quarter. If response time was your leak, that number moves without anyone touching the ads, the website or the content calendar.
If it does not move, you have learned something worth more than the fortnight it cost: your leak is somewhere else, and you now have clean data on the one place it definitely is not.
The part that is uncomfortable
Response time is unglamorous. There is no campaign in it, no launch, nothing to show a board that looks like marketing. It is an operations fix wearing a marketing budget, and it is boring in exactly the way that things which work are often boring.
That is also why it is still available. Every competitor you have is looking at the same channels and the same tactics you are. Almost none of them know their median response time, and the ones that do have usually already taken the business you thought you lost on price.