Real Estate Luxury

Powered by StealthAgents

Luxury buyer operations |

Measuring response time for high-value buyer enquiries

A measurement protocol for high-value buyer enquiries that separates first acknowledgement, substantive reply, and the delay the buyer actually experiences.

Measuring response time for high-value buyer enquiries
Primary metric
median time from buyer enquiry to substantive human reply
Sources reviewed
10
Published observations
5

Key Takeaways

  • Measure from the buyer send time, not the internal assignment time.
  • Separate acknowledgement from a substantive reply.
  • Exclude automated receipts from the human response measure.
  • Report the median and the slow tail by enquiry source.
Table of contents

A high-value buyer often judges a team by the first reply. That reply may be fast, slow, or absent, and each case tells a different story. This review sets out a measure that follows the buyer clock rather than the internal workflow. The aim is a fair number that a team can act on.

Research question and scope

This review asks how long a high-value buyer waits for a substantive human reply after sending an enquiry. The unit is one inbound enquiry that reaches the estate or agency through a monitored channel. The review measures the buyer experience, not the internal effort behind the reply. A narrow question makes the result easier to compare across teams.

The scope covers enquiries about a specific luxury property or a private search, received by email, web form, or messaging channel. It excludes general newsletter replies, vendor messages, and internal referrals. It also excludes enquiries that arrive outside the business hours stated on the website, which are measured under a separate after-hours rule. The scope should be written before the sample is drawn.

The review separates a first acknowledgement from a substantive reply. An automated receipt confirms delivery but does not answer the buyer. A substantive reply names the property, answers a question, or offers a next step. Both measures are useful, but only the second reflects the work the buyer is waiting for.

Record the enquiry source because different channels may have different response patterns. A web form may route to a shared inbox, while a messaging channel may reach an agent directly. The source is a grouping variable, not an excuse. The reader should be able to see whether one channel is consistently slower.

Definitions and unit of analysis

Define the start time as the moment the buyer sent the message in the channel time stamp. Do not use the time the lead was assigned or the time the agent opened the email. Those internal times can make a slow response look fast. Use the buyer time stamp even when it is inconvenient.

Define the first acknowledgement as any human response that confirms receipt and names a next step. An automated auto-reply does not count. Define the substantive reply as a response that addresses the buyer question or provides a specific property next step. A reply that only says someone will be in touch is an acknowledgement, not a substantive answer.

The unit is the enquiry thread, not each message. A thread that receives three replies is one buyer experience. Stop the clock at the first substantive reply, even if the conversation continues. Record later replies for context but do not add them to the main measure.

Decide before collection how to treat a reply that asks the buyer for more information. If the reply is specific and moves the conversation forward, it counts as substantive. If it is a generic request with no next step, it counts as an acknowledgement. Test the rule on a few examples and write the decision into the data dictionary.

Sampling and data dictionary

Draw the sample from the enquiry records for a fixed period, such as one quarter. Include every enquiry that meets the scope, or a random sample if volume is high. Record the export date, the filters, and the row count. Keep the raw export with the report so the sample can be rebuilt.

For each enquiry, capture the channel, the send time, the first human reply time, the substantive reply time, and the agent or team. Add the property and the buyer segment without storing unnecessary personal data. A short buyer reference is enough for matching. The report should never expose a buyer name or contact detail.

Use the channel time stamp rather than a manually entered time when possible. A manual field is easy to round or backfill. If the system does not preserve the original time, record the limitation and avoid claiming precision. A rough measure with a stated limit is better than a precise number built on guesses.

Include enquiries that received no reply and record them with an open end time at the observation date. Excluding unanswered enquiries would make the team look faster than the buyer experience. Report the unanswered share separately and include it in the tail analysis. A response measure that ignores silence is not a buyer measure.

Measuring delay and responsiveness

Report the median time to acknowledgement and the median time to substantive reply. Also report the slowest decile, because a small group of buyers waits far longer than the median. A luxury buyer may remember one slow reply more than ten fast ones. The tail is part of the service quality, not a statistical detail.

Break the result down by channel, property, and agent team. A shared inbox may create a queue that a direct channel avoids. A single property with a complex approval process may be slower for a good reason. The breakdown should lead to a specific question, not a general instruction to respond faster.

Report the share of enquiries that received a substantive reply within the business-hours promise. A promise should be stated in the same unit as the measure, such as four business hours. If the team has no promise, use the median as a baseline and label it as provisional. A target without a baseline is a guess.

Check whether the reply time changes when the enquiry arrives during a launch or a private preview. A high-value period may produce a longer queue and a different experience. Report the period and compare like with like. A busy week is context, not a reason to hide the delay.

Analysis and limitations

The records cannot show whether a buyer was satisfied with the reply. A fast reply that misses the question may be worse than a slower one that answers it. Pair the timing measure with a small quality review of the reply content. The two measures together give a more honest picture than speed alone.

A buyer may send the same enquiry through several channels, and one thread may be split across them. The sample should de-duplicate by buyer and property where the records allow. Record the de-duplication rule and the number of removed duplicates. A double count can make a channel look busier and slower than it is.

The review cannot control for the complexity of the enquiry. A request for a private viewing may need more work than a request for a brochure. Record a simple complexity label and compare within it. A fair comparison is more useful than a single average that mixes very different requests.

Give the finding to the team with one testable change, such as a named owner for each channel and a first-reply checklist. Record the change date and repeat the measurement with the same definitions. A second sample shows whether the change reached the buyer. It also protects the team from judging a new process on its first busy week.

Repeating the review

Repeat the observation in the same season and at a similar point in the launch calendar. A new development launch can change the enquiry mix and the response pattern. Note any campaign or event that could affect the sample. A like-for-like comparison is the only fair test of a change.

Keep the channel definitions and the business-hours rule in the appendix. A change in the hours or the routing can move the result without any change in effort. Report the rule beside the number. The reader should be able to see whether the team is comparing the same service window.

Agree on the next review date and the owner of the data export before the meeting ends. A measure that depends on one person is fragile. Write the export steps into the operations note and check them at the next review. The method should survive a staff change.

Use the result to protect the first hour after an enquiry, not to add another dashboard. A named owner, a clear next step, and a short checklist are often enough. Ask the agents which part of the reply takes the most time. Fix that step before asking for a faster overall response.

Data sources and references

Keep exploring