How do you stop follow-ups and renewals slipping through the cracks?

Follow-ups, service dates, maintenance schedules and renewals are some of the most predictable revenue a business has. You’ve usually known about them for months. That’s what makes it hurt when one goes past without anyone making contact.

Here’s why they slip, and a simple way to stop it.

Why they actually slip

In most businesses it comes down to one of three things.

The date is right but nobody owns it. The date sits correctly in the job software or a spreadsheet, a list gets run each month, and it lands in an inbox four people can see. Everybody assumes somebody else has it. That holds most of the time. In a busy month it doesn’t.

The date is wrong. A job got rescheduled, a contract was varied, or the customer’s details changed and the record never got updated. The list looks clean and it’s pointing you at the wrong week.

The process depends on the customer replying. You send the reminder or the quote. The customer is busy. You send it again. Then the file goes quiet, and quiet files don’t create tasks. Nothing flags that it has stalled, so it stalls until it’s too late.

None of those are about someone being lazy. They’re all the same gap: the process lives in someone’s memory and their inbox.

Start with data you can trust

There’s no point automating reminders against dates you don’t believe. Before building anything, do one quick check.

Export everything with a follow-up, service or renewal date in the next twelve months. Take a sample of thirty and check:

• Does the date in your system match the real agreement, job or contract?
• Is there a named person responsible, and are they still with the business?
• Is there a current phone number and email for the customer?

If more than two or three fail, fix the data first. Automation on bad data just produces well-timed mistakes.

A timeline that holds up

Adjust the numbers to suit your business. The shape is what matters.

Sixty days out: the internal check

Nothing goes to the customer yet. A task lands with the right person to look at the account and ask: has anything changed that I should know about before I contact them?

Forty-five days out: first customer contact

The reminder, quote or renewal offer goes out from a real person’s address, in plain language, with a specific date and a reason. “I need to lock this in by the 14th so we can hold your spot in the schedule.” A deadline with a reason gets a response.

Thirty-eight days out: first chase, automatic

If nothing has come back, one short reminder goes out on its own. Two sentences, straight to the point.

Thirty days out: the status changes

This is the step most businesses skip, and it’s the one that matters most. If there’s still no reply, the item moves to “awaiting customer” on a board or report. A stalled item now looks different from a healthy one at a glance.

Twenty days out: phone call

A task for a person. Two written prompts have already been tried, so a third email is just noise.

Seven days out and three days out: confirmation

Automatic, and more direct each time. The last one should say plainly what happens if there’s no answer.

A week after the job or renewal: the check-in

Almost nobody does this and it’s the cheapest goodwill you’ll ever get. A short note confirming everything’s done, with anything they need attached. It’s also the natural moment to spot the next piece of work.

Automate the prompts, keep the judgement

Everything in that timeline splits into two piles.

The reminders, status changes and task creation are mechanical. They should run whether or not anyone remembers, and run the same way for your smallest customer and your biggest.

Pricing decisions, what to recommend and the phone calls stay with a person. Ask one question of every step: would I be comfortable telling the customer this happened without anyone looking at it? Reminders pass that test. Recommendations don’t.

Where it should live

You’ve got three sensible options.

Inside the system you already use. Most job management and CRM tools have reminders, tasks and statuses. Use them properly and agree on a naming convention. It’s the cheapest option and works up to a point.

A light layer beside it. A CRM or workflow tool that reads the dates from your main system and owns the reminders, tasks and statuses. The key is deciding which system is the master when the two disagree, and writing that down.

Replace everything. Rarely the right answer for a team of five to fifty. Migrations cost real money and disruption, and the underlying problem is usually process.

Three numbers that tell you it’s working

1. Items sitting at “awaiting customer” inside twenty days. Your early warning. If it’s climbing, your first contact is too long or going to the wrong person.
2. Items confirmed in the last week. Every one of these ran too close. A healthy business has very few.
3. Results by person, as well as overall. An overall number can hide one person carrying more than they can manage.

None of those need a big reporting project. They’re three filtered views of a list you already have.

What good feels like

It feels quiet. The monthly list stops being a source of dread, because the only items asking for attention are the ones that need it. Nobody’s digging through a mailbox to work out what happened, and conversations with customers are about the work instead of apologising for being late.

That’s achievable without replacing your software. It takes a clean list, a written timeline, and a system that changes the status when the customer goes quiet. If you’re not sure how leaky your follow-up is, the free Business Systems Scorecard will show you in two minutes.