All use cases

Retain / Save

Policy auto-renewal and lapse save

The renewal letter with the higher premium is the moment a policyholder decides to shop around. The agent has the conversation before the price shock turns into a lapse.

Get aheadTime-based triggerRisk triggerSystem triggerEmailPushChatSMSVoiceInsurance

What it does

Renewal is the single highest-value retention moment in insurance, and most insurers handle it with a notice that lands two months out, explains a premium increase in fine print, and goes unread. The policyholder sees a number that went up, assumes the market has a better deal, and either lets the policy lapse or quietly moves it at renewal. The agent turns that window into a renewal-review conversation: it opens 60 to 90 days ahead, explains what changed and why, re-shops the available coverage options against the current cover, and works through the objection before the renewal date passes. The save happens while there is still time to keep the policy, not in a win-back campaign after the cover has gone.

How it works

  1. 1
    Trigger. the renewal window opens 60 to 90 days before the policy's auto-renewal date, or a renewal notice is issued and goes unopened, or a lapse-risk flag fires on the renewing policy.
  2. 2
    Decision. the agent reads the policyholder's memory — the premium change versus last term, claims experience, coverage held, prior objections, payment-method health — and decides whether this is a quiet confirmation, a premium-explanation conversation, or a re-shop that needs a different option or a human adviser.
  3. 3
    Action. it opens a personal renewal conversation on the channel the policyholder answers (email, push, chat, SMS, or voice for high-value policies): the premium change explained in plain language, the coverage options that fit, and a clear path to renew inside the insurer's own policy admin flow.
  4. 4
    Follow-through. objections and outcomes are written back to memory and the CRM; a renewing policy that stays silent gets one judged follow-up, not a drip; complex suitability questions or contested renewals escalate to a licensed adviser with the full picture. If the policyholder renews on their own, queued outreach is cancelled.
Example
AgentYour auto policy renews in about two months, and the premium has gone up from last year. The main driver is a rise in repair costs across your area, not anything on your record. Before it renews, want me to walk you through the options that could hold the price closer to where it was?
CustomerYeah, that increase is why I was about to get quotes elsewhere.
AgentUnderstood. Keeping your current cover, raising the voluntary excess slightly brings the premium back down — here's the comparison side by side. If it works, I'll take you to your insurer's renewal screen to confirm it; nothing changes until you approve it there.

Configuration

How the agent is wired for this use case.

Triggera renewal_window_open event from the policy admin system at 60 to 90 days before the auto-renewal date (or renewal_notice_unopened / a lapse-risk flag), routed to the agent with the policy reference.
Tools & actions
  • Policy admin system · read renewal terms, the prior-term premium, and coverage held; stage the renewal or an amended option for the policyholder to approve
  • Rating / quoting service · pull alternative coverage and excess options with their premium impact for the re-shop
  • CRM · read claims experience and prior objections; log the renewal conversation and its outcome
  • Customer memory · read tenure and past renewal behavior; write back objections and the result
  • Messaging channel · open the renewal-review conversation and render the premium comparison
Autonomymessage selection, the premium explanation, and the option comparison run unattended under judge gating; the renewal or any coverage change is confirmation-gated and binds only in the insurer's policy admin flow. Suitability-sensitive re-shopping follows a regulated-advice policy class — the agent explains and guides, it never binds a policy or gives advice beyond its scope.
Channelsemail · push · chat · sms · voice
Escalationa contested premium, a complaint, or a suitability question beyond the agent's scope hands off to a licensed adviser with the full renewal context attached.

What you need

The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.

Signals

renewal and auto-renewal dates, the 60-to-90-day window event, renewal_notice_unopened, premium-change-at-renewal, lapse-risk flags

Data

prior-term premium and the renewal premium, coverage held, claims history, customer memory of past objections and tenure, payment-method status, channel consent

Guardrails

judge gating on every unprompted message; one follow-up cap on silence; regulated renewal-notice and communications rules respected; suitability and advice-boundary policy — no binding or coverage change by the agent; the insurer keeps owning both the policy admin step and the send channels; cancellation of stale outreach once the renewal completes

Metrics it moves

  • renewal-rateup, by explaining the premium change and re-shopping inside the window instead of letting the notice go unread
  • churndown, as policyholders who would have shopped the policy away at the price shock renew on a fitting option
  • save-rateup, on renewing policies that entered the window flagged at lapse risk

Related use cases

Retain / Save

Renewal-window save

the cross-industry parent; this is the 60-to-90-day insurance variant

Retain / Save

Policy-lapse-risk early-warning save

catches lapse risk before the renewal window opens

Upsell & Cross-sell

Coverage upgrade and add-on cross-sell

right-sizing cover at the same signal moments

See it on your own customer journey

Bring one drop-off, one churn cliff, or one silent segment. We will show you what a proactive agent with memory and judgment does with it.

Book a demo