The trigger is a field nobody reads
Retention comes up in most strategy sessions and gets a date in the calendar in very few of them. When we ask what starts a renewal conversation, the answer is usually that somebody notices. A renewal noticed late is one the customer has made up their mind about. No one designed it that way. The account manager who is supposed to notice has an inbox that refills every hour, and a date sitting in a field two clicks away loses to it.
The date is there. For the teams we sit with, it went into a system on the day the customer signed: a contract end date in the CRM, the next service due in the scheduling tool, the anniversary of the first invoice in the accounting system, the start date on a membership record. It was entered because billing or the calendar needed it, and nothing reads it again until the customer rings to cancel or a card payment fails. The field exists and nothing is attached to it.
Renewal work sits in an unusual position against the four conditions we set for automating anything. The trigger, which is the condition most nominated tasks fail, was met the day the customer signed. The steps run the same way each time, because one annual renewal looks much like the next. What is missing is a decision about what should happen at a set distance from the date, and a person willing to own it.
A renewal date passes in silence. Nothing lands in an inbox when it comes round, so a team that would never leave a web enquiry unanswered for a week can miss it without noticing, which is why we build this sequence second, once follow-up on enquiries is running.
What a renewal sequence looks like
It starts earlier than teams expect. We count back from the date and agree the distances with the client, ninety days before an annual contract ends, or two weeks before a piece of equipment is due its service. The first message at that distance is not an ask. It is a short record of what the customer received in the period and what changed, sent from the account owner's name and written the way that person writes.
The second message goes closer in and makes the ask, which is to confirm the renewal or to book a short call about what would need to change. One ask per message, the same rule as enquiry follow-up, and the booking link goes to the account owner's own calendar. The argument over these two messages is about what they are allowed to claim. A line about the year's usage or the number of visits has to come from a field somebody trusts, and where no such field exists the line comes out.
The third step is not a message to the customer at all. At the same distance from the date, a task lands on the account owner's list with the customer's record attached, so the accounts worth a phone call get one from a person who has the history in front of them. The automation does the assembly. The person decides which accounts get the call, and that stays with them for as long as the sequence runs.
After the date, the sequence has two directions. If the customer renewed, the run closes and the date moves forward by one period, which most CRMs do not do on their own and which we spend the longest configuring. Otherwise a short lapse run begins, one message shortly after the date and one more at an agreed interval, and then the record moves to a lapsed list, where it waits for a reactivation sequence with a different job.
Where it stops
The stopping rules for a renewal sequence are stricter than its sending rules, and stricter than the ones we hold enquiry follow-up to. It stops on renewal. That sounds obvious and it is the rule that fails most often, because it needs the payment or contract system to tell the CRM that the money arrived. Where that link does not exist we build it first. A renewal reminder sent to a customer who paid last week is the message that gets the next one deleted unread.
It stops on any reply, and the reply goes to a person. It also holds where there is an open complaint or an unresolved support ticket on the account, a rule enquiry follow-up doesn't need and renewal work cannot run without. A message about next year's contract that lands in the middle of a dispute about this year's does damage that no amount of good wording recovers. So the sequence checks the ticket system on the day it is due to send, and waits if anything is open.
A cancellation notice stops it, and it does not restart. A customer who has written to say they are leaving and then receives a note about their upcoming renewal has learned that the company doesn't read its own mail. The record gets a flag a person set, and the sequence reads the flag before every send.
The cap on messages is lower than for an enquiry. A prospect who hasn't replied is a stranger, and one message too many costs a stranger's mild annoyance. A customer has a year of invoices behind them, and the same mistake costs the account. We hold to two messages before the date and at most two after it. The numbers are agreed with the client, and the person whose name is at the bottom can lower them at any time.
How it differs from enquiry follow-up
Timing is the first argument, and it runs longer than any argument about reply time. A renewal message has to arrive at the right distance from a date the company has known about for a year, and the room rarely agrees on that distance at the first attempt. Too early and it gets filed. After the date, it is an apology.
What goes in the message follows from what is on the record. A renewal message has a year of invoices and service visits to draw on, so it presents that history and skips the qualifying questions an enquiry message has to ask. The cost of a wrong field goes up with it. A message that names the wrong plan or the wrong start date tells the customer the company knows less about them than they assumed, and that is a bad thing to learn ninety days before a decision.
A renewal belongs to whoever holds the relationship, so the sequence sends from a named account owner and routes every reply and every task to that person, where a shared inbox would have done for an enquiry. Accounts with no owner are common once the customer list has outgrown the people who sold to it, and we settle the owner before the build. If nobody can be named, the account is left out of the sequence until somebody can.
Day thirty comes before the result does. Renewal work proves itself at the speed of the renewal cycle, and a company on annual contracts will not have a full reading for a year. That leaves the baseline counting the process. It records how many customer records carry a date, how many of those dates the team trusts, how many accounts have a named owner, and how many of the renewals that fell in the last ninety days were contacted before the date. The same four counts are taken the same way at day thirty.
