All use cases

Collect / Recover

Pre-lapse premium reminder and mandate update

The premium run that fails next month doesn't have to. The agent sees the expiring card or lapsing mandate today and gets it fixed before the policy is ever at risk.

Get aheadTime-based triggerSystem triggerRisk triggerSMSEmailPushChatInsurance

What it does

Most lapsed cover starts as a payment that quietly stops working: a card that expires before the next premium run, a direct-debit mandate that gets cancelled when a customer switches bank, a renewal premium that increases past the limit on the card on file. By the time a failed-premium notice goes out, the policy is already days from lapsing and the customer often won't notice until they try to claim. The agent works upstream of that failure: it flags the upcoming premium and the payment method behind it, gets the card or mandate updated through a secure link, and confirms the method is good for the next run, so cover stays continuous before the recovery and grace-period machinery is ever needed.

How it works

  1. 1
    Trigger. a time or risk signal on the policy: a card expiring before the next premium date, a mandate flagged as lapsed or cancelled, an upcoming premium increase that exceeds the method on file, or a payment-risk score crossing its threshold.
  2. 2
    Decision. the agent reads the policy state, the premium schedule, and how the customer usually pays and responds, then weighs whether a reminder is genuinely useful here or just noise. It frames the touch around keeping cover in force, not chasing money, and a quality judge gates the message before it goes.
  3. 3
    Action. a short, specific reminder on the policyholder's preferred channel, carrying a secure link to the insurer's hosted page to update the card or re-authorise the direct-debit mandate. Card details never pass through the conversation; the agent only confirms the method is in place for the next run.
  4. 4
    Follow-through. a completed update writes back to the policy record and cancels any pending reminders for that cycle. If the premium then runs cleanly, the loop closes silently. If it fails anyway, the full context hands off to premium-recovery so the policyholder never has to re-explain.
Example
AgentQuick heads-up about your motor policy: the card we use for your premium expires before next month's payment. Updating it takes a moment through this secure link, and your cover continues with no interruption.
CustomerDone. I've actually just changed banks, can I switch this to a direct debit from the new account?
AgentYes, the same page lets you set up the new mandate. Authorise it there and it applies from next month's premium, so your cover stays in force without another reminder from me.

Configuration

How the agent is wired for this use case.

Triggera time / risk event on the policy — card_expiring before the next premium date, mandate_lapsed, an upcoming premium-increase flag, or a payment-risk score — emitted by the policy-admin or billing system.
Tools & actions
  • Policy admin system · read policy state, premium schedule, and the next run date; write back the confirmed payment method.
  • Billing platform · check the method on file against the upcoming premium amount and flag a shortfall or expiry.
  • Payment provider · hand off to the insurer's secure hosted page to update the card or re-authorise the direct-debit mandate (the agent never touches card data).
  • Messaging channel · send the judgment-timed reminder on the policyholder's preferred channel and confirm the method is good for the next run.
  • CRM / audit log · record the reminder and the mandate change for the regulated trail.
Autonomythe reminder and the diagnosis run unattended under judge gating; updating the card or mandate completes only on the insurer's secure hosted step, so no money-moving action and no card data ever sit inside the conversation.
Channelssms · email · push · chat
Escalationa method that can't be repaired before the premium date, a disputed premium increase, or a request to change cover hands off to a human servicing or retention specialist.

What you need

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

Signals

card-expiry dates ahead of the premium run, mandate-lapse flags, upcoming premium-increase events, payment-risk scores.

Data

policy and cover state, premium schedule and amount, payment-method metadata (expiry, type, mandate status), consent and channel preferences, customer memory.

Guardrails

secure payment hand-off only, no card or mandate data in any conversation; regulated contact windows and frequency caps on reminders; reminder cancellation once the method is updated or the premium clears; the agent confirms the payment method only and gives no advice on the cover itself; judge gating on every unprompted message.

Metrics it moves

  • involuntary-churndown: the lapse is prevented upstream, so the failed-premium and grace-period funnel never has to fire.
  • renewal-rateup: a policy whose premium keeps clearing on schedule reaches its renewal in force rather than already lapsed.
  • contact-ratedown: confirming a healthy mandate before the run removes a whole class of failed-payment and reinstatement conversations later.

Related use cases

Collect / Recover

Insurance premium payment recovery

the downstream rescue when the premium fails despite the reminder

Retain / Save

Premium-lapse grace and reinstatement save

the retain-side flow once a policy is already in its grace window

Collect / Recover

Pre-dunning card update

the subscription and fintech parent of this upstream pattern

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