FNOL intake design — capturing a complete claim on the first call

Required fields by line of business, policy lookup before the greeting, warm transfers that carry context to the adjuster, and photo collection while the policyholder is still on the phone.

4 min readUpdated June 2026

On this page

A claim that starts incomplete starts over

First notice of loss is the highest-stakes intake in insurance. The policyholder is often calling on the worst day of their month — sometimes their year — and everything downstream depends on what gets captured in the next ten minutes. A FNOL that misses the date of loss, the injury question, or the right vehicle details doesn't just slow one call; it generates a callback, a re-key, and an adjuster who starts their work by redoing yours.

Good FNOL intake is a design problem, not an agent-training problem. This guide covers the four design decisions that determine whether claims start complete: required fields per line of business, policy lookup before the greeting, the warm transfer to the adjuster, and document collection in the same conversation.

Required fields, enforced by the workflow — not the agent

Every line of business needs a different intake, and the workflow should enforce the differences so completeness doesn't depend on which agent picks up. A common core applies everywhere: policy number, loss type, date and time of loss, location of loss, injuries or damages, preferred contact method, and urgency level. Then each line adds its own:

Auto — vehicle details (year, make, model, plate), drivers and passengers involved, other parties and their insurance, police report number if one exists, drivability of the vehicle, tow status
Property — property address versus mailing address, type of damage (water, wind, fire, theft), whether the home is habitable, emergency mitigation already underway, and whether anyone is displaced
Workers' comp — injured employee details, employer and supervisor, body part and nature of injury, whether medical treatment has been sought, witnesses, and the state jurisdiction (which drives the reporting clock)
Liability — claimant versus insured distinction, what happened and where, injuries or property damage alleged, and whether any demand or attorney is already involved

The operative word is enforced. Required fields that live in a training document get skipped under pressure. Required fields built into the intake flow can't be — the workflow won't move forward without them, and a complete claim is the only kind that leaves the call.

Policy lookup before the greeting

The single highest-leverage moment in FNOL is the second before the agent speaks. An ANI match against the policy system means the agent answers with the policyholder's name, policy, and coverage already on screen.

The policyholder doesn't start their worst day by spelling their name and reading a policy number off a wet declarations page
The agent immediately knows the line of business — which intake flow to run — and whether the policy is in force
Coverage questions ("am I covered for this?") get answered from real data instead of deferred to a callback

When ANI doesn't match — a borrowed phone, a new number — the flow falls back to a quick lookup. But designing for the match case first changes the emotional register of the whole call: it opens with "I see your auto policy — tell me what happened" instead of an account-locating exercise.

Warm transfer to the adjuster, with the context attached

The worst sentence in claims is the policyholder repeating their loss story for the second time. If the call needs an adjuster — serious injury, large loss, complex liability — the transfer should be warm and the context should travel:

The intake record, complete with every captured field, lands on the adjuster's screen before the policyholder is connected
The agent introduces the call ("I have Ms. Rivera, water damage at her home, mitigation underway") so the adjuster starts on judgment, not re-keying
The policyholder confirms details instead of re-narrating them

Decide in advance which loss types transfer live and which get a scheduled adjuster callback. Both are fine; what's not fine is a cold transfer that drops the context and forces the story to start over.

Collect photos and documents in the same conversation

Every document you collect during or immediately after the FNOL call is a follow-up cycle you never run. Two-way SMS is the workhorse here:

Text the policyholder a request for photos of the damage while they're still on the call — vehicle damage, the water line on the drywall, the police report
Confirm receipt before the call ends so nothing sits in an inbox unverified
Log the documents against the claim so the adjuster sees them alongside the intake fields

For losses where photos aren't possible yet, set the expectation explicitly and send the request anyway — a pending SMS thread is a far better reminder than "we'll mail you a form."

Close the loop with measurement

FNOL intake earns its design through the numbers: intake completion rate (claims with all required fields on the first call), adjuster transfer rate, callback rate for missing information, and time from FNOL to adjuster assignment, all by line of business. If your reporting can drill from those KPIs down to individual interactions, weak spots in the flow show up as patterns instead of anecdotes.

The short version

Design FNOL so completeness is structural: required fields per line of business enforced by the workflow, policy lookup on ANI match so the call opens with context instead of an account search, warm transfers that carry the full intake to the adjuster, and photo collection by SMS before the call ends. The policyholder tells their story once, the claim starts complete, and the adjuster starts on judgment instead of data entry.

Back to

Industries

Return to the main industries page to see the full product family.

Related guides

Guide

See how SingleComm fits your industry's compliance and workflow posture.

Schedule a demo