While they are still holding the phone. The honest target is seconds, not hours, because attention is what you actually bought.
Published January 19, 2026
The useful way to think about this is not as a benchmark to hit. It is a question about attention, and attention has a shape you can reason about without needing a study to tell you.
Somebody who has just submitted a form is, at that exact moment, thinking about your property. Ten minutes later they are thinking about something else, and probably about two other listings they messaged at the same time. The window you paid for closes on its own, whether or not anybody reaches it.
Most guidance lands on a figure like five minutes or an hour, and the figure is less important than the direction. Nobody has ever lost a lease because they replied too quickly.
What makes seconds the right target rather than minutes is that the person is usually still in the same session. They are still on the page, still holding the phone, still comparing. A reply that arrives inside that session continues a conversation. A reply that arrives an hour later starts a new one, and has to re-earn the attention first.
Every operator we talk to already knows speed matters. The gap is not awareness, it is arithmetic.
A front desk runs on a human schedule and inquiries do not. That mismatch is structural, and no amount of reminding people to be faster resolves it.
A fast, useless reply is not worth much. An automated acknowledgement saying somebody will be in touch shortly buys you almost nothing, because it does not advance the thing the person wanted.
The reply that works answers the actual question. Is it still available, what does it rent for, can I see it Saturday. If the first response can answer those from your live records and offer a real time, the speed compounds into a booking rather than just a faster holding message.
You do not need a vendor for this, and doing it yourself is more persuasive than anything you will read.
The pattern is usually not a uniform delay. It is a small number of fast replies during staffed hours and a long tail of inquiries that arrived at inconvenient times and were never really worked.
If your gap is concentrated outside office hours, that is a coverage problem and automation addresses it directly. If your gap is during staffed hours, the problem is volume or routing, and adding speed without fixing the routing just gets you to the same bottleneck faster.
Either way, the number you produced is yours and it is real, which makes it a far better basis for a decision than an industry figure from a vendor's slide.
Worth defining before you measure, because the definition decides whether the number means anything.
An automatic acknowledgement is not a reply. A voicemail greeting is not a reply. A message saying somebody will be in touch shortly is, at best, a promise. The thing worth timing is the first response that moves the person forward: an answer to what they asked, or a real time they can take.
Measured that way, the number is usually worse than people expect, and the gap between the two definitions is where prospects are lost.
One refinement worth adding to the exercise: the expectation is not the same everywhere, and averaging across channels hides that.
A slow email channel is a smaller problem than a slow chat widget on your own website.
On the site
Keep reading