How Should FNOL Call Routing Work?

First notice of loss (FNOL) call routing should use a 4-step sheet: spot the loss, find the likely policy and carrier, check exceptions, then send the caller to the approved carrier path or agency person. That lets customer service representatives (CSRs) help claim callers without hunting for numbers or giving coverage advice, even after hours.

I’m Chandan Maruthi, CEO of Twig. When I review agency phone calls and scripts, the same problem keeps showing up. The issue is not a missing claims philosophy. It is an old number or an exception rule that only one senior CSR knows.

Everyone says “claims go to the carrier.” But the Tuesday 5:40 p.m. fender-bender still gets messy. The senior CSR may be gone, the producer may own the relationship, or the caller may ask, “Should I even file this?”

TL;DR: FNOL call routing works best when you separate fact-gathering from advice. Identify the loss, record the carrier the caller states if known, send routine claims to the agency-approved carrier path, and send unclear or sensitive cases to the right agency person.

What Is the Best Way to Handle FNOL Call Routing?

The best way to handle FNOL call routing is a short decision tree your CSRs can use during a live call. The CSR should identify the loss, record the carrier if the caller knows it, check exception rules, and then use the approved carrier path or agency escalation rule.

Treat this as an operating template, not legal or coverage guidance. Have your principal, compliance adviser, and carriers approve the final script and rules for each state and line of business.

Here is the 4-step version I recommend for agencies with personal lines and small commercial books:

1. Recognize the call as FNOL. The caller says “accident,” “water leak,” “claim,” “hit my car,” “tree fell,” “slip and fall,” “stolen,” or “I need to report something.”
2. Find the likely policy and carrier path. Use caller name, phone number, address, vehicle, business name, policy number, or the carrier the caller names. Do not treat caller-provided information as verified unless your agency procedure allows it.
3. Apply exception rules. Injury, unclear carrier, coverage questions, VIP commercial account, large loss, cancellation or nonpay uncertainty, or producer-owned relationship.
4. Send the call to the next step. Transfer to carrier claims intake, give the carrier claims number, send the carrier’s claim link if appropriate, or send the call to the right agency person.

The point is not to make the first person who answers the phone “handle claims.” The point is to stop the live-call scavenger hunt while a customer is upset and your CSR is trying not to say the wrong thing.

What Goes on a Carrier FNOL Sheet?

A carrier FNOL sheet should include only what the person answering the phone needs right then. That means carrier claim paths, agency rules, and the name of the person who handles exceptions. If the sheet is too complicated, CSRs will stop using it during real calls.

Do not build a 19-column spreadsheet that only your operations manager understands. Build a phone-desk tool. It should be boring, current, and printable.

Field	Why it matters	Example entry
Carrier name	Prevents confusion between similar carrier names	Travelers personal lines vs Travelers small commercial
Line of business	Claim paths may differ by coverage type	Personal auto, homeowners, business owner's policy
FNOL phone number	Gives the CSR one approved live-call path	Carrier claims intake number
Online claims link	Useful for text or email follow-up if your agency uses it	Carrier claim reporting page
After-hours rule	Avoids voicemail dead ends	Transfer to carrier intake; escalate injury claims per procedure
Escalation owner	Gives CSRs a name, not a shrug	Commercial CSR, producer, principal
Do-not-send notes	Protects sensitive accounts and edge cases	“Call producer before direct carrier path for ABC Manufacturing”
Last verified date	Forces review because carrier paths can change	Reviewed monthly at first, then on an agency-approved cadence

I would rather see a simple sheet updated on a real schedule than a beautiful process doc nobody opens. Put it where CSRs already work. If your team prints phone scripts, print this too.

If your team uses a shared drive, make the file name obvious: FNOL routing - carrier claims numbers.

What Should a CSR Say on a Claim Call?

A CSR should acknowledge the loss, collect the facts needed to send the caller to the right next step, and avoid coverage opinions. The script should sound human, but it should also protect the agency from promises the carrier has not made.

A good FNOL script sounds like this:

“I’m sorry that happened. I can help get you to the right claims path. I’m going to collect a few basics so we send this correctly, but the carrier will make the coverage and claim decisions.”

Then collect only what is needed:

• Caller name and callback number
• Named insured or business name
• Policy number, address, vehicle, or other lookup clue
• Date and general type of loss
• Whether anyone is injured or the property is unsafe
• Whether emergency mitigation is already underway, if relevant
• Carrier, if the caller knows it

What I do not want a CSR saying:

• “That should be covered.”
• “Don’t file that; your rates will go up.”
• “This probably won’t count as a claim.”
• “The carrier will definitely pay for that rental.”
• “You only have a $500 deductible,” unless they are reading a verified policy artifact and your agency allows that wording.

A conservative phrase for an agency-approved script is: “The carrier will confirm coverage and next steps.” Boring is good on claims calls.

Which Claim Calls Need an Agency Person First?

Some claim calls should not go straight to the carrier because the caller is asking for advice, the policy is unclear, or the agency has a special account rule. Those calls need an agency-designated person before anyone gives guidance or sends the insured down the wrong path.

The exception categories vary by state, carrier, policy, and agency authority. Review these common operating rules with your principal, compliance adviser, and carriers:

Scenario	Route to carrier?	Better first step
Clear personal auto accident, carrier known, no coverage question	Often yes, if approved	Transfer or provide carrier claims intake
Caller asks, “Should I file this?”	Not as a routine transfer	Agency-designated licensed staff member, if required by your procedures and state rules
Injury, fatality, major property damage, or unsafe scene	Not only	Follow emergency script, then carrier or internal escalation per procedure
Policy status unclear or possible lapse	Not as a routine transfer	Agency-designated review before guidance
Commercial account with producer-managed relationship	Maybe	Notify producer or commercial CSR per account rule
Multiple policies could apply	Not as a routine transfer	Agency-designated staff review
Caller is angry about a prior claim	Usually no	Escalate to principal, claims advocate, or account owner
Carrier is unknown	No	Internal lookup before carrier path

A simple operating rule works: send routine claims to the approved carrier path; send unclear claims to the right agency person.

The uncomfortable middle is where agencies get in trouble. A customer says, “My basement has water. Should I use homeowners or just pay out of pocket?” That is not a phone-tree problem. That is a licensed-advice boundary problem, and your agency should define who handles it.

How Should After-Hours FNOL Calls Be Handled?

After-hours FNOL calls need stricter rules because your agency cannot rely on hallway questions, a senior CSR lookup, or a producer overhearing the call. Decide before closing which calls can go to the carrier, which calls need emergency wording, and which calls need a human response.

For after-hours, I like three buckets:

1. Routine and carrier known: give or transfer to the agency-approved carrier FNOL path.
2. Emergency wording trigger: if the caller says someone is in immediate danger or needs urgent medical help, instruct them to call 911 or the appropriate local emergency service. Do not try to assess the emergency. Have agency counsel or compliance approve the final wording.
3. Ambiguous or sensitive: capture details and escalate to the on-call person or next-business-day agency-designated callback, depending on your approved procedure.

Here is the operating table I would use:

After-hours task	Who handles it	Delay this prevents
Answer the initial call	AI receptionist, CSR, or answering service	Missed voicemail delay
Identify FNOL intent	Phone script	Repeated intent questions
Record the carrier named by the caller	CSR or AI receptionist using caller-provided information	Searching carrier directories
Send routine claim to carrier intake	CSR or AI receptionist if live transfer is set up and your rules allow it	Waiting for a next-day agency callback
Escalate exception to human	On-call CSR, producer, principal, or agency-designated licensed staff member if required	Wrong carrier path
Log the interaction	Transcript or CSR note	Reconstructing an undocumented call

The key is deciding before 5 p.m. what deserves a human interruption at 9 p.m. If everything escalates, your team burns out. If nothing escalates, your best accounts feel abandoned when the loss is serious.

If missed calls are already a revenue and service problem in your agency, the same phone discipline applies here. I wrote more about unanswered calls in From Missed Call to Booked Revenue.

Where Does Sera Fit, and Where Does She Not?

Sera fits best at the first step of FNOL calls: answering right away, identifying that the caller may be reporting a claim, collecting your required facts, escalating by your rules, and logging a transcript for staff. Sera does not replace licensed judgment or carrier claim handling.

Twig makes Sera. Sera is an AI front desk for local businesses. She answers every phone call, text, web chat, email, and WhatsApp message, 24/7, and books the appointment.

For an independent insurance agency, the useful FNOL role is narrower than “AI handles claims.” I would not buy that pitch. The safer job is:

• Answer calls, including lunch and after-hours.
• Recognize that the caller is reporting a possible claim.
• Ask for the basic facts your agency defines.
• Record the stated carrier when the caller provides one.
• Live-transfer on Growth and above when your rules call for it.
• Escalate to your team when the question is outside what she knows, with the conversation attached.
• Log a full transcript so the CSR, producer, or principal can see what happened.

You can learn more about Sera for agencies on our AI receptionist for independent insurance agencies page. If you want the broader category definition, see What is an AI front desk?.

Now the limits, because they matter:

• Sera does not bind coverage.
• Sera does not quote premiums.
• Sera does not give coverage advice.
• Sera does not file claims with carriers.
• Sera does not directly integrate with agency management systems (AMSs) like EZLynx, HawkSoft, Applied Epic, AMS360, or QQCatalyst.
• Sera logs transcripts, not call audio recordings.
• Twig is SOC 2 Type II certified, but Twig is not Health Insurance Portability and Accountability Act (HIPAA) compliant and does not sign business associate agreements (BAAs).

Most businesses are live in under 30 minutes by forwarding the phone line or adding website chat. Appointment booking, missed-call text-back, live transfers, and multi-language conversations are included on Growth and above, not Starter. Pricing starts at $49/month, and every plan starts with a 15-day free trial, voice included, no credit card. Details are on Sera pricing.

If you want to hear how Sera answers in real time, call the live demo line: (650) 795-7838.

What Should You Do Next?

Start with one sheet covering your 10 highest-volume carriers, then test it on calls your team actually gets. The first version does not need to be perfect. It needs to be clear enough that a CSR can use it while a shaken insured is on the phone.

For each carrier, document the FNOL phone number, online claim link, line-of-business differences, after-hours rule, and “do not send directly” exceptions. Then test the sheet on three calls your team actually sees: a personal auto accident, a homeowners water loss, and a small commercial incident where the producer owns the relationship.

Do not wait for the perfect claims process. Once the sheet exists, you can decide whether the first step should be handled by a CSR, an answering service, or an AI front desk like Sera.