Use timestamps that describe different events
Keep original capture, buyer acceptance, CRM receipt, assignment and first contact attempt as separate timestamps. Each interval answers a different operational question. If a record spends twenty minutes waiting to reach the CRM, a rep’s quick response after assignment does not explain the whole delay.
Define what counts as a contact attempt. An internal notification to a sales manager is not a call to the homeowner. A scheduled task that has not run is not a completed attempt. Use the actual event from the approved calling or messaging workflow, and keep a two-way conversation as a later stage.
Give every queue an owner and a backup
Assign a team to each accepted trade and territory. Name the backup when a rep is unavailable or a branch is closed. If ownership changes, preserve the original assignment time and the reassignment event so a delay does not disappear from the report.
Open the queue as a normal user and verify that new inquiries are visible with project context. A phone number without the requested work or service location can force the rep to repeat qualification the source already completed. Fix missing fields before asking the team to improve speed.
Decide what happens outside staffed hours
Align intake hours with your team’s approved contact practices and available coverage. A company can choose to pause delivery, route to another staffed team or accept a clearly labeled after-hours queue. The source and receiving system need the same decision, timezone and holiday exceptions.
Show after-hours delay in reporting rather than hiding it inside an average. If you also report staffed-hours response, label the measure and explain how the clock is calculated. The homeowner still experienced elapsed time, even when the operations report excludes closed hours.
Review the distribution of waiting times
| Measure | What it helps explain |
|---|---|
| Accepted but unassigned | Whether routing or ownership failed |
| Time to CRM receipt | Whether delivery delayed the inquiry |
| Time to first attempt | How long the homeowner waited before outreach began |
| Median and upper-percentile delay | Whether a small group waits much longer than the typical lead |
| Unattempted records | Work excluded when a report counts only completed attempts |
Keep unattempted leads in the report with their current age. Otherwise a team can appear fast because the slowest records never entered the completed-attempt calculation. Compare branches with similar hours and project scope, and investigate a few long-waiting records before drawing a source-quality conclusion.
Set a target the team can staff
Use your own pilot data to set an initial service target. Give the team a clear definition, operating window and escalation point when the queue falls behind. Do not borrow a universal conversion multiplier from an unrelated industry and present it as a forecast for your home-services program.
Document the approved follow-up cadence with the people responsible for contact practices. Respect opt-outs and other restrictions in that workflow. If the backlog grows, reduce intake or add coverage, then measure whether the next group receives a timely first attempt. Keep the change date beside the result.