Speed to lead measures the time between an enquiry arriving and the team responding. For property management, the useful version measures a reply that addresses the enquiry or begins an appropriate next step. An instant acknowledgement and a useful answer should not be treated as the same event.
There is no single response-time target that proves a property will lease faster. Establish your own baseline, identify the delays you can control and check whether shorter waits also produce accurate answers and completed actions.
Write the metric definition first
Choose the starting event: receipt by the listing source, delivery to your inbox or creation in the CRM. These timestamps can differ. If you start the clock only after a slow import finishes, the dashboard hides the prospect's actual wait.
Choose the stopping event: a meaningful answer, a relevant clarifying question or an appropriate handoff response. Track acknowledgements separately. Document how you handle duplicate enquiries, spam and test messages before comparing results.
Keep unanswered enquiries visible
A report built only from answered conversations can look excellent while a queue of unanswered messages grows. Report the count and age of enquiries still awaiting a useful reply alongside the response-time statistics. State the observation cutoff so another person can reproduce the report.
Illustrative calculation: five completed first replies took 2, 4, 7, 18 and 90 minutes. The median is 7 minutes and the average is 24.2 minutes. Neither statistic shows a sixth enquiry that remains unanswered. Keep that outstanding item in the report as its own status instead of quietly excluding it from the story.
Break the numbers down by operational cause
- Channel and source: identify delayed imports, missed calls or messages routed to an unattended inbox.
- Property: reveal different coverage arrangements or ownership rules.
- Time period: separate staffed hours, evenings, weekends and holidays using the property's time zone.
- Enquiry type: distinguish straightforward information requests from cases that need a specialist response.
- Outcome: check whether the useful reply led to a completed next step or an unresolved task.
A slower response on a sensitive question may reflect appropriate review. Investigate the reason before rewarding a faster answer that bypasses the person who should handle it.
Fix the handoff between systems
Trace one delayed enquiry end to end. Did it wait at the source, in an integration, in an unassigned queue or with an unavailable team member? The fix may be a routing rule, a named owner or coverage during a specific period rather than a new tool.
If an assistant handles the first response, measure the wait for subsequent human help too. Moving the delay from the inbox to a callback queue does not solve the customer's problem. Record whether the promised follow-up was completed and how long it took.
Review speed with quality
Sample replies against the information available at the time. Look for invented availability, unnecessary questions, premature confirmations and missed requests for a person. Pair the speed report with these findings so the team can distinguish genuinely useful improvement from faster message production.
Use the baseline and a defined review period to evaluate a change. Record simultaneous changes in staffing, advertising or property availability. This gives you a defensible operational comparison without pretending response time alone determines leasing results.