Missed calls are leads: a callback routine your team will actually keep

Of all the ways a lead reaches you, a missed call takes the most effort on their side and the least on yours. Nobody paid for the click. Nobody filled in a form. Someone found your number — on a hoarding, a delivery van, a visiting card, a listing — and dialled it. Then the agent was on another call, or at lunch, or the phone was in a drawer, and the call became a red line in a call log that scrolls out of sight by the afternoon.

Most teams agree that missed calls should be returned. Very few have decided who returns them, by when, with what words, and what happens when the callback is not answered either. That is the routine this article sets out, followed by how the missed-call setting in LumaKol works, in detail, so you can decide whether to switch it on.

Why missed calls slip through

It is rarely laziness. Missed calls fall through gaps in how the work is organised.

• Nobody owns them. A missed call is not in anyone’s queue, so it is nobody’s job until somebody happens to notice it.
• The number has no name. An unknown number in a call log could be a buyer, a supplier, a courier or a wrong number, and when a caller is busy, “could be anything” loses to the named lead in front of them.
• It lives on one phone. If the agent is off sick, on leave or has left the company, the missed call is invisible to everyone else.
• There is no record of the callback. Even when someone does ring back, nothing shows that they did, whether it connected, or what was said — so the next person cannot pick it up.

Every one of these is fixed the same way: the missed call has to become a lead, with an owner and a due time, the moment it happens.

How the missed-call setting works

In LumaKol, an owner or admin chooses what happens under Settings → Calling policy → “Calls from new numbers”. A new number here means one that is not already a lead in your workspace. There are three options:

Once it is on, this is what happens on each call:

• Only the work SIM is read, on Android phones of your agents and team leads. The personal SIM is never read, and outgoing calls to numbers that are not leads are never sent. iPhones cannot do this at all, because iOS does not let apps read call history.
• If the number already belongs to a lead — as its main number or one of its other numbers — no new lead is made. The call is added to that lead’s timeline instead.
• If the number is new, a lead is created named “Missed call” followed by the number, with the source Missed call, owned by the agent whose phone rang, and with a callback due now — so it sits among their follow-ups straight away.
• The agent’s phone shows a notification, “New lead from a missed call”. Tapping it opens the lead, ready to call back. If your workspace hides phone numbers from agents, the notification carries only the prompt to call back, not the number.
• A second call from the same new number does not make a second lead; it is attached to the one already created.
• Agents are told plainly. The app shows a notice, where it explains call-log access, that the workspace turns calls from new numbers into leads and so those numbers and call times are sent to LumaKol.

Keeping suppliers and wrong numbers out

Not every unknown caller is a prospect. The transporter, the landlord, a candidate chasing an interview and the person who dialled one digit wrong will all ring a published number. On a lead made from a missed call, the lead page — on the web and in the Android app — has a Not a lead button. It deletes the lead and remembers the number, so later calls from it never become a lead again. Agents can use it on their own leads, because they are the ones who take these calls. If a number is marked by mistake, an owner or admin can remove it from the list of numbers marked “not a lead” under Settings → Calling policy, and its next call will create a lead as normal.

Who calls back

The default — the agent whose phone rang — is right most of the time. The caller dialled that number, so a callback from the same number is one they recognise rather than another stranger. The agent may also have context the system does not: the hoarding in their territory, the listing that carries their number.

The default fails when that agent is unavailable. A missed call to someone on leave is a lead with a callback due and nobody to make it. Two ways to cover that gap:

• A manager reassigns the lead from the web app. Search the Leads list for “Missed call” to see the ones still carrying their automatic name, and filter by Overdue follow-ups to find the callbacks that have slipped.
• An automation does it for you. Under Automations, create a rule that starts “When a follow-up is overdue by” a time you choose, limited to leads from the source Missed calls, and have it notify managers or give the lead to someone else. Use the overdue trigger rather than the “isn’t called within” trigger: the missed call itself is already on the lead’s timeline, so the lead never counts as uncalled.

How fast

The person who called you is often trying other numbers too, and whoever rings back first has the best chance of the conversation. Set targets your team can actually hold, by situation, rather than one number that is impossible after six in the evening.

The last row matters. A missed call at nine at night still deserves a callback, but the next morning, before the agent opens their regular queue — not after it.

What to say

A missed-call callback is different from an outbound call: the other person started it. Do not open with a pitch. Open with the fact that they called, and let them tell you why.

“Good morning, this is the sales desk at [your company]. We had a missed call from this number a little while ago and I wanted to call you back — how can I help?”

Then, in this order:

1. Find out who they are. A buyer, an existing customer, a supplier or a wrong number. Thirty seconds settles it.
2. If it is not a sales enquiry, end politely and press Not a lead, so the number does not come back as a lead next week.
3. If it is an enquiry, get their name and what prompted the call — the advertisement, the listing, a friend’s recommendation. That is your real source, and the lead name “Missed call” plus a number tells nobody anything. Correct the name from the lead page in the web app afterwards, or ask a manager to.
4. Agree a next step with a time: a quote by this evening, a visit on Thursday, a call back at six when they are free.
5. Log the outcome when the call ends. The outcome and its follow-up time are what turn the callback into a lead the rest of the team can pick up.

When your callback is not answered either

It happens often: they called you while free, and now they are busy. Treat the callback like any other unanswered call rather than giving up after one try.

• Log No answer. With LumaKol’s default outcomes it sets the next follow-up three hours later; your admin can change that.
• Send a short WhatsApp message from one of your message templates, so they know who called and can reply when they are free.
• Let the calling policy handle the rest. After each unanswered call the lead waits the time you set before it comes back into the queue, and after the maximum number of attempts it is flagged for review instead of being dialled forever.