The short answer
A good FNOL call captures, in one go: who is calling and their policy, what happened, when and where, who else was involved, any police or incident report, injuries and damage, and what the caller needs next. Required notices are given the same way on every call. Most delays come from one missing detail, such as the time of loss or a police report number, that forces a callback.
Why the first call sets the pace of the claim
First notice of loss is the first report of a loss to the insurer or its claims administrator. Everything after it, from assigning an adjuster to arranging a rental car, depends on what was captured on that call. A missing detail means a callback, which delays the claim for a policyholder who is already having a bad day.
The FNOL call checklist
Open and verify
Identify the caller and their relationship to the policyholder. Verify the policy before discussing it. Give the recorded-line notice and any other notice the programme requires.
Check everyone is safe
If the loss has just happened, confirm nobody is in danger and that emergency services have been called where needed, before collecting details.
What happened
A short account in the caller's words, the type of loss (collision, theft, weather, fire, water, injury) and the cause if known.
When and where
Date and time of the loss, and the exact location. These are the details most often missed, and they matter for coverage.
Who was involved
Other parties and vehicles, their insurers if known, and witnesses with contact details.
Reports and evidence
Police or incident report number and the agency that took it. Photos, receipts and documents the caller can send, and how to send them.
Injuries and damage
Whether anyone was hurt, what was damaged, and where the vehicle or property is now.
Coverage questions
Answer only from the caller's policy: rental cover, deductible, towing. If unsure, say what will be checked and when, rather than guessing.
Next steps
The claim number, what happens next and when, who will be in touch, and how to reach the claims team.
Wrap-up
Claim type, loss date and time, location, other party, police report, rental eligibility and follow-ups saved to the claims system before the next call.
The details that cause callbacks
| Missing detail | Why it matters |
|---|---|
| Time of loss | Coverage depends on the policy being in force at that moment, and it anchors the timeline. |
| Exact location | Needed for police reports, liability and choosing repairers or adjusters. |
| Police or incident report number | Expected for many theft and collision claims. Chasing it later adds days. |
| Other party and their insurer | Needed to recover costs from another insurer. |
| Rental eligibility | A wrong answer either way leads to a complaint or a cost the policy doesn't cover. |
| Best contact number and times | Adjusters lose time chasing policyholders they cannot reach. |
Required notices and complaints
Many programmes require set notices on claim calls, such as telling the caller the line is recorded, or statements required by state rules or the carrier. Requirements vary by state and by client, so take the exact wording from the client's script and give it the same way every time.
Callers often voice dissatisfaction on claim calls. Insurers are generally expected to record and handle complaints, so agents need to recognise one and capture it, even when the caller never uses the word "complaint".
How to QA an FNOL call
Score FNOL calls on completeness and accuracy, not only courtesy:
- Were all required details captured, and were they right?
- Were required notices given, in the required words?
- Were coverage answers correct for this caller's policy?
- Was a complaint recognised and logged?
- Did the caller leave knowing the claim number and the next steps?
Scoring every claim call, rather than a sample, shows which details are missed most and on which teams. See how to QA every call.
Where Orian fits
How Orian helps on claim calls
- Walks agents through the first report of a claim step by step, with a checklist for time, place, other party and police report.
- Shows the exact coverage answer from the policy summary, with its source.
- Keeps the recorded-line notice on screen until it is given, and logs every required notice on every call.
- Flags missing details before the call ends, and drafts the claim fields at hang-up for your claims system.
- Prompts complaint capture when a caller expresses dissatisfaction, logged for QA.
This guide is general information about running contact-centre programmes, not legal advice. Rules change and vary by state, country and client contract, so confirm your requirements with your compliance team or counsel.