FNOL stands for first notice of loss. It is the moment someone tells their insurer, or the broker who placed the policy, that something has gone wrong, such as a fire, a car accident or a stolen laptop, and asks for a claim to begin. Everything that follows depends on that notice. A broker and a carrier see it from opposite sides, and in most places they still run on separate copies of the same facts.
The broker records the loss, notifies the carrier in line with the policy terms, and keeps the client informed. Late or incomplete notice can put coverage at risk, and the broker owns that risk. The carrier receives the notice by phone, email, portal or broker submission, then checks the policy, triages the claim, assigns an adjuster and acknowledges it back. Meanwhile the client, who may be having the worst week of their year, wants one thing: to know someone has it.
Where it breaks today. On the broker side, the notice lands in whichever inbox or phone the client happens to know, not at a claims desk. Someone retypes it into the broker's system and again into the carrier's portal or an email, and nobody watches the policy's notice deadline. The broker often learns the notice was late only when the carrier says so, and cannot show when it was told.
On the carrier side, notices arrive incomplete, missing a policy number, a date or a cause, and across phone, portal and broker email. The first days go to chasing details and checking coverage by hand. The acknowledgement back to the broker is manual too, so the broker ends up chasing for status.
The notice arrives as a phone call or an email with attachments. Someone retypes it into the broker's system, then into the carrier's. Details drift, nobody owns the clock, and the client calls both sides to ask what happened.
Each system does its job. The fragmentation comes from something else: insurance has lacked a cohesive backbone to sit on top of. Think about your phone. Every app inherits security, permissions, payments and logging from the operating system, so none has to rebuild them. Insurance needs the same. Every workflow should inherit security, controls, an audit trail and integration, whichever side of the claim it serves.
An operating system also decides who does what. The best outcomes come from AI and other intelligence working alongside people. AI reads the email and drafts the notice, other sources add context such as claim history or weather, and an experienced person decides and approves. The platform keeps each in its lane, logs every step, and lets you swap in better intelligence without rebuilding the workflow.
On that backbone, first notice becomes one case that serves both parties:
Naitiv builds that operating system for insurance on ServiceNow Financial Services Operations. ServiceNow runs each notice as a case and reads the broker, carrier and claim systems in place, while AI Control Tower governs the AI doing the reading. Naitiv's Email-to-Case on FSO already turns inbound emails into cases, a natural starting point for FNOL.
The broker gets a notice it can prove and a client it can update. The carrier gets a notice that is complete, triaged and on its way to an adjuster.
Start with loss notices for a few commercial lines and prove that the case matches the systems of record. Naitiv can show a working prototype on your own notice flow in about a week.
.svg){kind=icon}
