Case Study · Property & Casualty Insurance

Automating Claims Intake and Triage for Lakeshore Mutual Insurance's 300,000 Policyholders

How Kawach Technology automated claims intake and fraud detection for Lakeshore Mutual Insurance, cutting response time from 7 days to 4 hours.

Read the Case Study
Share this case study
Lakeshore Mutual Insurance
Automating Claims Intake and Triage for Lakeshore Mutual Insurance's 300,000 Policyholders
Client
Lakeshore Mutual Insurance
Industry
Property & Casualty Insurance
Location
Chicago, Illinois, USA
Duration
10 months
7 days → 4 hrsInitial Response Time
76%Digital Filing Adoption
+3.2xSuspected Fraud Caught Pre-Payout
-38%Call Center Volume
01

Executive Summary

How Kawach Technology automated claims intake and fraud detection for Lakeshore Mutual Insurance, cutting response time from 7 days to 4 hours.

Key outcomes
  • 7 days → 4 hrs initial response time
  • 76% digital filing adoption
  • +3.2x suspected fraud caught pre-payout
  • -38% call center volume

Project fact sheet

ClientLakeshore Mutual Insurance
IndustryProperty & Casualty Insurance
LocationChicago, Illinois, USA · Software development in the USA
Business sizeRegional insurer, 300,000+ policyholders
Business modelProperty & Casualty Insurance
Project duration10 months
Core technologyJava, Spring Boot, PostgreSQL, Python (ML), React, AWS
02

The Challenge

Lakeshore Mutual Insurance serves more than 300,000 policyholders across the Midwest, but filing a claim in 2024 still meant picking up the phone, sending a fax, or mailing in paperwork — there was no digital self-service option at all. Every claim that came in was manually triaged and assigned to an adjuster by a claims coordinator working through a queue, which alone added days before anyone had actually reviewed the claim's substance.

Policyholders routinely waited over a week just to hear back after filing, which is a genuinely difficult experience when the claim in question is often about something stressful — storm damage to a home, a car accident, a burst pipe. Meanwhile, fraud detection relied entirely on adjuster intuition built from experience and after-the-fact audits; there was no systematic way to flag a suspicious claim pattern before the payout had already gone out.

Every status inquiry required a phone call, which meant the call center absorbed a steady stream of "what's happening with my claim" calls that a self-service system could have handled instantly — straining call center capacity and making policyholders wait even to ask a simple question.

Key problems identified

#Problem
01Claims could only be filed by phone, fax, or mail, with no digital self-service option.
02Every claim was manually triaged and assigned to an adjuster, adding days before any actual review began.
03Policyholders often waited over a week just to hear back after filing a claim.
04Fraud detection relied entirely on adjuster intuition and after-the-fact audits, with no systematic flagging.
05Claims status updates required policyholders to call in, adding to already-strained call center volume.
03

Goals & Objectives

ObjectiveWhat success meant
Enable Digital Claims Filing
Give policyholders a fast, self-service way to file a claim.
Automate Triage & Assignment
Route claims to the right adjuster automatically based on type and complexity.
Flag Potential Fraud Earlier
Catch suspicious claim patterns before payout, not after.
Reduce Call Center Load
Let policyholders self-serve claim status instead of calling in.
04

The Solution

We built a digital claims intake portal as the front door to everything else — policyholders can now file a claim online or via mobile in minutes, uploading photos and documentation directly rather than mailing them in. That structured digital intake is what made automated triage possible in the first place: the system now routes each claim to the right adjuster based on claim type, complexity, and current workload, work that used to require a human coordinator manually reading every submission.

Fraud detection was the piece Lakeshore's claims leadership was most cautious about, understandably — false positives that delay a legitimate claim create real harm. We trained a machine-learning model on Lakeshore's own historical claims data, looking for the patterns that had actually preceded confirmed fraud in the past rather than generic industry heuristics, and we ran it in parallel with the claims team's normal process for an extended validation period before it influenced any live triage decision.

Self-service status tracking closed the loop on the call-center problem: policyholders can now check exactly where their claim stands without calling in, which took a meaningful chunk of routine inquiry volume off the phone lines. We rolled the new system out by claim type rather than all at once — starting with simpler, lower-complexity claim categories where automated triage had the clearest track record, before extending to more complex claim types once the team had built confidence in the system's judgment.

Modules delivered

ModulePurpose
Digital Claims Intake Portal
Online and mobile claims filing with direct photo and document upload.
Automated Triage Engine
Routes claims to the right adjuster based on type, complexity, and workload.
ML Fraud Flagging
A model trained on Lakeshore's own historical claims data to flag suspicious patterns pre-payout.
Adjuster Assignment & Workload Balancing
Balances new claims across adjusters based on current caseload.
Self-Service Status Tracking
Policyholders check claim status anytime without calling in.
Document & Photo Upload
Direct upload of claim evidence from any device.
05

Key Features

Digital Claims Portal

File a claim online or via mobile in minutes.

Automated Triage

Claims routed to the right adjuster automatically.

ML Fraud Detection

Suspicious patterns flagged before payout.

Self-Service Status Tracking

Check claim status anytime without calling in.

Adjuster Workload Balancing

New claims distributed based on current caseload.

Mobile Photo/Document Upload

Submit claim evidence directly from any device.

06

Technology Stack

LayerTechnologies
Backend
Java Spring Boot PostgreSQL
Fraud Detection
Python scikit-learn
Frontend
React mobile-responsive
Infrastructure
AWS encrypted claims storage
07

Delivery Process

Total timeline 10 months
  1. 1

    Claims Workflow Discovery

    Mapped the full claims lifecycle from filing through payout across claim types.

  2. 2

    Digital Intake Portal Design

    Built the online/mobile filing flow with direct evidence upload.

  3. 3

    Triage & Assignment Automation

    Automated adjuster routing based on claim type, complexity, and workload.

  4. 4

    Fraud Model Training

    Trained the fraud detection model on Lakeshore's own historical claims data.

  5. 5

    Parallel-Run Validation

    Ran automated triage and fraud flagging alongside the existing claims team process before trusting live decisions to it.

  6. 6

    Phased Rollout by Claim Type

    Launched with simpler claim categories first, expanding to more complex types as confidence grew.

08

Security & Compliance

MeasureHow it was handled
State Insurance Regulatory Compliance
Claims workflows align with Illinois and multi-state insurance regulatory requirements.
Claims Data Encryption
All claims data, including uploaded evidence, is encrypted at rest and in transit.
Fair Claims Practices Compliance
Automated triage and fraud flagging were designed to align with fair claims handling regulations.
09

Results & Impact

Results reported for this project after launch.

7 days → 4 hrsInitial Response Time
76%Digital Filing Adoption
+3.2xSuspected Fraud Caught Pre-Payout
-38%Call Center Volume

Before vs. after

BeforeAfter
Phone/fax/mail-only claims filing Digital self-service filing portal
Manual multi-day triage Automated triage and adjuster assignment
Fraud caught only after payout, if at all ML flagging before payout
Policyholders called in for status updates Self-service status tracking
10

Client Feedback

A week-long wait just to hear back on a claim is a terrible experience for someone dealing with storm damage or a car accident. Cutting that to about four hours changed how our policyholders feel about us at the exact moment it matters most. And the fraud model catching more than three times what we caught manually, without slowing down legitimate claims, is the kind of result that's easy to sell internally.
PA
Patrick O'MalleyVP of Claims Operations, Lakeshore Mutual Insurance
11

Key Achievements

  • Response Time Cut from a Week to Hours

    Initial claims response time dropped from about 7 days to roughly 4 hours.

  • 76% Digital Filing Adoption

    More than three-quarters of policyholders now file claims digitally rather than by phone, fax, or mail.

  • Fraud Detection More Than Tripled

    Suspected fraud caught before payout increased 3.2x compared to the prior manual-only process.

12

Frequently Asked Questions

How do you avoid false positives delaying legitimate claims?

We ran the fraud model in parallel with the claims team's normal process for an extended period, comparing its flags against real outcomes, before letting it influence any live triage decision — and it flags for adjuster review rather than auto-denying anything.

Are adjusters being replaced by the automated system?

No. The system handles triage and routing so adjusters spend their time on actual claim assessment rather than administrative sorting — every claim is still reviewed by a human adjuster.

How does the platform stay compliant across different state insurance regulations?

Claims workflows were built with Lakeshore's compliance team to align with Illinois and neighboring-state insurance regulatory requirements, including fair claims handling rules.

Why was rollout phased by claim type instead of all at once?

Starting with simpler, lower-complexity claims let the team validate the automated triage and fraud flagging track record before extending it to more complex, higher-stakes claim types.

Planning a Similar Property & Casualty Insurance Project?

Tell us what you're building, what you're trying to improve, or where your current software is falling short.

Know someone this would help? Share it