A missed event is not automatically a lost job
A caller may try twice, leave a voicemail, reach another line, or call about an existing job. A missed-call report contains events; it does not by itself establish new demand, suitability, or lost revenue.
Preserve provider event IDs and times. Group events only when the evidence supports the same service request. Keep uncertain duplicate notices separate until checked. One telephone number can represent multiple jobs, so do not deduplicate the entire month by phone number.
- New request or existing-job update?
- Duplicate notification or a separate attempt?
- Already connected through another route?
- Suitable service request, non-fit, or still unknown?
Give the review a clear owner
Use a routine that fits staffing and service expectations. This guide does not prescribe a universal callback speed or automatically text anyone. Any messaging or recording system needs its own verified setup and appropriate permissions.
If no one can take after-hours work, an automated acknowledgment alone does not create capacity. Review the ad schedule, service promise, and actual answering arrangement together.
- Select the missed events since the last review and identify already-handled requests.
- Check the provider log and job records for duplicates and existing connections.
- Assign an appropriate follow-up owner, respecting the customer's request, timing, and permissions.
- Record the attempt and whether contact was made; do not label an attempt a recovery.
- Confirm suitability, quote, booking, and later completion in the request record.
- Close with a confirmed outcome or retain the unknown state and next check.
Follow the request through the review
The six call/voicemail events in this example do not mean six lost jobs. There are three new requests after excluding the existing-job update: one known suitable, one unsuitable, and one unresolved. One completed job is linked to follow-up. Payment still needs its own evidence.
Do not multiply missed events by an average tow price and call the result recovered revenue. Such a figure would assume unique demand, suitability, booking, completion, and collection without proving any of them.
| Event group | What happened | Count |
|---|---|---|
| MC-01: two missed attempts | Callback connected; suitable request; job later completed. | One inquiry and one confirmed completed job. |
| MC-02: missed call | Caller was checking an existing job. | An operational update, not a new lead. |
| MC-03: missed call | Callback attempted; no response. | One unresolved request, not recovered revenue. |
| MC-04: missed call + voicemail | Out-of-area request confirmed. | One unsuitable request; no booked job. |
Keep the recovery measures separate
Compare similar periods and note changes in staffing, service availability, or advertising. A rise in callbacks may reflect more missed calls rather than better handling. A fall in the queue may reflect unrecorded outcomes rather than resolution.
At the end of the week, choose one process change and check whether it reduces the actual gap: unclear responsibility, repeated attempts, missing job IDs, or unconfirmed payment. Keep private caller details in approved operational systems, not public tools or analytics.
| Measure | What it tells you |
|---|---|
| Eligible unresolved requests | The queue requiring review after removing verified duplicates and handled updates. |
| Follow-up attempts | Work attempted, not people reached. |
| Connected requests | Contacts made, not automatically suitable inquiries. |
| Booked requests | Confirmed accepted work, which can still cancel. |
| Completed requests | Confirmed work linked to the original inquiry. |
| Net collected | Recorded payment less refunds for matched jobs, with unknown amounts separate. |
Use this at your next review
Missed-call review log
A simple editable text worksheet. Keep completed copies and private customer information in your own approved systems.
- Review period and responsible person
- Request ID and provider event IDs/times
- Duplicate / existing job / new request / uncertain; evidence
- Already handled? Appropriate next action and owner
- Follow-up attempt date; connected? Suitability confirmed?
- Quote / booked / completed / net collection; supporting records
- Unresolved item and next check; one process improvement