How AI Automates FNOL (First Notice of Loss)

When a policyholder reports a loss, the clock starts. The first notice of loss, or FNOL, is the moment a claim enters the insurer's world: a phone call, an email, a broker's spreadsheet, a photo of a damaged truck. It is also where most of the friction in claims begins, because that first report almost never arrives in the clean, structured form a claims system expects. Someone has to read it, make sense of it, check it, and decide where it goes. For decades that someone has been a person, and the queue behind them is where cycle time, leakage, and customer frustration accumulate.

AI changes what happens in those first minutes. This article explains what FNOL automation actually does, where an external AI layer fits, and, just as important, what it does not touch. WIR is not a claims administrator and does not settle claims. What it offers is an architectural approach: structure and route the incoming report before it reaches the core, so the system of record receives a clean, validated, auditable claim instead of raw text.

What FNOL is, and why it is the bottleneck

FNOL is the first structured record that a loss has occurred. In practice the raw input is anything but structured. A claimant describes an accident in their own words. A broker forwards a PDF. A driver sends photos and a transcribed voice note. A form is half filled. The claims core, whether it is Guidewire ClaimCenter or an insurer's own platform, needs specific fields populated correctly before it can open a claim, set a reserve, and route the file. Bridging that gap is manual work, and manual work at intake is slow, inconsistent, and easy to get wrong.

The cost of getting it wrong at FNOL is not evenly distributed. A miskeyed coverage code, a missed severity signal, or a claim sent to the wrong queue does not stay a small error. It compounds downstream into a longer cycle, a mis-set reserve, or leakage that is only discovered after payment. FNOL is the cheapest place in the claims lifecycle to get the data right, and the most expensive place to get it wrong.

How AI automates the first notice of loss

FNOL automation is a sequence, not a single model. An external AI layer works through it in order:

• Capture across channels. The report arrives however the claimant sends it: email, portal, broker submission, document, image, or transcribed voice. The layer ingests all of it rather than forcing one channel.
• Structure the unstructured. Language models read free text and documents and extract the fields the claim actually needs: what was lost, when, where, policy reference, parties involved, severity signals. This is the same reading problem that submission intake solves on the underwriting side, applied to the claims report.
• Validate. The extracted data is checked against the policy: is coverage in force, does the loss date fall inside the term, do the parties reconcile. Gaps and contradictions are flagged rather than silently passed through.
• Triage and route. The claim is scored for complexity and severity and sent to the right path: a simple, low-severity claim toward straight-through handling, a complex or suspicious one to an experienced adjuster. Triage at intake is where cycle time is won or lost.
• Surface fraud signals early. The same enriched record can carry an early fraud indicator, so a suspicious loss is flagged at first notice rather than after payment. This is the claims-side companion to fraud detection at underwriting.

The output is a clean, validated, routed claim with an audit trail, handed to the core to open.

The external-layer principle: structure and route before it reaches the core

The design rule that makes this safe is the same one WIR applies everywhere: the AI never becomes the system of record. This external-layer principle is the same one WIR uses to structure and route intake before it reaches the core. The claims platform, Guidewire ClaimCenter or otherwise, still opens the claim, holds the reserve, and remains the source of truth. The layer sits in front of it, does the reading, validating, and routing, then writes a structured result back through APIs. There is no core migration and no rip and replace, which is exactly why an external AI layer can sit on top of a system like Guidewire without replacing it.

WIR has demonstrated this external-layer approach in a proof of concept with a global insurer in the transport line, structuring and routing incoming submissions before they reached the core. That work was on the submission side of the business, but the architecture is identical: read the messy input, structure it, validate it, route it, and hand a clean record to the system of record. FNOL is the same problem pointed at the claims report instead of the quote request.

What AI does not do at FNOL

Automating FNOL does not mean removing the human or handing settlement to a model. The layer prepares the claim; it does not decide the claim. Coverage determination, reserving, negotiation, and payment stay with the insurer and its adjusters. A low-severity, unambiguous claim can move quickly with light touch, but the moment ambiguity, high severity, or a fraud signal appears, the file goes to a person with the enriched record already assembled. Deciding what happens next remains the insurer's call, made against its own rules and appetite.

Why the economics favor automating FNOL

Claims is the largest cost center most insurers have, and the FNOL step sets the trajectory of every claim behind it. McKinsey, in its analysis "Claims 2030: Dream or reality?", projects that advanced automation and analytics could reduce the cost of the claims journey by an estimated 25 to 30 percent. The mechanism is not mysterious: less manual rekeying, fewer misroutes, earlier fraud signals, and reserves set on better data. Getting the first notice right is where much of that saving originates, because a clean claim at intake is one that does not have to be reworked later. Higher straight-through processing follows from the same source, which is why lifting the STP rate starts at intake rather than at settlement.

FNOL automation in Brazil: SUSEP and LGPD

WIR was born in Brazil, and two constraints shape any claims automation there. The first is the Superintendência de Seguros Privados (SUSEP), which expects insurers to own and justify how claims are handled rather than defer them to an opaque process. The second is the LGPD, Brazil's general data protection law (Law 13.709 of 2018), whose Article 20 gives a person the right to request review of a decision made solely by automated processing that affects their interests.

Both point to the same design rule that governs the layer itself. If AI triages a claim or raises a fraud flag at first notice, that step has to be explainable and reviewable, traceable to the data and the logic behind it, with a person able to step in. A layer that logs its reasoning, returns an audit trail, and keeps a human in the loop is built to stand behind both a SUSEP review and an LGPD review. Automating FNOL does not mean automating accountability away.

The bottom line

The first notice of loss is where claims are made slow or made fast, clean or messy, cheap or expensive. AI automates the part that has always been manual, reading the report, structuring it, validating it, and routing it, so the claim that reaches the core is one the core can act on immediately. Done as an external layer, it changes the intake without touching the system of record, keeps a person in charge of the decisions that matter, and leaves an audit trail that a regulator can follow. That is the same architecture WIR uses to structure and route intake before it reaches the core, pointed at the moment a loss is first reported.