A missed-call follow-up window that protects the lead

*October 22, 2026*

A missed call is a lead with a clock on it. The caller may try a competitor before the callback arrives. A written follow-up window turns a vague promise to call back into an owned task with a deadline.

Start by defining the window for each call type. A new sales enquiry is not the same as an existing customer asking about a delivery. Record the target, the owner, and the escalation when the target is missed.

Set the window by caller value

Define new business calls as the shortest window your team can actually meet. Existing customers with an open issue may need a different target. Internal calls can wait.

Do not publish a five-minute promise unless coverage supports it every hour you advertise. A missed promise is worse than a realistic one.

Record the attempt, not just the outcome

Each callback should record the time of the first attempt, the number used, whether it connected, and the next planned attempt. A single "called back" note hides three failed attempts.

Where policy allows, leave a short voicemail with the company name, the reason for the call, and a safe callback number. Do not leave account details.

Handle unreachable callers

Set a maximum number of attempts and a final message. After that, move the lead to a nurture queue with the reason and the date.

If the caller asked not to be contacted, record the request and stop. The opt-out is a fact that must survive any handoff.

Review the window weekly

Report the share of missed calls returned inside the window, the median time to first attempt, and the count still unassigned. A high return rate with long delays is still a service problem.

The manager reviews the exceptions, not every call. Two or three failed cases usually reveal whether the issue is staffing, script, or ownership.