Intelligent Claims Automation · Insurance Case Study · Tezo
AI Data Insurance

Claims that decide themselves. Adjusters free for the ones that can’t.

A mid-market P&C carrier was losing its best examiners to routine files it never needed them for. Working with Tezo, it rebuilt claims intake and decisioning so straightforward losses now close on their own, and complex ones reach an adjuster with the file already assembled.

Intelligent Claims Automation 7 min read
INTELLIGENT CLAIMS AUTOMATION · PROPERTY & CASUALTYHow a claim becomes a decisionEVERY CHANNEL A CLAIM ARRIVES FROMCall centre FNOLAgent portalPolicyholder appScanned mailShared email inboxUNIFIED INTAKEClassified · deduplicated · virus-scanned · attached to the right claim number, before a human sees itevery adjuster override returns as labelled training signal1EXTRACTACORD forms, CCC andMitchell estimates, medicalbills, police reports, photosHandwriting and 200-dpiscans treated as first-classPer-field confidence gates2CLASSIFYComplexity, severitytrajectory and fraud signalscored on every claimRouting is a property of theclaim, not of the shift rosterClaimSearch checked at FNOL3DECIDEBusiness-authored rules thatclaims ops can read and editModel adds a scored view withits contributing factors shownAuthority limits are hard rules4REVIEWAdjusters approve, adjust orescalate inside the coreclaims system they already useLow-confidence extractionsescalate rather than enterthe file silently5LEARNOverride rates, decisionvariance and outcome spreadmonitored continuouslyDrift and fair-outcomechecks across protected-class proxiesHUMAN AUTHORISATION · no claim pays without it58% of eligible auto PD closes straight through · 31% of all claim volume, no adjuster touchCORE INSURANCE SYSTEMSClaims · Policy · Billing · CRM · Paymentsunchanged: integrated over published APIs, so any layer above can be rolled backDECISION RECORD · append-onlyinputs · rule version · model version · score · contributing factors · human action · timestampIllustrative engagement scenario. Composite client profile; figures are modelled targets, not measured client results.TEZO
Scroll to explore the full diagram
Workflow illustration: how a claim moves from five arrival channels through extract, classify, decide, review and learn, with human authorisation on every payment and the core systems untouched beneath.
About the client

A carrier whose growth had outpaced its claims operation.

A mid-market property and casualty carrier writing personal auto, homeowners and small commercial across 11 US states, with around $600M in direct written premium and 240,000 claims a year. Its 180 adjusters and examiners worked across two service centres on a mainstream core platform, while loss notices arrived through a call centre, an agent portal, an app, scanned mail and a shared inbox. Nothing in claims had been automated before.

$600M
Direct written premium
240,000
Claims a year
11
US states
180
Adjusters and examiners
The challenge

Where the business stood before the engagement.

01

Every claim arrived as a pile, not a file

Loss notices came through five channels and left the same way: emailed ACORD forms, estimates in two vendor formats, medical bills, phone photos, police reports scanned at 200 dpi. An examiner spent the first half-hour of every claim reconstructing it, and nothing was queryable until someone had typed it in.

02

The same claim got different answers

Two adjusters looking at comparable property-damage losses reached materially different reserve and settlement positions, depending on caseload, tenure and the day of the week. The file recorded what had been decided and never the reasoning behind it, which is a fair-claims-practice exposure as much as an economic one.

03

Expertise was spent where none was needed

A $1,400 windshield claim and a $140,000 bodily-injury claim entered the same queue and competed for the same reviewer. The carrier’s most experienced examiners spent roughly 40% of the week on files requiring no judgement at all, while the files that genuinely needed them waited in line behind those.

04

Fraud signals surfaced too late to matter

Suspicious patterns were caught at reserve review or at the point of payment, weeks after both the money and the goodwill had already moved. SIU received a high volume of undifferentiated referrals with no way to rank one against another, so genuine cases sat in the same pile as the noise around them.

05

The evidence did not exist when regulators asked

Market-conduct exam responses and DOI complaint replies meant reconstructing the decision rationale for a claim from free-text adjuster notes. A single exam response consumed weeks of manual file pulls, and the answer was only ever as good as whatever somebody had thought to write down at the time it was handled.

What we did

Measure first. Automate second.

1

Measured the book before building anything

The first six weeks produced no software. One quarter of closed claims was instrumented and segmented by document mix, severity, channel and touch count, to establish which claims were straight-through eligible and which never would be. About a third qualified, lower than the executive expectation and higher than the adjusters’. Nothing was trained until claims leadership signed it off.

2

Gave five channels one front door

Email, portal uploads, agent submissions, mobile photos and scanned mail were routed into a single intake service that classified, deduplicated, scanned and attached every artefact to the correct claim number before a human saw it. The shared inbox stayed open for six months as a fallback, then closed on evidence that nothing was falling through, rather than on a date.

3

Read every document once, and permanently

Extraction models were trained on the carrier’s actual document set rather than a generic corpus: ACORD loss notices, CCC and Mitchell estimates, medical bills, police reports and handwritten statements. Confidence thresholds were tuned field by field, so a low-confidence value escalated to a person instead of quietly entering the claim file and being trusted downstream.

4

Made triage a property of the claim, not the roster

Every structured claim is now scored on complexity, severity trajectory and fraud signal, with an ISO ClaimSearch check at first notice rather than at reserve review. Routing stopped depending on who was on shift. A claim of a given profile goes to the same queue at the same priority every time, and claims operations can see and change that behaviour without a release.

5

Put the rules in the business’s hands

Settlement recommendations for straightforward claims come from a decision layer where claims operations author and edit the rules themselves, in a format they can read. The model contributes a scored view with its top contributing factors exposed alongside it. Payment authority limits are enforced as hard rules, never as model outputs, so nothing can recommend past its authority.

6

Kept a person on every decision that pays

Adjusters approve, adjust or escalate inside the core claims system they already use, and no claim pays without a human authorisation event. Every override is captured as labelled signal and fed back, which is why accuracy improves rather than plateaus. Each automated decision writes an append-only record: inputs, rule and model version, score, factors, human action, timestamp.

Business outcomes

What the carrier got back.

Quantifiable
3.4 days → under 4 hours
First response on auto property damage
0% → 58%
Eligible auto PD claims closing straight through (31% of total claim volume, no adjuster touch)
41 minutes → 7 minutes
Document handling time per claim
±38% → ±11%
Decision variance on comparable claims
22% → 47%
SIU referrals converting to live investigations
Qualifiable

The queue now sorts itself

Adjusters open the file that actually needed them. Roughly 19% of claims-handling hours moved from routine processing back to complex work, without a change in headcount.

An exam response became a query, not a project

Every automated decision carries its own evidence, so answering a market-conduct request or a DOI complaint starts from a record rather than from a reconstruction.

Technology stack
Microsoft Azure
Cloud platform, orchestration and runtime
Azure AI Document Intelligence
Custom extraction models per document type
Azure OpenAI
FNOL narrative summarisation, grounded and citation-bound
Azure Machine Learning
Severity and complexity model training and serving
Camunda DMN
Business-authored decision rules and authority limits
Microsoft Fabric
Claims analytics and the decision-variance baseline
ISO ClaimSearch
Industry fraud enrichment at first notice of loss
Analytical learnings

What this project changed about how we approach claims work.

01

Straight-through eligibility is smaller than executives assume and larger than adjusters do. Measuring it first turned a contested business case into an agreed one, and it is now the opening phase of every claims engagement we run.

02

Extraction accuracy is a document-set problem before it is a model problem. Generic models performed well on clean forms and failed on the two things that mattered most here: handwritten statements and low-resolution scans.

03

Rules the business can read get used. Rules only engineering can change get worked around. Handing rule authorship to claims operations did more for adoption than any accuracy improvement we shipped.

04

Override data is the compounding asset. The system improves only because every adjuster correction is captured as labelled signal, which means the review interface matters as much as the model.

05

The audit record was scoped as a compliance obligation and turned into the adoption argument. Adjusters trusted recommendations they could interrogate, and stopped trusting the ones they could not.

Start with a conversation, not a commitment.

Tell us where the work is stuck. We will tell you what we would do, what it would realistically take, and whether we are the right partner for it.