Someone asks in a portfolio meeting how fast the team responds to inquiries.

The answer comes back confidently. Under an hour, on average, across the portfolio.

Now ask the follow-up question. Where did that number come from? Which system produced it, what counted as a response, and what happened to the inquiries nobody ever answered?

In most operations, nobody in the room can answer that. The number exists because a dashboard produces it, and the dashboard is measuring something rather less impressive than everyone assumes.

The problem is not that teams are slow

The industry has spent years telling property managers to respond faster. The advice landed. Many leasing teams now know the five-minute research and have automated acknowledgements running, but that does not mean the response-time number they report is measuring what they think it is.

This matters more than it sounds, because a wrong response-time number does not just misinform you. It actively protects the problem. A metric that reports success removes the pressure to investigate, so the inquiries falling through keep falling through, quietly, with a green dashboard sitting on top of them.

Here are the five ways the number goes wrong. Most operations have at least three.

1. The clock stops on the auto-acknowledgement

The most common error by a distance.

An inquiry arrives. Nine seconds later an automated email confirms receipt. Your system records a nine-second response time, which is true, and completely disconnected from whether anyone helped the prospect.

Automated acknowledgements are worth having. They set expectations and they buy time. But they are not responses, and counting them as responses means your headline metric can improve permanently without a single additional lead being worked.

The fix: measure first human response as a separate number. Keep the acknowledgement metric if it is useful for checking the automation is running, but never let it be the figure you report.

2. Phone inquiries are missing entirely

Many response-time dashboards focus on written channels, because written inquiries naturally carry timestamps while phone activity is usually tracked somewhere else, if at all.

A call that rings out at 5:40pm may never appear in the same calculation as a portal message. It becomes a missed-call problem rather than a response-time problem, which means your portfolio metric can look healthy while an entire channel sits unmeasured.

That is not a small omission. For many operations the phone is where the highest-intent prospects go, because someone who dials is ready to talk now rather than later.

The fix: at minimum, track call answer rate and missed-call volume alongside written response time. They are different metrics and both belong on the page.

3. The mean hides everything that matters

Fifty inquiries. Forty-nine answered within four minutes. One arrives Friday evening and gets picked up Monday at 10am, forty hours later.

Your average is forty-seven minutes. Nobody experienced forty-seven minutes. Forty-nine people had an excellent experience and one person had a terrible one, and the average describes neither.

Worse, the average moves in ways that feel meaningful and are not. Add ten more fast responses and the average falls, which reads as improvement when nothing about the weekend gap has changed.

The fix: report the median, plus a count of how many inquiries exceeded your target. The median tells you the typical experience. The slow-tail count tells you how many people had the bad one. Together they cannot be gamed by volume.

4. The inquiries nobody answered are excluded from the calculation

This is the one that should worry you most, and it is structural rather than deliberate.

To calculate an average response time you need a response. An inquiry that never received one has no elapsed time, so if unanswered inquiries are excluded from the calculation, the worst outcome available to you never enters the denominator at all.

Follow that through and you get something genuinely perverse. A prospect who contacted you and never heard back cannot make your reported response time worse. In a calculation built that way, the reported number improves while the customer experience does not.

Research outside property management suggests this group is not small. A widely cited audit of 2,241 companies found 23% never responded to an inquiry at all.

The fix: report a no-response rate as a standing metric beside response time. Inquiries received, inquiries that got a human reply, and the gap between them. If that gap is not zero, it is the most important number on the page and no response-time average should be discussed without it.

5. Every channel is timed by a different system

Portal messages are timestamped by the portal. Website form submissions by your website tool. Texts by whichever phone they arrived on. Emails by the mail server.

Each of those clocks starts at a different moment and measures a slightly different event. Some start when the prospect submits, some when the message syncs to your system, and syncing is not instant.

So a portfolio-level average is frequently an average of numbers that are not measuring the same thing. Combining them produces a figure with a decimal point and no meaning.

The fix: report by channel until the underlying timestamps genuinely come from one place. Four honest channel numbers beat one dishonest portfolio number.

While we are correcting things: the 21x figure is not a leasing benchmark

You will see it everywhere in property management content. Respond within five minutes and you are 21 times more likely to qualify a lead. At least one property management source attributes that figure to the National Apartment Association.

It is not theirs. It comes from the 2007 Lead Response Management study, run across more than 15,000 leads and 100,000 call attempts in a cross-industry sales context. It measured outbound call attempts and qualification, not closing rates, and not replies across email, portal messaging and text.

The direction transfers well. Intent decays fast and the decay is steepest at the start. But it is not a property management benchmark, it was not measured on renters, and quoting it as though the NAA established it for multifamily will be noticed by exactly the reader you want to impress.

What to measure instead

Six numbers, produced the same way every month.

That last one deserves a note. Sending is easy to measure. A two-way contact tells you something more useful, which is whether the prospect was actually reached. A team can post excellent response times alongside a poor contact rate, and only the two numbers together tell you whether you have a speed problem or a reachability problem.

The variance is the finding

Here is the part that changes how you read all of this.

Velocify ran a secret shopper study of lead response at top multifamily companies, covering 10 of the 50 largest multifamily property owners in the United States. It found that 60% of the companies studied failed to attempt telephone contact with a new lead within 24 hours of submission, and that the average number of contact attempts was 2.5, against what their research suggested should be closer to six.

But the finding they flagged as most significant was different. It was the lack of consistency between different properties owned by the same company. Same ownership, same tools, same stated policy, different behavior.

Two caveats worth stating plainly. The study is from 2014, so treat the percentages as dated. And ten companies is a small base, so read the numbers as indicative rather than definitive.

The structural point has not aged, and anyone who has managed a portfolio will recognize it instantly. Your portfolio average is hiding a distribution, and the distribution is where the decisions live. One asset at eight minutes and another at nine hours is not a market problem. It is usually one person, one habit, or one channel nobody is watching, and you cannot find it inside a single blended number.

So report by property, not just by portfolio. Then ask what the best site is doing that the worst one is not. That conversation becomes available the moment the numbers are separated, and not before.

Why most teams cannot produce any of this

Zillow ran a research program on multifamily lead conversion, and their product manager summarized what operators kept telling her: on-site teams get plenty of leads but have no data on which practices actually convert them, so they are operating blind a lot of the time.

That is a listing portal describing its own customers, not a software vendor describing a prospect. Worth taking seriously.

The reason is not effort. Every metric above requires two things most operations do not have. A single record of every inquiry regardless of which channel it arrived through. And a recorded event marking the first human response against that inquiry.

Without the first, you cannot calculate a no-response rate, because you do not have a complete denominator. Without the second, you cannot separate the acknowledgement from the reply.

Both are capture requirements, not reporting requirements. No spreadsheet fixes them afterwards, because the information was never written down at the moment it existed. That is also why the annual attempt to produce these figures by hand takes a week and then never happens again.

Where to start this month

• Stop reporting the average. Switch to median plus slow-tail count. Costs nothing, and it is the single change that makes the number honest.

• Add the no-response rate. Even a rough manual count, for one property, for one month. If it comes back above zero, you have found something more valuable than any speed improvement available to you.

• Separate the acknowledgement from the reply. If your current system cannot, record that as a finding rather than working around it.

• Split the portfolio number by property. Then look at the spread rather than the middle.

• Leave the target alone until the measurement is honest. Setting a five-minute goal on top of a number that excludes unanswered leads optimizes the wrong thing, and it will produce faster acknowledgements rather than faster answers.

Common mistakes

• Improving the metric instead of the process. Adding a faster auto-reply improves the number and changes nothing for any prospect. If a change improves your reported response time without changing what a renter experiences, it was not an improvement.

• Reporting a portfolio average to owners. It invites comparison against a benchmark measured differently, and it hides the property-level variance that would actually explain performance.

• Treating speed as the whole problem. A fast reply through the wrong channel, or with nothing useful in it, still loses the lead. Our article on why a four-minute reply can still lose the lease covers what else has to be true.

• Measuring the first reply and ignoring what follows. A fast first touch followed by silence is common and invisible, and it usually lives in the handoff between an automated message and a human.

Go back to that portfolio meeting. The answer was under an hour, on average, and everyone moved on.

The honest version has four parts. Our median first human response is X. Y inquiries went past our target last month. Z received no human reply at all. And here is the figure for each property, because the spread between them is wider than any of us would like.

That answer is harder to give, and it starts a conversation worth having. The reason most operations cannot give it has nothing to do with how hard the leasing team works. It is that inquiries arrive into several places at once, and nothing records them as one set of events you can count.

That is the part RIOO is built to address. Leasing management brings inquiries from multiple sources into one structured leasing workflow, and dashboards and reports draw on that same centralized data, so the numbers can come from one place rather than being assembled across systems that each measure a slightly different moment.

Try the no-response count for one property this month. If it comes back above zero, it is worth seeing what the full picture would look like.

Frequently asked questions

Q1. How should I measure lead response time in property management?
Median time to first human response, split by channel, reported alongside a count of inquiries that exceeded your target and a no-response rate. Averages and auto-acknowledgement timestamps will both flatter you.

Q2. Does an automated acknowledgement count as a response?
Not for measurement purposes. It confirms receipt and buys time, which is useful, but counting it as your response time means the metric can improve indefinitely without any prospect being helped. Track it separately.

Q3. Why is my response time good but my conversion poor?
Common causes are an acknowledgement being counted as the response, phone inquiries being excluded from the calculation, unanswered leads dropping out of the average, or fast first replies that nobody follows up.

Q4. Is the five-minute rule a property management benchmark?
No. The widely quoted figures come from cross-industry sales research measuring outbound call attempts and qualification. The direction applies to leasing, but the specific multiples were not measured on renters and should not be presented as a multifamily standard.

Q5. Should I report response time to owners?
Yes, but by property rather than as a portfolio average, and alongside the count of inquiries received. A speed number with no volume attached invites comparison to benchmarks that were measured differently.