Use case
eFNOL claim declaration: a usable file from the very first contact
eFNOL (electronic First Notice of Loss) is a claim declaration made through a digital channel. With Korint, the AI-native modular insurance suite, policyholders declare their claim online or by voice, AI structures their account and analyses their supporting documents, and your handlers receive a pre-qualified file, connected directly to their claims system.
Who is this for?
Insurers, wholesale brokers, MGAs and TPAs
This use case is for organisations that handle claims on their own behalf or for an insurer, and want to modernise the declaration without replacing all of their tools.
Korint eFNOL works on its own, connected to your existing claims system, or within the Korint suite, alongside claims management, underwriting and portfolio steering.
The problem
An incomplete declaration is a file that starts with chasers
In many cases, the declaration arrives in a state no one can work with:
- Vague circumstances
- Missing supporting documents
- Information scattered across an email, a phone call and a form
- Late checks: an inconsistency in an invoice or an accident report is only spotted once the investigation has started, when it is already costing everyone time
Why it matters
The declaration sets the pace of the whole claim
The first contact is the moment a policyholder truly judges their insurer. It is also where handling efficiency is decided: a file that is complete and structured from the outset is processed faster, checked better and settled more calmly.
So the challenge is not just to collect a declaration online, but to make it usable the moment it arrives. That is the difference between a digital form and a genuine eFNOL journey.
How it works
From declaration to the right workflow, in four steps
Step 1
The policyholder tells what happened
The policyholder declares online or describes the circumstances by voice. Speech-to-text turns their account into structured information: date, place, people involved, damage declared. The journey adapts to the insurance product concerned, so it only asks for the information that matters.
Step 2
AI prepares the file
Accident report, invoice, photo of the damage: AI analyses the documents sent, extracts the key information and pre-fills the file. The account and the documents form a structured basis for the investigation, instead of a pile of attachments to rework by hand.
Step 3
Anomalies are flagged at entry
Document checks spot inconsistencies and signs of potential fraud at the very moment of the declaration. These alerts guide the handler’s checks; the handler stays in charge of the analysis and the decision.
Step 4
The file joins the right handling workflow
The steps of the journey are configured to your products and processes. The data is sent to your claims system via API, with no re-keying. The handler receives a pre-qualified file, with the documents and the points of attention needed to carry on with the investigation.
The result
What you gain
Less manual preparation: extraction, pre-filling and back-office integration free your handlers up for analysis and taking care of the claim.
A more natural declaration for the policyholder: voice lets them describe a complex or urgent situation without rephrasing it into a form.
Earlier checks: anomalies are flagged before they spread through the handling of the file.
End-to-end continuity: the policyholder experience, document AI and your business workflows are linked in a single journey.
Frequently asked questions about eFNOL
What is eFNOL?
eFNOL, for electronic First Notice of Loss, is the initial declaration of a claim through a digital channel. It gathers the circumstances, the information needed to open the file and the first supporting documents.
What is the difference between FNOL and eFNOL?
FNOL is the first notification of a claim, whatever the channel: phone, post or digital. eFNOL is its electronic version. AI is not essential to an eFNOL; at Korint, it enriches the journey with voice transcription and document analysis.
What information should a claim declaration collect?
Depending on the product and the nature of the claim: identity and contact details of the declarant, policy reference, date and place of the event, circumstances, damage, people involved and supporting documents. A good journey only asks for what genuinely serves the investigation.
What does AI do in the Korint eFNOL journey?
It transcribes the spoken account, extracts the data from supporting documents, pre-fills the file and flags document inconsistencies. It prepares the handler’s work; the settlement decision stays human.
Can eFNOL be deployed without changing claims system?
Yes. The Korint journey connects to your existing claims system via API. The scope of the exchanges is defined when the project is scoped.
How long does it take to deploy?
It depends on the products concerned, the journeys to configure, the AI features chosen and the connections to your information system. A precise schedule is set after scoping.
Let's talk about your claim declaration journey
Our teams are at your disposal.