The Case You Lost at 5:01 PM
An after-hours inquiry tests your intake system. How to measure the wait, assign the next action, and distinguish an attempted call from human contact.
Wolfe Services · · 3 min read
Updated
Imagine a prospective client calling at 5:01 p.m. on Friday, reaching voicemail, and speaking with another firm before yours returns the call. This is a hypothetical intake scenario, not a reported case result. It is useful because it makes an ordinary operating question concrete: what happens to an inquiry when the usual team is unavailable?
A firm can define a response policy without knowing whether the workflow follows it. The answer needs records of arrival, assignment, attempts, and actual contact. A recollection that the team is usually quick cannot establish the waiting time for the people it did not reach.
Measure the right event
Start by deciding what “response” means in the report. An automated confirmation, a staff member’s attempted call, and a conversation with the prospect are different events. Each may deserve a timestamp, but they should not share a label that implies a person was reached.
The initial clock starts when the inquiry arrives. A second timestamp records the first staff action. Actual contact gets its own record. If contact never occurs, keep that inquiry visible in the reporting population rather than calculating speed only among the people the firm successfully reached.
A median can describe the middle of a distribution while concealing a long wait for a smaller group. Read it alongside a slower percentile, the sample size, and the count still awaiting contact. Those measures help the team locate a staffing or routing issue; they do not by themselves prove why a prospect chose another firm.
Keep two clocks after hours
Business hours are a reasonable basis for an internal service target. Elapsed hours describe what the prospect experienced. Record both when assessing after-hours coverage.
A Friday-evening inquiry answered on Monday might comply with a business-hours rule while still involving a long elapsed wait. Leadership needs that distinction when deciding whether to change coverage. Calling the result fast or slow without defining the clock makes the discussion harder than it needs to be.
Assign the next action
A shared inbox can tell several people that an inquiry exists without making anyone responsible for it. The operating workflow should show who owns the next action and who receives an alert when it remains overdue.
This is part of the intake discipline behind Docket. The product’s published capabilities and its roadmap remain separate: connecting an inquiry to an intake workflow does not mean every retained outcome already flows back to marketing automatically. The contact-form field note follows those boundaries.
Walk through one Friday inquiry
Use an approved test record to follow the route from arrival to assignment. Then inspect an appropriate internal sample of actual inquiries to establish what happened in practice. Keep personal details out of any marketing presentation.
Ask when staff first acted, whether they reached the prospect, which clock the report uses, and what happened when the inquiry remained open. If a record is missing, identify the missing boundary. If responsibility was unclear, assign it. The useful outcome of the exercise is a specific change that the next inquiry can test.