---
title: "Claims Automation: The Complete Guide to Automating the Claims Lifecycle in 2026"
description: "Claims automation stage by stage: what is genuinely automatable across the eight-stage claims lifecycle from FNOL to recovery, what is not and should not be, and why investigation is the stage where cycle time and leakage both concentrate. The reference for claims leaders evaluating the category."
date: "2026-07-29"
lastModified: "2026-07-29"
author: "Pankaj Dhariwal"
tags: ["Pillar"]
canonical: "https://gethesperai.com/blog/claims-automation-pillar/"
---

# Claims Automation: The Complete Guide to Automating the Claims Lifecycle in 2026

> **TL;DR** Claims automation is the execution of claim work by software and AI agents across all eight lifecycle stages - FNOL and intake, triage and assignment, coverage verification, investigation and evidence, estimation and valuation, settlement and litigation, payment and closure, and recovery - with a licensed human making every decision that is a decision. Seven of the eight stages have a software incumbent. Investigation does not, which is why a claim can move through six automated stages in hours and then sit for 14 or more days waiting on a person. This guide walks every stage, names what automates and what does not, and gives the sequencing, metrics, and vendor map a claims leader needs to evaluate the category.
>
> - Property claim cycle time hit a record 23.9 days in 2024 (J.D. Power); auto, the most automated line, fell to 19.3 days by 2025
> - Claims leakage runs 5-10% of claims paid, and 7-14% on litigated claims (EY)
> - Investigation is the one lifecycle stage with no software incumbent - Hesper closes it in 2-4 hours instead of 14+ days

- **23.9 days** - Average property claim cycle time (A record high - J.D. Power 2024 U.S. Property Claims Satisfaction Study)
- **5-10%** - Claims leakage as a share of claims paid (7-14% on litigated claims (EY))
- **~$15B** - Recoverable subrogation left uncollected each year (NAIC Journal of Insurance Regulation)
- **2-4 hrs** - Investigation time per flagged claim (vs 14+ days manual (Hesper AI))

> **What this guide covers**
>
> A working reference for VPs of Claims, claims operations leaders, and COOs evaluating claims automation as a category. We define the term, walk all eight lifecycle stages with what automates and what does not at each, name the stage where the clock stalls, and give you the sequencing order, the metric set, and the vendor map. It is written to be useful during an evaluation, not during a demo.

## What claims automation actually is

Claims automation is the execution of claim work by software and AI agents across the full lifecycle - intake, triage, coverage analysis, evidence gathering, valuation, settlement, payment, and recovery - with a licensed human making every step that is genuinely a decision. The useful definition is not fewer people. It is that every step which is a lookup, a comparison, a reconciliation, or a document read gets done by a machine in minutes, and every step that is a judgment stays with an adjuster who now has the evidence assembled in front of them instead of spending the week assembling it.

Three things get sold as claims automation and are not. A chatbot at first notice of loss is intake, not automation of the claim. Straight-through processing on the simplest fifth of the book is real and valuable, but it is a rule about which claims to skip, not a capability that works the hard ones. A workflow engine that routes tasks between the same humans doing the same work has automated the routing and nothing else. Each of the three helps. None of them touches the stages where cycle time and loss cost actually accumulate.

It is worth separating three levels, because vendors and carriers use one word for all three. Task automation does one step: extract the fields from an ACORD form. Stage automation owns an entire stage end to end: everything triage does, from severity scoring through assignment. Lifecycle automation runs every stage against one shared evidence record, so nothing is re-keyed and no stage starts by rebuilding context the previous stage already had. Most carriers in 2026 sit at task and stage. The distance between stage automation and lifecycle automation is where the remaining money is, because two automated stages that do not share state still hand off through a human.

For the narrower snapshot of which specific tools are shipping today and which parts of the pipeline still have no vendor, see [insurance claims automation in 2026: what is automated, what is still manual](/blog/insurance-claims-automation-2026-whats-automated/). This guide is the structural version of that map.

## The clock and the ledger

A claim is two things running at once: a clock and a ledger. The clock is cycle time, from the loss until the file closes, and it is what the policyholder experiences. The ledger is loss cost, every dollar that leaves on that claim, and it is what the underwriting result experiences. Almost every claims automation decision is a bet on one of the two. The good ones move both, because the same delays that stretch the clock are usually the same gaps that leak the ledger.

The clock is getting worse in property. The J.D. Power 2024 U.S. Property Claims Satisfaction Study put the average property claim cycle time at 23.9 days, a record high, with catastrophe claims at 34.2 days. That is not a small drift. It is the slowest the industry has been measured at, in the line where a slow claim means a family is not back in their house.

Auto is the counterfactual that proves automation works when it is aimed at the right stage. J.D. Power reported auto repair cycle time peaking at 23.1 days in 2023 and falling to 19.3 days by 2025. Auto is the line where estimating, parts procurement, and payment were automated hardest and earliest. Where the automation landed, the clock moved. Where it did not, it did not.

Cycle time is not a soft metric that only shows up in survey scores. Accenture found that 30% of dissatisfied claimants switched carriers, with 60% citing settlement speed and 45% citing the closing process. A slow claim is a cancelled policy on a delay, and the acquisition cost to replace that policyholder is spent by a different department than the one that caused the delay.

The ledger is quieter and larger. EY puts claims leakage - the gap between what a claim should have cost and what it did - at 5-10% of claims paid annually, rising to 7-14% on litigated claims. On a book paying $500M in losses a year, the midpoint of the all-claims range is roughly $37.5M. That is arithmetic on EY's published range rather than a benchmark for any specific carrier, but it is the right order of magnitude to hold in your head when a claims automation business case is being argued in basis points. For the mechanics of how leakage forms, see [our pillar on claims fraud leakage](/blog/claims-fraud-leakage-pillar/) and the practical version in [reducing claims leakage](/blog/insurance-claims-leakage-reduce-losses/).

Underneath leakage sits fraud. The Coalition Against Insurance Fraud put the cost of insurance fraud in the United States at $308.6 billion a year in its 2022 study. Fraud is not a separate problem from leakage; it is the part of leakage that has intent behind it, and it is the part that requires an investigation rather than an audit to resolve.

> Every carrier can already flag more suspicious claims than it can work. Adding detection raises the number of leads. It does not raise the number of leads that become resolved files. That gap is the whole reason the clock stalls in the middle of an otherwise automated lifecycle.
>
> - Hesper AI product research

The direction of travel is not in dispute. McKinsey's Claims 2030 work projects that more than half of claims activities could be automated by 2030. The question a claims leader has to answer in 2026 is not whether, it is which half, and in what order.

## The eight stages, and what automates at each

The claims lifecycle runs eight stages. Different carriers name them differently and some split or merge a stage, but the work is the same everywhere. The table below is the summary of this entire guide: what is genuinely automatable at each stage in 2026, and what is still a human's job.

| Stage | Automatable in 2026 | Still human |
| --- | --- | --- |
| 1. FNOL and intake | Omnichannel loss capture; extraction from ACORD forms, emails, photos, and voice; claim creation in the core system; duplicate and prior-loss checks; first-pass severity flags | The loss that matches no template, and the claimant who cannot describe what happened |
| 2. Triage and assignment | Severity, complexity, litigation, and fraud scoring in minutes; straight-through routing for clean low-severity claims; assignment by license, line, skill, and workload | Overriding routing on a claim that is legally or reputationally sensitive |
| 3. Coverage verification | Full policy and endorsement analysis against the loss facts; cited coverage position; drafted reservation-of-rights and coverage letters | The coverage decision itself, and ambiguity that turns on jurisdictional case law |
| 4. Investigation and evidence | Records retrieval and summarization, document forensics, statement cross-referencing, timeline reconstruction, OSINT, prior-claims and provider analysis - 15+ phases run in parallel | The fraud determination, the examination under oath, credibility assessment, and the SIU referral signature |
| 5. Estimation and valuation | Damage quantification from photos and documents; supplement adjudication; reserve recommendation; comparison against benchmark severity | Total-loss and complex-structure calls, and anything that needs a physical inspection to resolve |
| 6. Settlement and litigation | Demand-package digestion; benchmarked valuation ranges; drafted responses; early litigation-risk flags | The negotiation, the authority decision, and every strategic call once counsel is involved |
| 7. Payment and closure | Payee verification; payment-anomaly detection before release; closure checklists; file-completeness audit | Releasing payment above authority, and resolving any exception the anomaly check surfaces |
| 8. Recovery | Screening every closed file for subrogation and salvage potential; drafting demands and arbitration filings; tracking statute deadlines | The decision to litigate a recovery, and negotiating with the adverse carrier |

Read the right-hand column carefully. It is short, and almost every entry in it is a decision rather than a task. That is the shape of an honestly automated claims operation: the machine does the work, the human makes the calls, and every call arrives with the evidence already assembled underneath it. Any vendor whose right-hand column is empty is describing a product that does not exist and a regulatory posture that will not hold.

## Stages 1-3: FNOL, triage, and coverage

### Stage 1: FNOL and intake

First notice of loss is the most automated stage in the industry and the one carriers are proudest of, which is exactly why it is worth being precise about what the automation bought. Digital FNOL moved intake from a phone call transcribed by a person into structured data captured at the moment of loss. That matters less because it saved the call and more because everything downstream now starts from clean typed fields instead of free text that each later stage has to re-read.

- Extraction from ACORD forms, adjuster emails, carrier and agent portals, loss photos, and voice transcripts directly into the claim record
- Duplicate-claim and prior-loss checks at first touch, before a file number is assigned
- First-pass severity and complexity flags that determine whether the claim needs a human at all
- Automated acknowledgement and document-request letters, which is where a measurable slice of the cycle-time clock is won or lost in the first 48 hours

What does not automate at intake is the loss nobody modelled. A claim that does not fit a template should be handed to a person immediately rather than forced through one. A good intake automation is measured by how fast and how visibly it escalates, not by how much it swallows.

### Stage 2: Triage and assignment

Triage classifies each claim by severity, complexity, litigation potential, and fraud risk, then routes it - straight through if it is clean and small, to a specific adjuster by license and workload if it is not, to SIU if it scores as suspicious. Carriers have largely solved this. Scoring that took an experienced adjuster twenty minutes of reading now happens in seconds, and the routing rules are auditable. The deep version of this stage is in [the claims triage automation playbook](/blog/claims-triage-automation-guide/).

The failure mode here is specific, common, and expensive: better triage produces more referrals, and the teams receiving those referrals did not grow. A carrier that improves fraud triage without expanding investigation capacity has bought a longer queue, not a lower loss cost. This is the mechanism behind [why most flagged claims are never fully investigated](/blog/why-flagged-insurance-claims-never-investigated/), and it is the single most under-modelled second-order effect in claims automation programs.

### Stage 3: Coverage verification

Coverage verification is the stage where language models changed what is technically possible. A policy with a stack of endorsements is a long document that has to be read against one specific set of loss facts. That is now genuinely automatable: read the form and every endorsement, apply them to the facts on the file, produce a coverage position with each element cited to the clause that governs it, and draft the reservation-of-rights or coverage letter that follows. What used to be a half-day of a senior adjuster's reading is now a first draft in minutes.

What stays human is the decision and the ambiguity. A coverage denial is a regulated act with unfair-claims-practice exposure attached to it, and ambiguity that turns on jurisdictional case law is not a document-reading problem. The correct output of an automated coverage stage is a cited draft position, not a verdict. If a vendor's coverage module issues denials, that is not a feature, it is a liability.

## Stage 4: investigation, the stage with no incumbent

Every other stage in this guide has a software incumbent. Intake has FNOL platforms. Triage has scoring engines. Estimating has CCC, Mitchell, and Solera. Payment has payment rails. Detection has FRISS, Shift Technology, and Verisk. Investigation has no incumbent. At most carriers, in 2026, the answer to what happens after a claim is flagged is still a person, a case file, and 14 or more days.

The arithmetic is unforgiving. A typical carrier runs roughly one investigator per 200+ cases. A manual SIU investigation takes 14 or more days of that investigator's time when it is done properly - records to pull, statements to compare, a timeline to build, a report to write. In Hesper's own benchmarking, that ratio produces a full investigation on roughly 25% of flagged claims. The other 75% are paid, denied, or parked. Not because someone assessed them as clean, but because there was no capacity to find out. The backlog mechanics are in [the claims investigator backlog guide](/blog/claims-investigator-backlog-guide/).

This is why more detection has diminishing returns. Detection answers which claims to look at, and that has not been the constraint for years. FRISS, Shift Technology, and Verisk are good at what they do and they are complementary to an investigation layer rather than substitutes for it. A better score on a claim nobody has capacity to work does not change the outcome of that claim.

The reason investigation resisted automation for so long is that it looks like judgment from the outside. It is not, mostly. An investigation decomposes into discrete phases, most of which are evidence work rather than decision work, and most of which are independent enough to run at the same time:

- Evidence collection - claim documents, medical records, repair estimates, police and fire reports, prior claims through NICB and ISO ClaimSearch
- Document forensics - metadata, compression artifacts, and internal-consistency checks that establish whether a submitted document is what it claims to be
- Statement cross-referencing - comparing every account given by every party against each other and against the physical evidence
- Timeline reconstruction - a single chronology assembled from timestamps across every source, which is where most contradictions surface
- Open-source and public-records research - the publicly available information that confirms or contradicts the claim narrative
- Provider and network analysis - billing patterns, treatment protocols, and the shared addresses, phones, and attorneys that reveal a ring rather than a claim

Hesper runs 15+ of these phases in parallel and completes an investigation in 2-4 hours rather than 14+ days, with every assertion in the final report cited to the specific evidence that produced it. The compression comes from parallelism, not from cutting phases - a human investigator does one thing at a time because a human can only do one thing at a time. The architecture is covered in [parallel processing across investigation phases](/blog/parallel-processing-siu-investigation-phases/) and [AI agent architecture for claims investigation](/blog/ai-agent-architecture-claims-investigation/).

| Flagged-claim coverage: manual SIU vs an investigation layer (Hesper internal benchmark) | Value | Share |
| --- | --- | --- |
| Manual SIU coverage of flagged claims | ~25% | 25% |
| Investigation-layer coverage | 100% | 100% |

What does not automate here is the determination, and it should not. A fraud finding carries a signature, and the person who signs it has to be able to defend it in a deposition, an examination under oath, or a suspicious activity report to a state fraud bureau. An EUO is a live proceeding. Credibility assessment of a person in a room is not an evidence-processing task. The agent assembles the case; the investigator decides it. See [the defensibility standard for fraud investigation AI](/blog/fraud-investigation-ai-defensibility-standard/) and [the general counsel's view](/blog/general-counsel-ai-fraud-investigation-litigation/) for what that signature has to survive.

Investigation is where this platform has unusual depth, and it is deliberately one stage of eight rather than the whole story. A carrier does not buy claims automation to get better fraud investigation; it buys claims automation to close claims faster and cheaper, and discovers that the stage blocking both is the one nobody automated. The full treatment of that stage is [our pillar on autonomous AI claims investigation](/blog/autonomous-ai-claims-investigation-pillar/), with the operational view in [SIU operations](/blog/siu-operations-pillar/) and the detection layer above it in [insurance fraud detection](/blog/insurance-fraud-detection-pillar/).

## Stages 5-7: estimation, settlement, and payment

### Stage 5: Estimation and valuation

Estimating is the second most automated stage after intake, and auto is the proof. Photo-based damage assessment, parts pricing against live catalogs, and supplement adjudication are mature products with real accuracy on high-frequency, low-complexity damage. This is the clearest single explanation for the divergence in the J.D. Power numbers: auto repair cycle time fell from its 23.1-day peak in 2023 to 19.3 days in 2025, while property cycle time went the other way to a record 23.9 days in 2024. Auto got the estimating automation. Property largely did not.

Property estimating is harder for structural reasons rather than technical ones. A vehicle is a catalog of known parts; a house is not. Interior damage is occluded, scope grows once a contractor opens a wall, and the variance between a photo estimate and a physical scope is material. What automates well in property is the first-pass scope, the line-item pricing, supplement review against the original estimate, and reserve recommendation. What does not is the total-loss call, complex structural damage, and anything that needs someone on the roof.

Reserve accuracy is the underrated part of this stage. A reserve set from a first-pass estimate and never revisited is a slow leak into the ledger, and it is the kind of drift that only shows up in a quarterly triangle. Automated reserve recommendation that re-runs whenever new evidence lands on the file is one of the least glamorous and highest-return automations available.

### Stage 6: Settlement and litigation

Settlement is where automation is least mature and most often oversold. The negotiation itself does not automate. What automates is everything that feeds it: digesting a 400-page demand package into the facts that matter, benchmarking the valuation against comparable resolved claims, drafting the response, and flagging litigation risk early enough to change the strategy rather than react to it.

This is disproportionately worth doing because the litigated tail is where the ledger bleeds hardest. EY's 7-14% leakage figure on litigated claims is roughly double its 5-10% all-claims range. Anything that shortens the time between a demand landing and a substantive, well-priced response is working directly on the most expensive part of the book. The corollary is that a demand package sitting unread for three weeks is one of the most expensive queues a carrier operates.

### Stage 7: Payment and closure

Payment is close to solved as a mechanical matter. Digital payment rails settle same-day, and the operational lift of issuing money is no longer a bottleneck anywhere. The remaining automation opportunity in this stage is not speed, it is the check before the money leaves: payee verification against the claim record, anomaly detection on amount, payee, and pattern, and a hold on anything that does not reconcile. A fast payment to the wrong payee is a worse outcome than a slow one.

Closure is the quiet stage and the one most likely to be automated badly. A file that closes without a complete record is a file you cannot defend in an audit and cannot recover on later. Accenture found that 45% of dissatisfied claimants cited the closing process, which makes closure quality a retention issue rather than a file-hygiene one. Automated closure should run a completeness audit - every decision cited, every document filed, every recovery avenue screened - before it marks anything closed. That evidence discipline is the same one described in [generating an audit-ready report](/blog/audit-ready-fraud-report-speed-ai/).

## Stage 8: recovery, the money already lost

Recovery is the most under-automated stage in the lifecycle and the easiest to justify economically, because the dollars in question have already left the building. Subrogation and salvage are the only stage where automation recovers cash rather than avoiding cost, and the finance conversation is correspondingly short.

The NAIC Journal of Insurance Regulation estimates roughly $15 billion in recoverable subrogation dollars go uncollected each year, and that up to 15% of claims close without their recovery potential ever being identified. That second number is the automatable one. Identification is a screening problem, not a legal one: read the loss facts, determine whether a third party contributed, check whether the statute is still open, and flag it before the file closes. See the [subrogation definition](/glossary/subrogation/) for the mechanics.

What automates in recovery is the screen on every closed file, the liability analysis behind a demand, the demand letter itself, arbitration filings, and statute-deadline tracking. What does not automate is the decision to litigate a recovery and the negotiation with the adverse carrier. The reason this stage stays manual at most carriers is not difficulty; it is sequencing. Recovery sits at the end, after the adjuster's attention has moved to the next file, and a screening step that depends on someone remembering to do it is a screening step that does not happen at scale.

## What does not automate, and should not

A claims automation evaluation is more informative when it is run backwards. Instead of asking what a platform can do, ask what it refuses to do and why. Five things should stay human, and a vendor that claims otherwise is either describing a roadmap or misunderstanding the regulatory surface.

1. The coverage decision. A machine can read every endorsement and cite the controlling language. Issuing a denial is a regulated act with unfair-claims-practice exposure, and it belongs to a licensed adjuster.
2. The fraud determination. The finding gets signed, and the signature has to survive a deposition, an EUO, or a referral to a state fraud bureau. The agent builds the case; the investigator concludes it.
3. Negotiation and settlement authority. Authority is delegated to people under a documented framework. Automating the preparation for a negotiation is high value; automating the authority is a governance failure.
4. Anything requiring physical presence. Scene inspections, roof scopes, in-person recorded statements, salvage evaluation on the lot. No amount of model quality substitutes for someone standing there.
5. The exception nobody modelled. Every claims book has a long tail that fits no template. The test of a claims automation program is not how much it handles - it is how fast and how visibly it escalates what it should not.

There is a regulatory floor under all five. The [NAIC Model Bulletin on the Use of Artificial Intelligence Systems by Insurers](https://content.naic.org/insurance-topics/artificial-intelligence), adopted in December 2023 and since taken up by a large share of states, requires insurers to run a written AI systems program covering governance, risk management, and internal audit, and to extend that oversight to third-party AI vendors. The practical effect on claims automation is twofold: a human stays the accountable decision-maker, and the system has to be able to show which input produced which output on any given claim. For the buyer-side version, see the [compliance officer's deployment guide](/blog/compliance-officer-ai-investigation-deployment/) and [how a chief risk officer evaluates claims AI](/blog/chief-risk-officer-ai-claims-investigation/).

## How to sequence a claims automation program

The sequencing mistake is close to universal: carriers automate in the order vendors call on them, which is front to back, because the front of the lifecycle is where the demo is prettiest. Front to back is the wrong order. The right order is stalled stage first, because a lifecycle moves at the speed of its slowest stage regardless of how fast the others got.

1. Instrument before you automate. Measure cycle time stage by stage, not end to end. A single end-to-end average tells you nothing about which stage owns the days inside it. You cannot prioritize what you have not decomposed.
2. Fix the stalled stage, not the loudest one. If intake takes four hours and investigation takes 14 days, another hour off intake is noise. Rank stages by days contributed, not by how often people complain about them.
3. Automate the handoffs, not just the stages. Two automated stages that do not share state produce re-keying, and re-keying is where both time and errors reappear. Handoff automation is usually cheaper than stage automation and returns more.
4. Keep one evidence spine. Every stage should write to a single evidence record with source, timestamp, and provenance. This is what makes the audit trail a byproduct rather than a reconstruction project, and it is the only version that survives a DOI exam.
5. Put the human in the decision, not the workflow. If your target operating model still has adjusters approving routine routing steps, you automated the work and kept the clicking. Escalate exceptions to people; do not make people the transport layer.
6. Prove it on one line before scaling. Pick the line where the stalled stage hurts most, run it for a quarter against a measured baseline, and expand on evidence. Most AI claims programs stall in change management rather than model quality.

The change-management half of this is at least as hard as the technical half. The people-side playbook is in [the claims operations manager guide to AI-augmented investigation](/blog/claims-operations-manager-ai-transition/), the budget and timeline version is in [the Claims VP deployment playbook](/blog/claims-vp-deploying-ai-investigation-playbook/), and the finance case is in [the CFO ROI memo](/blog/cfo-roi-memo-ai-claims-investigation/). If you are trying to work out who at the carrier actually decides, see [the buying center map](/blog/buying-center-mapping-ai-investigation/).

## The metrics that prove it worked

Most claims automation programs are measured on the metrics that are easy to move rather than the ones that matter. The set below is chosen so that each metric is hard to game and each one fails loudly when the automation is doing something cosmetic.

| Metric | What it measures | Why this one |
| --- | --- | --- |
| Cycle time by stage | Days from stage entry to stage exit, per stage | End-to-end cycle time hides which stage is actually stalled |
| Touch count per claim | How many times a human opens the file | The cleanest proxy for whether work was removed or merely moved |
| Straight-through rate by severity band | Share resolved with no human touch, split by severity | An unsegmented STP rate is gamed by counting easy claims |
| Flagged-claim coverage | Share of flagged or referred claims that get a complete investigation | The one number that separates detection spend from resolution capability |
| Leakage rate | Overpayment as a share of claims paid, from audit sampling | The ledger. EY benchmarks 5-10% all-claims and 7-14% litigated |
| Recovery identification rate | Share of closed files screened for subrogation and salvage | NAIC estimates up to 15% of claims close with recovery potential unidentified |
| Reopen rate | Share of closed claims reopened within 12 months | Catches automation that hit its cycle-time target by closing files badly |
| Audit defensibility | Share of decisions with a complete, cited evidence trail | What a DOI exam, a reinsurer, or opposing counsel actually samples |

Two of these deserve emphasis because they are the ones carriers most often do not track. Flagged-claim coverage is the difference between buying detection and buying resolution, and a carrier that cannot state its coverage percentage does not know what its detection spend is producing. Reopen rate is the honesty check on everything else: it is trivially easy to improve cycle time by closing files prematurely, and reopen rate is the metric that catches it a quarter later. The fuller metric treatment is in [SIU KPIs for 2026](/blog/siu-kpis-what-to-track-2026/) and [how to measure AI ROI in claims](/blog/measuring-fraud-investigation-ai-roi/).

## Where the vendors actually sit

Claims automation is sold as one category and bought as at least five. The vendors overlap far less than the shared label suggests, and most evaluation confusion comes from comparing products that occupy different stages.

- Core claims systems - Guidewire, Duck Creek, Majesco, Snapsheet. System of record and workflow across all eight stages, deep in none of them. Their AI modules are stage features on top of a platform decision you already made.
- Estimating and repair networks - CCC, Mitchell/Enlyte, Solera. Stage 5, overwhelmingly in auto, and genuinely excellent at it. Not investigation, not coverage, not recovery.
- Detection platforms - FRISS, Shift Technology, Verisk. Scoring and matching that feeds stages 2 and 4. They tell you which claims deserve attention. They do not work the claim.
- Document AI - Ocrolus, Hyperscience, ABBYY. Extraction and classification that feeds every stage. Reading a document is not adjudicating it.
- Investigation and resolution - Hesper AI. Stage 4 at depth, wired into the stages on either side of it.

Hesper AI is the claims resolution platform: agents that run the lifecycle from first notice to final recovery, with a full investigation engine inside stage 4 rather than a referral out of it. Detection is built in, so it runs standalone or downstream of FRISS, Shift Technology, or Verisk - all three remain complementary. The distinguishing claim is not that it touches more stages than a core system does. It is that the one stage every other vendor routes around is the one it is built to finish. For the platform comparisons, see [claims management systems compared](/blog/claims-management-systems-comparison/), [AI fraud platforms compared](/blog/ai-fraud-platforms-compared-2026-pillar/), and [the hidden integration costs of legacy claims AI modules](/blog/hidden-integration-costs-legacy-claims-ai/).

## Key takeaways

- Claims automation means software and AI agents executing the work across all eight lifecycle stages, with a licensed human making every step that is genuinely a decision.
- A claim is a clock and a ledger. Property cycle time hit a record 23.9 days in 2024 (J.D. Power); leakage runs 5-10% of claims paid, 7-14% litigated (EY).
- Auto proves automation works where it is applied: repair cycle time fell from a 23.1-day peak in 2023 to 19.3 days in 2025 (J.D. Power), while property went the other way.
- Seven of eight stages have a software incumbent. Investigation does not, which is why an otherwise automated lifecycle still stalls for 14+ days on a flagged claim.
- Hesper runs 15+ investigation phases in parallel and finishes in 2-4 hours, lifting flagged-claim coverage from roughly 25% to 100%.
- Recovery is the cheapest stage to justify: the NAIC estimates ~$15B in recoverable subrogation goes uncollected annually, with up to 15% of claims closing without recovery potential identified.
- Sequence by stalled stage, not front to back, and measure cycle time by stage, touch count, flagged-claim coverage, leakage, and reopen rate.

## Frequently asked questions

### What is claims automation?

Claims automation is the use of software and AI agents to execute claim work across the full lifecycle - FNOL and intake, triage and assignment, coverage verification, investigation and evidence, estimation and valuation, settlement and litigation, payment and closure, and recovery - while a licensed human makes every step that is genuinely a decision. It is broader than straight-through processing, which is a rule about which simple claims to skip rather than a capability that works the hard ones.

### Which stages of the claims lifecycle are already automated in 2026?

Intake, triage, coverage verification, estimating, and payment all have mature software incumbents and are automated at most large carriers. Settlement is partially automated on the preparation side but not the negotiation. Recovery is under-automated relative to how easy it is to justify. Investigation of flagged claims is the one stage with no software incumbent at most carriers, which is why it is still measured in weeks.

### Does claims automation reduce headcount?

It changes what the headcount does more than it reduces it. Every step that is a lookup, comparison, reconciliation, or document read moves to software; every step that is a decision stays with a person who now has the evidence assembled instead of spending the week assembling it. In practice most carriers redeploy capacity toward the work they previously could not reach - the 75% of flagged claims that never got a full investigation, and the closed files that were never screened for recovery.

### How much does slow claims handling actually cost?

Two ways. On retention, Accenture found 30% of dissatisfied claimants switched carriers, with 60% citing settlement speed and 45% citing the closing process. On loss cost, EY puts claims leakage at 5-10% of claims paid annually and 7-14% on litigated claims, and delay is one of the mechanisms that produces it - unread demand packages, stale reserves, and files closed without a recovery screen.

### What is the difference between claims automation and fraud detection?

Fraud detection is one input into two stages of the lifecycle: it scores claims at triage and identifies which ones deserve investigation. Claims automation is the execution of the whole lifecycle. A carrier can have excellent detection and a completely stalled claims operation, because detection tells you which claims to look at and has never been the constraint on how many you can actually work.

### Why is investigation the hardest stage to automate?

It looks like judgment from the outside, so it was left alone. Most of it is not. An investigation decomposes into discrete evidence phases - records retrieval, document forensics, statement cross-referencing, timeline reconstruction, public-records research, provider and network analysis - and most of those phases are independent enough to run simultaneously. Running them in parallel is what compresses a 14-day investigation into 2-4 hours. The determination at the end stays with the investigator.

### In what order should a carrier automate the claims lifecycle?

Stalled stage first, not front to back. Instrument cycle time stage by stage so you know which stage owns the days, then fix the stage contributing the most days rather than the one people complain about most. Automate the handoffs between stages as well as the stages themselves, keep one shared evidence record so the audit trail is a byproduct, and prove the change on one line of business against a measured baseline before scaling.

### Can AI make claim decisions on its own?

It should not, and the regulatory environment assumes it will not. The NAIC Model Bulletin on the Use of Artificial Intelligence Systems by Insurers, adopted in December 2023, requires insurers to maintain a written AI systems program covering governance, risk management, and internal audit, and to extend that oversight to third-party vendors. In practice this means a human remains the accountable decision-maker on coverage decisions, fraud determinations, and settlement authority, and the system has to be able to show which input produced which output on any given claim.