A follow-up system that survives a busy week

Most sales that are lost are lost by default after the second contact, before the customer has ever said no. Not to a competitor with a better product, and not on price. They stop because nobody called again, and by the time somebody notices, the customer has bought elsewhere and the record says lost.

A follow-up system is not a discipline problem to be solved with reminders on a whiteboard. It is a design problem with three parts, and each of them fails in a predictable way.

Rule one: set it during the call, never after

The moment a customer agrees to a callback is the only moment the arrangement exists in anybody head. If capturing it requires a second action, opening a screen, writing in a diary, sending yourself a message, it will happen for the first few calls of the day and stop happening by the fourth.

This is why the follow-up date belongs in the same sheet as the call outcome. One flow, no context switch: status, remark, date, done. In Telodial that is two taps and the next number is already ringing.

Rule two: it has to interrupt, not wait

A list of follow-ups due today is not materially better than a diary, because both require somebody to remember to look. On a day with a hundred and sixty calls, nobody looks.

A follow-up that rings, full screen, at the agreed time, survives a busy week. This is the single change teams report as the reason the software paid for itself, and it is unglamorous: not intelligence, not automation, just an alarm attached to a customer record with the last remark on it.

Rule three: carry a reason

A follow-up with a date and no context produces a checking in call, which asks the customer to restate their own situation for your benefit. It converts badly and it slightly annoys people.

The remark taken on the previous call is what turns that into a real conversation: he was waiting on the loan sanction, she wanted to discuss it with her husband over the weekend, they were comparing with two other quotations. A call that opens there continues something. A call that opens with checking in restarts from nothing.

A cadence that works for most businesses

The spacing matters much less than people think, and far less than whether the calls happen at all. As a default:

1. Within a day of the first conversation, with whatever was promised.
2. Three days later, if there was no decision.
3. A week after that.
4. Fortnightly while the customer is still deciding.
5. A dated revisit for anyone who postponed, on the date they named.

Every one of those is a dated follow-up with a reason, not a vague intention to stay in touch.

The list nobody works

Two lists usually contain more money than the fresh leads a business is spending on.

Today follow-ups, called as a block first thing in the morning, before new enquiries arrive. Everything promised yesterday, handled before the day gets away.

Lost leads older than a quarter. Most of them were never actually refused; they went quiet and got tidied into lost. Filtered, minus the genuine refusals, and dialed with the original remarks on screen, this is consistently the cheapest month of business a calling team can have.

Both are just filtered lists that an auto dialer can work through. That is the whole trick: a follow-up system is not a philosophy, it is a queue that fills itself and rings on time.

The mechanics are on the follow-up reminders page, and the wider argument for capturing outcomes on the call is in what telecalling CRM software is.