The first hour and the next day: how follow-up timing decides which leads you close

Ask any sales manager where deals are lost and they will say “price” or “competition”. Look at the data in their CRM and a different answer appears: the lead was called two days after it came in, the callback that was promised for Tuesday happened on Friday, and the third touch never happened at all. Timing is the cheapest conversion lever a team has, and the one most teams leave on the floor.

The first hour: speed beats polish

When someone fills in a form, clicks a lead ad or calls and misses you, they are in a buying frame of mind right now — often comparing several providers in the same sitting. A widely cited Harvard Business Review study of online leads (“The Short Life of Online Sales Leads”, 2011) found that firms which reached a lead within an hour were almost seven times more likely to qualify it than firms that waited even one more hour, and the gap kept widening after that.

You do not need a perfect pitch in that first call. You need to be the first human voice. A thirty-second “I saw your enquiry — is now a good time, or shall I call at six?” beats a polished call tomorrow.

• Route new leads to a phone, not an inbox. A CRM that pushes the lead to the agent’s mobile with a Call button removes the “I will check the sheet later” delay.
• Missed calls from unknown numbers are leads too. If your team uses Android phones, an owner or admin can set Settings → Calling policy → “Calls from new numbers” so that a missed call on the work SIM becomes a lead with a callback due now, owned by the agent whose phone rang. Otherwise return them within the hour and add the caller as a lead on the spot, so the callback promise lives somewhere other than the call log.
• Measure first-response time per agent and look at it every week. In LumaKol, Reports → Coaching shows speed to lead — how long new leads waited for a first call — and each caller’s time to first call. What is visible gets faster.
• Put a clock on it. An automation rule that passes a new lead to someone else, and tells the managers, when nobody has called it within ten or fifteen minutes turns the target into something the system enforces.

The promised callback: the only date that really matters

“Call me after 6” is a commitment. Keep it and you have earned trust before the pitch even starts; miss it and the customer files you under “unreliable” and answers the competitor who did call at six. The failure mode is rarely laziness — it is that the promise lives in an agent’s memory or a WhatsApp group rather than in a system with a reminder.

The fix is structural. Every call outcome should end with a follow-up time, chosen in a picker rather than typed as free text, stored in the agent’s time zone and surfaced as a due list the next morning. Overdue callbacks belong at the top of the queue in red, not on page three.

A cadence that works for most lead types

There is no universal sequence, but the shape below holds for enquiry-driven businesses — property, admissions, insurance, loans, clinics, travel. Adjust the intervals to your sales cycle; keep the discipline.

Notice that half the touches are not calls. A calling CRM with message templates lets an agent send the “Hi, this is Anita from Nair Realty — I called about the 2BHK you enquired on” message in one tap and logs it on the lead, so the next agent who picks up the file sees the whole thread.

You can also hand the shape of the cadence to a sequence. In LumaKol a sequence runs timed steps after a lead is added: emails go out on their own from your own email account (never from LumaKol), WhatsApp and SMS steps remind the lead’s owner with the text ready to send from their own phone, and task steps put the next call in their follow-ups. The lead leaves the sequence when it is won or lost, or as soon as a call is answered, so nobody gets a “just checking in” email after they have already spoken to you.

Know when to stop

Persistence has a ceiling. After a set number of attempts with no connection — five is common — a lead should leave the active queue, land in a nurture stage and stop consuming call time. This is also where compliance lives: a lead that asks not to be called must be marked do-not-call immediately and never resurface in a queue. Make the attempt counter and the do-not-call outcome part of the system, not notes — in LumaKol the attempt limit is a calling-policy setting, and the “Requested no contact” outcome moves the lead to Lost and out of every queue.

Making a team keep the cadence

1. Capture the outcome at the moment the call ends. A prompt that appears on the phone when the call disconnects gets filled; a form on a laptop later does not.
2. Default the next follow-up from the outcome. “Interested — call back” can pre-fill tomorrow 10:00; the agent only changes it if the customer said otherwise.
3. Start each day from the due list, not from the fresh leads. Callbacks first, then overdue, then new.
4. Show two numbers on the team board every day: callbacks kept on time, and leads untouched for more than 24 hours.
5. Review, do not police. A weekly ten-minute look at overdue callbacks per agent is enough once the system does the reminding.