When a restoration inquiry does not become work, the phone conversation is only one possible cause. The property may be outside your territory, the caller may need a service you do not offer, or a qualified inquiry may stall after a handoff. An audit should distinguish those outcomes instead of treating every unanswered or unbooked call as lost revenue.
Use an inquiry funnel with explicit stages
Define a small set of stages your team can identify consistently: call received, conversation completed, eligible inquiry, assigned follow-up, and accepted work. Keep spam, existing-job calls, and out-of-scope requests visible as separate outcomes.
This makes the denominator meaningful. A booking rate calculated from all phone traffic can fall because active customers called more often, even if new-loss handling improved.
Separate the failure from its remedy
Investigate the stage where the record stops progressing.
| At a glance | Observed gap | First thing to inspect |
|---|---|---|
| Call not answered | No completed conversation | Public number, forwarding path, hours, and fallback |
| Incomplete intake | Missing address or callback information | Required questions and correction handling |
| No ownership | Details delivered but nobody accepted | Recipient rules and acknowledgement process |
| Delayed follow-up | Accepted inquiry without the next action | Workload, availability, and promised expectations |
| No job | Qualified conversation without accepted work | Reason for not proceeding; do not assume an answering failure |
Review a representative sample
Choose a period containing both ordinary and busy days. Include answered calls, missed calls, transferred calls, and inquiries marked out of scope. Assign one reviewer to apply the definitions, then have another person spot-check ambiguous cases.
For each eligible inquiry, locate the call, the handoff, and the final disposition. If records cannot be connected, record that as a data gap rather than guessing what happened.
Keep a short exception log
Each entry should describe an observable issue and the next investigation.
- The affected stage and the evidence available.
- Whether the caller’s details were sufficient for follow-up.
- The intended recipient and whether ownership was acknowledged.
- The expectation communicated to the caller.
- The actual outcome or the fact that it is still unknown.
- The person responsible for resolving the process issue.
Fix the smallest process that explains the problem
Missing calls may require a routing change. Incorrect addresses may require a confirmation step. Unclaimed messages may require a named owner. A CRM delivery problem needs an exception path. These are different interventions, and replacing the answering provider will not automatically resolve all of them.
Retest the affected scenario after the change. Over time, look for fewer exceptions at that stage rather than assuming a rise in total jobs proves the intervention worked.
Make the business case with your own numbers
Use observed eligible inquiries, actual conversion, and your own contribution-margin assumptions if you estimate an opportunity. Keep the estimate separate from recorded revenue. Do not multiply every missed call by an average job value and label the result a loss.
Hank can support the answering and intake parts of the workflow. For a concrete starting point, review the intake reference and the handoff ownership guide.
Where to go from here
Review restoration answering and accountable handoffs against the gaps you found. Keep answered calls, accepted handoffs, and booked jobs separate when evaluating the result.