FNOL for a Fender Bender Is More Complicated Than It Should Be

A few weeks ago while driving home across the GW Bridge back to New York, a car tried to pass me and clipped my front tire. 

We pulled over, luckily no one was hurt, and exchanged info. The other driver, clearly rattled, said off the bat they wanted to go through insurance. I said okay. 

The fender bender should have been the hard part. Two weeks later with limited resolution, it clearly was just the beginning of it.

I wrote about my experience and how both insurance companies could have more efficiently managed the claims, sped up resolution, and saved me hours of AI feedback loops, reentering the same information, and waiting for next steps that still have not come.  

When FNOL Becomes an Endless Loop

After they reported the first notice of loss (FNOL), an adjuster from the other insurance company gave me a call. They asked for my story and said they'd text me a link for me to upload photos — but that link never came. Instead a text came asking me to create an account to continue. Then I missed a call. A second adjuster had picked up the case and left me a message saying the insurance company had decided to accept 25% liability, with nothing on their end to explain why.

That meant the remaining 75% was now my problem, even though I was not at fault. That meant I now had to file a second claim with my own insurer. 

Duplicate Work Is the Real Cost of Disconnected Systems

My insurer wanted 10 photos from the accident uploaded via a link they sent over text. A few days later, they followed up by instructing me to drive my car to a specific auto repair shop 11 miles outside the city, which for those who are familiar with New York, always takes longer to get to than it should. The technician at the garage then took the same photos I'd already uploaded and sent them, too. I continued to wait for the promised follow-up from an adjuster, which never came. 

I called in and reached a voice AI agent, gave my claim number, explained that I'm not at fault but the other carrier isn't covering full liability so I need to file on my end too. It transferred me to another AI agent. I explained the whole thing again. It transferred me again. 

By Tuesday, a full week after the accident, nothing was resolved.  

Nothing about this accident was complicated. A car clipped my tire at low speed. Nobody was hurt. Fault was reasonably clear. And it still took a week, two insurers, two adjusters, one in-person inspection that duplicated photos I'd already sent, and two AI agents that couldn't hold onto the story I'd just told them, to get nowhere.

It's Not the Car. It's the System.

Sure you could argue that vehicles are more complex and becoming harder to repair, but the truth is that’s not what is causing the delay. 

It was about five different systems that didn't talk to each other: a photo-upload link that never arrived, a mobile app built for one purpose that couldn't kick off a claim, an in-person inspection that repeated work already done, and a voice AI that reset to zero every time it handed me to the next agent.

That's not a technology problem in the sense of the AI being bad at conversation. It's a design problem. Every one of those steps was built as its own point solution, solving its own narrow task, with no shared memory of what had already happened. The result is that the person going through the worst part of their week does the most repeating.

What FNOL Should Actually Look Like  

I have been living, from the consumer side, the exact problem we think about at Notch. Insurance carriers are spending unnecessary time settling a case. 

If a voice agent was able to communicate context from a customer conversation to another voice agent or a human adjuster, everyone would save time. If documents, photos, and information about an accident could be properly and safely stored and usable by everyone who touches the claim afterward, repetitive tasks could be avoided and everyone could reach a resolution quicker. The AI audit report is no longer optional either, and it’s essential all this information is stored correctly. 

FNOL automation is changing the game for carriers. It shapes how a policyholder, in this case me, experiences the entire process. It should happen on the spot, in one flow, not spread across a photo tag, an app, a garage visit, and a phone tree. A negative experience can affect the relationship, and potentially their renewal.

A fender bender is, at its core, can be a simple problem: figure out what's damaged, decide who pays, get it fixed. But a lot of what makes a simple accident feel unbearable isn't the need to replace a new fancy tire. It's that nobody built the process to remember what you already told it.