All use cases

Retain / Save

Premium-lapse grace and reinstatement save

A premium went unpaid and the policy is in its grace period. Quietly, cover is running out — and most policyholders don't realise the clock is ticking.

Get aheadTime-based triggerRisk triggerSystem triggerSMSEmailVoiceChatInsurance

What it does

When an insurance premium is missed, the policy doesn't lapse at once: it enters a grace period, and then a reinstatement window with its own rules and deadlines. Most policyholders never see the notice, assume the direct debit went through, and only discover the gap when they try to claim against cover that has quietly expired. The cost of doing nothing is a lapsed policy, lost renewal premium, and a customer who has to re-underwrite to come back. The agent treats the missed premium as the start of a conversation it opens itself: it states the reinstatement window, the exact amount due to keep cover continuous, and a compliant path to pay — inside the dunning rules that govern regulated insurance communications.

How it works

  1. 1
    Trigger. a premium payment fails or a grace-period clock starts on the policy admin system, with the policy type and the lapse and reinstatement deadlines attached.
  2. 2
    Decision. the agent reads the policy — product, premium, grace and reinstatement dates, payment method, and any prior lapse history — and checks the state-specific reinstatement rules and the required regulatory disclosures before composing anything. A judge gates the message for tone, accuracy, and policy before it goes.
  3. 3
    Action. it reaches out on the policyholder's preferred channel, leads with what is at stake (cover lapses on this date), states the exact amount to keep the policy in force, and routes to a compliant payment step. Money never moves inside the conversation: the agent hands off to the client's secure payment page and confirms once cover is restored.
  4. 4
    Follow-through. the outcome writes back to the policy admin system and CRM; if the lapse moves toward the end of the reinstatement window, the case escalates to a licensed agent before cover is lost. If the policyholder pays on their own first, the queued outreach is cancelled, and saves are measured against a holdout.
Example
AgentYour auto premium due on the 3rd didn't go through, so your policy is in its grace period and cover ends on the 18th. To keep it continuous, the amount due is the missed premium only — no re-application. Here's a secure link to pay, and I'll confirm the moment cover is back in force.
CustomerThe card on file expired. Can I just pay now?
AgentYes — that link takes a new card and settles the missed premium. Once it clears I'll send written confirmation that your cover never lapsed.

Configuration

How the agent is wired for this use case.

Triggera premium_payment_failed event or a grace-period-start flag from the policy admin / billing system, carrying the policy type, lapse date, and reinstatement deadline.
Tools & actions
  • Policy admin system · read policy status, premium, grace and reinstatement dates, and lapse history; write back the reinstatement outcome.
  • Billing platform · confirm the missed-premium amount and the mandate state; record the settled payment.
  • Payment provider · generate the secure hosted payment link; the agent never handles card data.
  • Compliance / disclosures library · pull the state-specific reinstatement terms and the required regulatory wording for the message.
  • Messaging channel · run the grace-period outreach on the policyholder's channel of record.
  • CRM · log the contact, disclosure, and resolution for the audit trail.
Autonomythe outreach runs unattended behind the judge inside the regulated dunning policy; any payment is a money-moving step handled only through the secure hand-off, never inside the conversation; reinstatement that needs underwriting sign-off is routed to a licensed agent.
Channelssms · email · voice · chat
Escalationa lapse nearing the end of the reinstatement window, a policy that requires re-underwriting to reinstate, or any dispute over cover hands off to a licensed agent.

What you need

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

Signals

premium_payment_failed, grace-period-start and reinstatement-deadline events, self-cure payment events (for cancellation of stale outreach).

Data

policy type and status, premium and amount due, grace and reinstatement dates, payment method and mandate state, lapse history, channel consent, customer memory.

Guardrails

regulated dunning rules encoded as policy — contact windows, frequency caps, and required disclosures; state-by-state reinstatement terms; secure payment hand-off only, no card data in the conversation; judge gating on every outbound message; human handoff before cover is irrecoverably lost; holdout assignment for honest save measurement.

Metrics it moves

  • involuntary-churndown: the premium is repaired during the grace window before the policy lapses for non-payment.
  • renewal-rateup: a policy kept continuous through a missed payment is a policy that reaches its renewal instead of dropping off the book.
  • save-rateup, measured against a holdout so reinstatements that would have happened anyway are not counted.

Related use cases

Collect / Recover

Insurance premium payment recovery

the collect-side counterpart that repairs the payment method and re-bills

Retain / Save

Policy-lapse-risk early-warning save

the upstream layer that acts before any premium is missed

Collect / Recover

Failed-payment instant recovery

the subscription/fintech retry pattern this insurance variant specialises

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