A real estate lead response SLA should define exactly which event starts the clock, which action stops it, when the clock runs, and how missed or unmeasurable responses are reported. Start with an internal service standard, not a promise that every prospect will answer within a fixed number of minutes.
This template helps a team leader audit response timing across a CRM and lead sources. It is a proposed measurement procedure, not a legal agreement, an industry benchmark or a Callion reporting feature. For who takes responsibility, use the lead response plan; this article addresses a different question: can two people calculate the same pass/fail result from the same records?
Define the clock before choosing a target
Google's SRE workbook recommends expressing a service-level indicator as good events divided by total events. That is a software-reliability measurement pattern, not evidence for a real-estate response deadline. Adapt the idea by defining what counts as an on-time inquiry and which inquiries belong in the denominator. Google SRE guidance.
Do not make a missed inquiry disappear because it never acquired a response timestamp. For a completed reporting cohort, count an inquiry whose deadline passed without a qualifying action as a miss. Keep exclusions, unresolved eligibility decisions and missing data visible separately. A rate is not auditable if the team can remove inconvenient records after seeing the result.
Choose the response target after reviewing staffing, customer expectations and the brokerage's separately approved contact rules. No numerical target in the example below is a recommended industry standard.
Copy this measurement specification
Complete these fields before configuring an alert or calculating a percentage. This is an original worksheet, not a vendor configuration export.
| Field | Decision to record | Acceptance check |
|---|---|---|
| Population | Named source, inquiry type and intake period | Reconcile source arrivals with CRM records |
| Counting unit | One distinct inquiry, with a duplicate-delivery rule | A replay does not create a second timer |
| Start | Source receipt time, or another explicitly named event | Do not silently substitute delayed CRM creation |
| Stop | Evidence of the selected response action | Separate attempted contact from a two-way exchange |
| Clock | Elapsed time or a staffed schedule with time zone and holiday rules | Retain both raw timestamps even when the timer pauses |
| Threshold | Chosen interval and whether equality passes | Test a record exactly on the boundary |
| Exclusions | Pre-agreed reasons and a separate count | No exclusion solely because the inquiry missed its deadline |
| Unknowns | Missing timestamps or unresolved classification | Show them; do not quietly score them as passes |
| Reporting cutoff | When the cohort is mature enough to assess | Separate not-yet-due records from overdue ones |
| Ownership | Owner of exceptions, alert channel and review interval | A test exception reaches someone who acknowledges it |
For this template, an automated receipt, an agent's outbound attempt and an actual conversation are three different events. Select one for the standard and name it honestly. A first-attempt standard does not establish successful contact; a conversation standard depends partly on whether the prospect replies.
Keep staffed time separate from elapsed time
Zendesk documents storing first reply time in both calendar hours and business hours. Its business-hour SLA targets pause outside the configured business hours. Those are support-ticket definitions, not universal CRM rules. Zendesk reply-time documentation.
Consider a hypothetical staffed schedule of Monday–Friday, 09:00–17:00 in one specified time zone. An inquiry arrives Friday at 16:58 and the selected action occurs Monday at 09:04. Assume no holiday or clock change during this interval.
- Staffed time: two minutes on Friday plus four on Monday = six minutes.
- Elapsed time: 64 hours and six minutes.
- Against an illustrative ten-staffed-minute target, it passes. Against a ten-elapsed-minute target, it fails.
Neither clock changes what the prospect experienced. Report both when discussing coverage. Do not describe six staffed minutes as six minutes of actual waiting, and do not treat the staffed schedule as legal permission to contact someone.
Do not trust a familiar dashboard label
HubSpot's help-desk SLA settings allow a selected time zone, scheduled hours and pause conditions. Its documentation says those goals apply to help-desk tickets. A brokerage should not assume a similarly named sales-contact field follows those settings. HubSpot SLA documentation.
Ask the implementer to demonstrate the exact start and stop events in your own system. Test an automatic acknowledgement, a manual attempt, a reassignment and a missing source timestamp with synthetic records. Compare the raw event times with the reported result. Do not contact real prospects for a timer test.
Record the rule version used by each report. If you change the schedule or qualifying response action, show the change rather than presenting two differently defined periods as a clean before-and-after improvement.
Calculate a result that includes the misses
Suppose a hypothetical completed cohort contains 100 in-scope inquiries. Under the written rules, 82 have documented on-time actions, ten have documented late actions, five have passed their deadlines without an action, and three lack enough timing evidence to classify. None is excluded.
Report 82 verified passes out of 100 in-scope inquiries: 82% verified on-time, with 15 known misses and three unknowns. Do not report 82 out of 92 by discarding the unanswered and unmeasurable inquiries. The 82% is a conservative verified result, not a claim that the three unknowns were actually late. Resolve their evidence and version any corrected report.
For a zero denominator, show “not applicable.” For records whose deadlines have not arrived, show a provisional cohort instead of declaring them misses early. State the numerator, denominator, unknown count and rule version next to every rate.
Review the missed and unknown records before changing the target. A delayed source feed, an unclaimed task and a missing timestamp need different remedies. Retain an exception owner and a due date for that investigation; do not reset the original clock simply to make the dashboard green.
This procedure measures adherence to a chosen response standard. It does not prove conversion lift or replace the separate rules governing outreach. For outcome denominators, use the lead conversion measurement guide. Browse the speed-to-lead hub for the surrounding operating process.