Insurance renewal reminder calls: before it lapses
An insurance customer does not announce that they are leaving: the policy expires, a week or two passes, and they reappear elsewhere with a renewed policy. What makes this loss unusual is that its date is already in the database — it is calendar work. This article builds the renewal campaign: why customers do not renew, the five-touch calendar, a script covering four situations, the points that need care on a financial call, the data fields required, and the four numbers worth measuring.
Renewal loss happens quietly
An insurance customer rarely announces that they are leaving. The policy expires, a week or two passes, and the customer reappears elsewhere with a renewed policy — and nothing in any report calls that a lost customer, because formally nothing happened.
What makes this loss unusual is that its date is known in advance. Every policy's expiry is already in the database. This is not unpredictable customer behaviour; it is calendar work, and calendar work is where automation is at its most useful.
The problem is usually capacity rather than intent. The portfolio one agent can watch is finite, and renewal calls always compete with new-business calls. A call that brings a new customer shows a result today; a renewal call merely keeps what already exists — so it stays second in the queue.
Why customers do not renew
There are four typical reasons for not renewing, and only one of them is about price.
- They simply forgotThe largest group. The policy was bought a year ago, the expiry date is not in anyone's head, and nobody reminded them. All this group needs is one call on time.
- The contact details went staleThe number changed, the email bounces. A reminder was sent and reached nobody. This is a technical problem and it is solved with data quality.
- They are comparingThe customer is looking at the market and waiting for an answer. Timing decides here: a call before the comparison starts is a conversation, a call after it is a reply to an objection.
- They are unhappy with the termsThere was a claim last year, or service left a bad taste. This group is won by resolving the earlier experience rather than by a call — and this call must not be built as a sales call.
Running a renewal campaign without separating these four means reading the same text to everyone. For the first group one sentence is enough; for the fourth, that same sentence does damage.
The renewal calendar: when to call
A renewal campaign is not one call but a window. The pattern below is a common one; a company can move the dates to suit its portfolio, and what matters is that the sequence exists in writing.
- About 30 days before expiry: a reminder contact, aimed at learning the intent
- About 14 days before: a concrete offer and the paperwork path for those who fit
- About 7 days before: confirmation and clarity about the payment step
- One or two days before: a final reminder, only to those who have not replied
- About 7 days after expiry: a recovery window — which is a different script
The practical value of the sequence is that each step has its own goal. Trying to sell on the first call burns the whole window: the customer says «it's early yet» and meets the next call colder than the first.
The script: four situations, four continuations
A renewal call is short. Long explanation does not work here, because the customer already knows the product — what they need is the date, the amount and the step.
- Ready to renewConfirm, explain the paperwork and the payment step, name the person responsible and the timeframe. The outcome is written in the CRM as renewed.
- Thinking or comparingNo pressure. A specific date is agreed — «shall I call you Friday?» — and that date is logged as a reminder. The follow-up happens when the customer said, not when the campaign wants.
- A question about terms or priceThis is where the conversation goes to a person. Tariffs, coverage and exclusions are not the subject of an automated script.
- Not renewingAsk why, and write it down. A refusal with no reason produces the same result next year; a refusal with a reason is information about the portfolio.
What needs care on these calls
In financial services a call script is built under different rules from marketing copy. The lines below are not legal advice — they are practical points to settle together with the company's own internal rules and its regulatory obligations.
- Who is calling and why is made clear in the first sentence
- The script speaks only from information the company has approved — no improvisation
- Questions about tariffs and coverage go to a person rather than being answered automatically
- The company's rules on call recording and data handling apply
- A customer who declines does not re-enter the campaign — that is part of the list
- Calling hours are bounded: nothing is scheduled for nights or early mornings
How control is built into calling campaigns is covered at more length in compliance in banking call campaigns — most of what is written there applies to an insurance portfolio as well.
The data without which this campaign does not work
The quality of a renewal campaign follows the quality of the list. These are the minimum fields.
- Policy expiry date and type
- Contact number, and when it was last confirmed
- Renewal history — how many times renewed, how many times late
- Whether there is a claims history (the fact, not the content)
- Preferred channel and hour
- The previous refusal reason, if there was one
The field most often left empty is the last one. Not recording why someone declined forces the renewal campaign to start from zero every year.
How Vexvon supports this campaign
Vexvon's AI voice agent calls from each company's own scenario, approved information and escalation rules. The parts a renewal campaign uses:
- The target list is built from a CRM filter — expiry-date segments become separate campaigns, and one campaign holds up to 5,000 targets
- Preview shows, before the campaign starts, how many will be reached and which rows have no number
- The scenario defines the fields to extract: renewal intent, callback date, refusal reason
- When a question about tariffs or terms arrives, the agent hands the call to an operator
- Reminders are checked every minute and night hours are protected, so «call me Friday» does not get lost
How a quote request is handled on the chat channel is shown in the insurance chatbot article; this one is about the renewal window on the call channel. How the calls are stored is on the CRM page.
What to measure
The result of a renewal campaign is not one number. Four indicators together give the picture.
- Renewal rate — what share of the policies in the window renewed
- Early renewal share — those who renewed before expiry, the clearest sign the campaign is working
- Reach rate — what share of the numbers on the list could be spoken to at all
- Distribution of refusal reasons — price, service, no longer needed
How these are assembled into a report is shown on the analytics page. The cadence should be monthly, because a different segment of the portfolio enters the window each month.
Where to start
There is no need to cover the whole portfolio at once. Starting with one segment makes measurement easier and leaves room to correct the script.
- Pick one product among the policies expiring next month
- Build only two touches: 30 days and 7 days
- Make the refusal-reason field mandatory
- After a month, compare the early-renewal share with the previous period
To talk through how this window would work on your own portfolio, get in touch.