Insurance retention power dial playbook: blocks, cadence and renewal KPIs

The call block, in two shifts

Retention is a date-driven operation. A renewal date is a hard deadline and a policy that lapses is expensive to win back, so the queue should be organized by time remaining rather than by account value.

Daytime, renewals inside 30 days. Work newest-arriving renewal notices first, and work accounts with a large premium increase early in the window because those policyholders shop fastest.

Evening, working policyholders. Many policyholders cannot take a call during the day, and the evening block inside the local calling window reaches the households whose renewals would otherwise go unchallenged.

List hygiene and segmentation

Import the renewal book with the policy and line, premium change, claims history, tenure, payment method and prior shop history. Segment by line of business and by premium change band, because a small auto increase and a large property increase are different conversations.

Suppress accounts the carrier or the policyholder has asked not to contact, accounts in an active claim dispute, and accounts already in a cancellation workflow.

Attempt cadence

Four touches over two weeks, compressed against the renewal date.

• Day 1 explain the change: premium change, reason, shopping status, applied discounts.
• Day 4 revised summary: send the updated renewal summary with anything applied.
• Day 8 second time of day: evening if the first attempts were mornings.
• Day 14 close-out before the renewal date.
• Then park unless the policy lapses or the policyholder asked for a later call.

The calling window comes from 16 CFR 310.4(c), which permits residential calls between 8:00 a.m. and 9:00 p.m. local time at the called person’s location. Honor the National DNC Registry rules at 47 CFR 64.1200 and any stop request.

Dispositions by shop and lapse status

• Renewal confirmed: payment method.
• Shopped and kept: with the reason.
• Shopping elsewhere: competitor and reason.
• Payment plan: schedule and dates.
• Lapse risk: the specific trigger.
• Cancelled: reason.
• Unreachable: attempt count.
• Do not call: permanent.

Working three lines on a renewal book

DialBreeze rings up to three numbers per specialist and the specialist takes the live answer, with a recorded voicemail dropping on the rest. Retention lists include landlines and cell phones, and the connect rate is usually better than a cold list because the number is current. Three lines mainly buys more completed conversations per hour.

Keep voicemail messages general: name, carrier or agency, the renewal date, and a callback number, with no premium figure. Recording feeds the AI summary, and several states require every party to consent before recording, so disclose when you record.

TCPA restrictions on autodialed and prerecorded calls to wireless numbers at 47 CFR 64.1200 apply to the cell numbers on the list, and an existing relationship does not remove them.

Where the AI summaries go

The summary should capture the policy, the premium change, the reason discussed, whether the policyholder shopped, any competitor named, what was applied, and the outcome. “Mentioned shopping again at next renewal” is a forward-looking field that sets up the next cycle, and it is the kind of detail a hurried note loses.

Move the competitor and the reason into the CRM with the outcome. Retention reporting without reasons is just a percentage, and it cannot tell the product team anything.

KPI targets as ranges

Reference points measured in DialBreeze production use (last 90 days to 2026-09-26, three-line sessions, one operator per session): median of about 85 dials per active calling hour, about 600 dials per operator day, and a 17.8 percent person-connect rate. Those are aggregate measured values, not a promise.

For a retention desk:

• Dials per specialist day: 400 to 700 on three lines.
• Retention rate on accounts contacted: tracked by line of business and premium change band.
• Shopped-and-kept share: the number that shows the coverage comparison is working.
• Reason code capture: should be near 100 percent on cancellations.
• Lapse risk accounts recovered: reviewed weekly.
• Disposition completeness: 100 percent, with competitor named on every shop.

One more operating habit belongs in this block: after any cancellation, confirm how the policyholder wants to be contacted going forward. Some of them want nothing, and that instruction has to reach every queue, not just this one. Others want a renewal reminder next cycle, which is a different record than a cancelled policy.

Review the numbers by reason code rather than in aggregate. A retention rate that holds steady while the leading cancellation reason shifts from price to service tells a very different story from a rate that drops because one line of business repriced. The aggregate number hides the shift, and the reporting only becomes useful when cancellation reasons are captured consistently.

State notice rules, discounts and the parts that belong to compliance

Insurance is state-regulated, and three areas belong outside this playbook. First, state insurance regulation and unfair claims practices rules govern how a premium change, a coverage term and a cancellation may be described. Second, nonrenewal and cancellation notice requirements are set by statute and by the policy, and the retention team should not be improvising around them. Third, discounts may only be offered if the carrier offers them and the policyholder qualifies.

On the calling side, keep the suppression list current, honor the calling window and the National DNC Registry, and disclose recording where all-party consent applies. Route product, notice and discount questions to compliance and counsel rather than to a script. This playbook is an operating guide, not legal advice.