Finding missed callbacks

A missed callback is a broken promise, not a missed call

Two different failures get called the same thing. A missed inbound call is a customer who called and could not reach anyone. A missed callback is a customer who did reach you, was promised a call back, and never got one. Both cost you. The second costs more, because the customer did everything right, waited for you, and learned something about how your team keeps its word.

A callback promise comes in two forms. The rep offers it: “Let me check with the underwriter and call you back this afternoon.” Or the customer asks for it: “Can you call me after five?” A callback request becomes a promise the moment the rep says yes. Count both.

Why missed callbacks stay invisible

A callback that happened leaves a trace: a call in the log, a note, often a recording. A callback that never happened leaves nothing, except in the conversation where it was promised. That is why so few teams know how many they miss.

• The promise lives in the conversation. “I will call you back” is said out loud and rarely typed. If nobody creates a task, the only record is the recording or the text thread.
• Reports count activity, not promises. Calls made, talk time and dials per rep can all look healthy on a day when three promised callbacks were skipped.
• The customer does not complain. Few people call to ask why you did not call. They answer the next company's call instead.
• The promise outlives the shift. A callback promised at 4:45 for “first thing tomorrow” belongs to a rep who may be off tomorrow.

Where callbacks get promised

Listen for five kinds. Each one tends to slip at a different point, so it helps to know which kind you are looking at.

Texts carry the same promises. “I will give you a call tomorrow” in a thread is as much a promise as the spoken version, and it is easier to find because it is already written down.

How to find them in one week of calls

You do not need to review every call your team has ever made. One recent week, worked carefully, will show you the pattern.

1. Pick one recent week and gather its calls and text threads, including calls that went to voicemail and threads on company numbers.
2. List every promise. Listen, or read transcripts and notes, for the phrases your team uses: “call you back,” “get back to you,” “give you a call,” “reach out tomorrow,” “after I check.” Add every voicemail that asked for a call.
3. Write each promise as a row with five fields: the customer, the number, who promised, what they promised, and the deadline.
4. Set the deadline the same way every time. A named time is the deadline. “Today” means the end of that business day. “Tomorrow” means the end of the next business day. A promise with no time at all also gets the end of the next business day, which is generous.
5. Check the call log for each row. Look for a call to that number, from anyone on the team, before the deadline.
6. Mark each row with one of the four results below.

• Kept. A call went out before the deadline, whether or not the customer answered. If it reached voicemail, the next attempt is a new promise with its own time.
• Late. The call went out, but after the deadline.
• Missed. No call to that number at all.
• Can't tell. You cannot see whether a call happened, usually because it was made from a personal phone. That is a finding in itself: a call you cannot see is a promise you cannot manage.

Two judgment calls come up quickly. A text sent instead of a promised call does not count as kept unless the customer asked for a text. A callback made by a teammate does count, because the customer cares that someone called, not who.

A worked example

Synthetic example. These figures are invented to show the method, not to suggest what your team should find.

A team of eight reps at an independent insurance agency reviews one week: 212 calls and text threads. The manager finds 41 promised callbacks. Checked against the call log, 29 were kept, 5 were late, 5 were missed and 2 were can't tell, because those calls were made from personal phones. That is 29 plus 5 plus 5 plus 2, so all 41 promises are accounted for.

The misses are not random. Three of the five are answer callbacks promised on Friday afternoon, “let me check with the underwriter and call you back,” that rolled into the weekend and were forgotten by Monday. The other two are customer-set times after five o'clock, when the rep who made the promise had already left. That is two fixes, not five: a Friday rule and an evening owner.

The manager calls the five customers that morning, before working on either fix.

Why callbacks get missed, and the fix for each

• No time attached. “I will call you back” has no deadline, so it can never be late and nobody notices when it lapses. The fix: always name a time out loud, and make it one you can keep.
• The promise never became a task. It lives in the rep's head until the next call pushes it out. The fix: create a dated task before taking the next call, with the number and what was promised.
• The owner went off shift. The fix: before anyone leaves, every callback due after their shift goes to a named person on the next one, with the context.
• Waiting on someone else. The rep is waiting for a manager, a specialist or a client before calling. The fix: call at the promised time anyway, with an update and a new time. An update is a kept promise. Silence is not.
• A handoff with no name. “Someone will call you” belongs to nobody. The fix: the person making the promise names who will call and when, and that person accepts the callback before the day ends.

The daily routine that keeps the next one from slipping

1. At the end of every call with a promise, say the time back to the customer and create the task before the next call.
2. Each morning, list today's callbacks and yesterday's overdue ones by owner. Overdue callbacks get made first.
3. Before each shift ends, hand every callback due after the shift to a named person on the next one.
4. Each week, repeat the one-week check on a sample of promises and compare the kept, late and missed counts with the week before.

The morning list recovers a miss while it is still a day old, and it fits inside the review in the four numbers a sales manager should see every morning. The weekly check tells you whether the routine is working. When you want every promised callback found across all of your team's calls, not only a weekly sample, see how a team can keep track of every promised callback and next step.

When you find one, call today

A missed callback does not get better with time. Call as soon as you find it, own it in one sentence, and bring what you promised. Synthetic example: “I said I would call you Tuesday with the renewal figures, and I did not. I am sorry. I have them now, and it takes two minutes.” No excuse, and no story about how busy the week was.

If the customer does not answer, text the same thing in two lines, with the answer if you have it or a specific time if you do not. Then keep that promise, because it is the one they will remember.

What a missed callback does not prove

It does not prove the customer was lost, or that they would have bought if you had called. It proves a promise was broken, which is a fact you can act on today. Keep the count about promises, and use your sales records for outcomes.

What to do this week

1. Pick last week and list every promised callback with its owner and deadline.
2. Check each one against the call log and mark it kept, late, missed or can't tell.
3. Call every missed customer today, starting with the oldest promise.
4. Find the point where each miss slipped, and fix the one that repeats.
5. Start the morning callback list tomorrow, and move customer calls off personal phones so every callback can be seen.