Find expiring policies and send renewal notices

Collect expiring policies through the insurers' shared gateway or agency systems, and draft renewal notices showing what changed. Coverage changes are flagged.

  • Insurance agencies
  • Sales
  • Operations & orders

The problem today

Two to three months before expiry, staff sign in to each insurer's agency system, list expiring policies, and draft notices customer by customer. A customer with policies from several insurers has their information split across those systems. When a renewal substantively changes coverage, Japanese rules also require confirming the customer's intent for the changed part.

The workflow in Kitewell

  1. Get policies nearing expiry through the insurers' shared gateway or each insurer's agency systemWeb
  2. Group policies by customer; AI summarizes premium and coverage changes from last yearAI judgment
  3. AI flags policies whose coverage substantively changes as candidates for confirming intentAI judgment
  4. Staff review the notices and the list, and approve sendingApproval
  5. Send the notices and alert staff to customers who have not replied as the deadline nearsAutomatic

What AI does

Groups policies spread across insurers by customer and summarizes what changed from last year. For policies that may need intent confirmation, it shows the changes behind that judgment.

Where people decide

Staff decide whether intent confirmation is needed and what the notice says, and approve before anything is sent.

Features used

What a PoC checks

  • Whether expiring policies can be retrieved through the insurers' shared gateway or each insurer's system
  • Whether your agency agreements and each insurer's system rules allow automated screen operation
  • Whether the change summaries and intent-confirmation flags match your standards

Discuss a PoC for this work

We check whether this workflow runs on your own work and screens.