The Policy Anniversary Call: A 5-Minute Script and the Automation That Makes Sure It Happens
The cheapest revenue in the business and the most skipped, because nothing reminds you. A five-minute script, minute by minute, and the five-step system that runs it.
"How many of your clients' policy anniversaries do you consistently reach out on? Not selling, just checking in. I realized I was missing a lot of those moments." An agent asked that three times over one summer, each time a little more sure that it was low-hanging fruit and each time admitting he still was not doing it. The answers he got from other agents ranged from "sell and forget is the most common failing of advisors" to one producer who credited touchpoints on existing clients for well over a million dollars of annuity premium in a single year. The anniversary call is the cheapest revenue in the business and the most skipped, for one reason: nothing reminds you. Here is the five-minute version of the call, and the automation that makes sure it happens without you remembering. Why the anniversary, specifically It is a date you already have. Every policy record has an effective date. It is the one moment a client expects to hear from an insurance agent and is not annoyed by it. It is when life has changed by exactly one year: a new baby, a new mortgage, a raise, a diagnosis, a parent moving in. Every one of those is a coverage conversation, and you did not have to manufacture it. It is when policies lapse. A client who is thinking about dropping coverage usually does it around a renewal or a rate change, and a call the week before is the difference between a saved policy and a chargeback. The five-minute script Minute 1, the reason. "Hi Maria, it's Dan, your insurance agent. Your policy with us turned one this week and I make a point of checking in on every anniversary. Do you have five minutes?" Say the anniversary. It tells them this is a service call, not a sales call. Minute 2, the policy. Confirm the basics out loud: who is covered, the amount, the monthly draft, the beneficiary. "Is that still right?" Beneficiary changes are the most common thing this question surfaces, and the most consequential. Minute 3, the year. "What's changed this year? Anyone new in the house, anyone moved out, any changes at work?" Then listen. This is the whole call. Minute 4, the household. If a spouse or adult child came up in minute 3 and is not covered, ask one question about them. If nothing came up, ask: "Is there anyone in the family who's been meaning to sort out coverage and hasn't?" Several agents make a habit of speaking with beneficiaries directly, with the client's blessing, so the beneficiary knows the policy exists and has someone to call. Minute 5, the close. One of two endings. Nothing changed: "Great. I'll call again next year, and my number is in your phone if anything comes up before then." Something changed: "Let me put together the numbers on that and call you Thursday at the same time." Then create the task before you hang up. Two rules. Never open with an offer. Log what you heard on the contact before the next call, because next year's call starts from this year's note. The automation The agent who asked the question three times had already identified the problem: it sounds good and rarely happens. Make it a system, not a habit. Effective date on every policy record. If it is in a spreadsheet, it is not in the system. Import the book with dates. A reminder that fires from the date. Two weeks before each policy anniversary, the CRM creates a task for the servicing agent with the client's name, the policy, and last year's note. A birthday reminder works the same way and some agents prefer it. A text the client sees first. Day of the anniversary, one message from the agency number: "Your policy turned one this week. Dan will give you a quick call to make sure everything's still right." The call is expected, so it is answered. An alert when the policy changes. If a policy lapses, charges back, or stops paying, the servicing agent should be alerted that day, not at the next anniversary. A weekly count. Anniversaries due, calls completed, follow-ups created. If the count is zero for two weeks, the system is not the problem. What it produces Beneficiary corrections, which are worth the call on their own. Coverage on spouses and children who were never asked. Policies saved a week before they would have lapsed. And a book that knows its agent, which is the only kind of book that pays renewals for twenty years. Where AgencyView fits AgencyView keeps every policy as a record on the contact with its effective date, and household members as their own linked records, so the anniversary reminder and the household question are both built from data already there. Tasks are created from the CRM's workflows on a date field; texts go from the agency's number; and Contact Alerts flag a policy that has lapsed, charged back or stopped paying, along with missing contact details and text opt-outs, the day they appear. Every edit to a contact is recorded, so next year's call starts from this year's note.
Where AgencyView fits
Keep reading
Share: Facebook · LinkedIn · X · Email
All articles · AgencyView