Guide · Claims

FNOL intake software: a buyer’s guide for MGAs and carriers

There is no single best FNOL intake software; the right choice depends on how notices reach you and which claims system you keep. Voice and chat tools suit call-heavy lines, core claims suites have FNOL modules built in, and document-intake tools such as Brisc suit notices that arrive by email with attachments. Brisc’s Claims Analyst reads each notice and its attachments in full, extracts the claim record with every field traced to its source document, drafts the acknowledgement for a handler to send, and hands the structured record to the claims system you already run.

Claims intake automation is software that reads a first notice of loss as it arrives, extracts the claim record, and passes it to the claims system, with a person reviewing the exceptions. Brisc sells one of the options in this guide. Every other vendor is described from its own website.

The job

What does FNOL intake software actually do?

FNOL intake software does four jobs. Products differ in which of the four they cover and which channels they start from.

  1. 01

    Receive

    Take the notice in from email, a portal, a phone call or a chat. Each tool starts from different channels.

  2. 02

    Read and extract

    Read the notice and its attachments and build the claim record: insured, policy, date of loss, claimants, what happened.

  3. 03

    Check and flag

    Flag missing fields, severe events, possible exclusion wording, and documents that describe several losses.

  4. 04

    Hand off

    Acknowledge the sender and pass the record to the claims system, where the claim is handled.

Brisc covers receive (email, upload and scheduled pull), read and extract, check and flag, and hand off, with the acknowledgement drafted for a person to send.

Four kinds

What are the four kinds of claims intake tool?

Claims intake tools fall into four groups: voice and chat FNOL, FNOL modules inside a core claims suite, document-intake AI for email and attachments, and general intelligent document processing (IDP) platforms.

  1. 01

    Voice and chat FNOL

    Agents that answer the claimant by phone, SMS or chat and capture the loss in conversation. Right for personal lines and call-heavy books, where the claimant reports the loss directly.

  2. 02

    FNOL inside a claims suite

    Intake built into a core claims system. Right when you run that system, or are replacing yours, and want intake and claim handling from one vendor.

  3. 03

    Document-intake AI

    Tools that read notices arriving by email with attachments in many layouts and build the claim record. Right for commercial and specialty lines, MGAs and carriers, where brokers and cedents send documents.

  4. 04

    General IDP platforms

    Document processing that covers claims among many document types. Right when you want one extraction platform across underwriting, claims and finance, and have the team to configure it.

The shortlist

Which FNOL intake software should you shortlist?

Each vendor is described from its own website.

OptionTypeWhat its own site saysConsider it when
StradaVoice and chat FNOLAI agents that take a full first notice of loss over phone, chat or email around the clock and open the claim with fields populated. Connects to Guidewire, Duck Creek and agency systems by API or browser agent.Claimants and agents phone in, and you need cover out of hours
LiberateVoice and chat FNOLAn insurance-native voice agent that answers calls and handles FNOL, with SMS links for photos and documents and a digital channel for filing a claim. Connects to Guidewire, Duck Creek, Applied, Vertafore and Snapsheet.Phone volume is the bottleneck in your claims front office
Guidewire ClaimCenterFNOL inside a claims suiteWizard-based digital claims intake inside ClaimCenter. In October 2026 Guidewire announced Concierge, agents that take the loss by voice or chat and deliver the claim to ClaimCenter.You run ClaimCenter and want intake inside it
Duck Creek Agentic FNOLFNOL inside a claims suiteConversational intake that captures loss details, photos and documents, routes by severity and carrier rules, and sends the record into Duck Creek Claims or connected systems. Its FAQ says it currently focuses on personal auto.You run Duck Creek and write personal auto
FurtherAIDocument-intake AIDomain-specific AI for insurers, MGAs and brokers, with a claims intake product that moves notices from first notice to open and surfaces coverage gaps at intake.You want one AI vendor across underwriting and claims
Five Sigma (Clive)Document-intake AIAI agents that extract incident details from unstructured data, including PDFs, Word, Excel, images and emails, and generate FNOL reports for the claims system. Works on top of an existing claims system. Lists carriers, MGAs, TPAs and self-insurers.You want intake and adjuster support agents from one vendor
Bevaya (formerly Roots Automation)Document-intake AIAn AI agent that captures FNOL and first report of injury details from email, mailroom, portals and APIs, and creates the claim file in Guidewire, Duck Creek, Salesforce or another system of record. Names carriers, brokers and TPAs.You are a TPA or carrier with high mailroom volume, including workers’ compensation
Sprout.aiDocument-intake AIA claims processing layer that captures and prioritises claims from inbound documents, including handwritten forms, and integrates with Guidewire, Duck Creek, Majesco, Sapiens and other core systems.Your claims arrive as documents in many languages and formats
Applied Systems (Cytora)Document-intake AICytora reads loss notices in any format from claimants, hospitals, repair shops and courts and routes each to the claims team, alongside the carrier’s claims system rather than replacing it.You are a carrier that also wants claim updates delivered to agencies
Indico DataGeneral IDP platformAn intake platform for commercial insurers that ingests emails, documents, ACORD forms and attachments, identifies the claim type, extracts and validates details, and writes them into the claims or downstream system.You want one document platform for underwriting and claims
BriscDocument-intake AIThe Claims Analyst reads each first notice of loss and its attachments in full (PDF, Excel, Word, PowerPoint, image), extracts the claim record with every field traced to its source, flags severe events, possible exclusions and multi-loss documents, and drafts the acknowledgement for a handler to send.Notices that arrive by email with attachments in many layouts; you keep your claims system; a person sends every acknowledgement

Comparing with FurtherAI specifically? See Brisc vs FurtherAI.

Keep your claims system

How do you automate FNOL without replacing your claims system?

Put an intake layer in front of the claims system and keep the claims system as the system of record. The intake layer reads each notice, builds the record and checks it; a person reviews the exceptions; the claims system receives a clean record instead of an email to re-key.

How the record reaches your claims system:

  • API integration. Brisc integrates with systems of record by API.
  • A file the system loads. Brisc delivers a file in the layout your claims system imports.
  • You pull it. Your team or your own tools pull records from Brisc’s API or through MCP agent access.

What this means for go-live:

  • Go-live needs no integration project on day one. Notices in, evidenced records out.
  • Brisc customers go live in 2 to 6 weeks.
  • Your claims system, your workflows and your reporting stay as they are.

See FNOL intake for what the Claims Analyst extracts, and integrations for how records leave Brisc.

Email to claims system

How do you get claim notifications from email into your claims system?

Route the claims inbox to the intake tool, extract one record per notice with each field traced to its source, have a person review the flags and the drafted acknowledgement, then hand the record to the claims system. That is the “auto process for getting them into the system” claims teams ask for, with a person still checking what goes in.

  1. 01

    Route the inbox.

    Point the claims mailbox at the intake tool, or upload notices. No template for brokers or cedents to fill in.

  2. 02

    Extract the record.

    Insured, date and time of occurrence, claimant names, reported and made dates, policy number, external claim number, incident description, damage summary, location.

  3. 03

    Review the flags.

    A handler checks severe-event and exclusion flags, sets severity on an editable scale, and edits and sends the drafted acknowledgement.

  4. 04

    Hand it on.

    The record goes to the claims system by API, file or pull. Every lifecycle step is audited: FNOL, acknowledged, escalated, closed.

The role boundary

What should stay with your claims handlers?

Buy intake automation for the administrative layer, and keep coverage with people. Ask every vendor which decisions its tool makes on its own.

What Brisc does:

  • Reads every notice in full, every page and every attachment.
  • Extracts the claim record, with each field traced to its source document.
  • Flags severe-event and exclusion keywords and multi-loss documents.
  • Drafts the acknowledgement from five templates: open, open with schedule, close, reservation of rights, and denial.
  • Records every lifecycle transition: who, when, from what state.

What stays with your handlers:

  • Coverage positions. Brisc flags wording; the handler decides.
  • Reservations of rights and denials. Brisc drafts these letters only on a handler’s instruction.
  • Reserves. Brisc does not set reserves.
  • Splitting a multi-loss document into separate claims.
  • Sending. A person sends every acknowledgement.

Related reading: human in the loop in insurance AI, modernizing claims triage with AI, and accuracy and audit.

Before you choose

What questions should you ask an FNOL vendor?

Put these to every vendor, Brisc included.

  1. 01

    Attachments.

    Does it read the attachments, or only the email body?

  2. 02

    Evidence.

    Is every extracted field traced to its source document?

  3. 03

    Acknowledgement.

    Who sends the acknowledgement: the tool or a person?

  4. 04

    Several losses.

    What happens when one document holds several losses?

  5. 05

    Your claims system.

    Does it need your claims system replaced, or integrated first?

  6. 06

    Decisions.

    Which decisions does it make on its own, and which stay with handlers?

  7. 07

    Data.

    Where does your data live, and does it train a model?

  8. 08

    Accuracy.

    How is accuracy measured, field by field, on your notices?

  9. 09

    Go-live.

    How long to go live, and what does day one need from your IT team?

For data handling, see security and tenancy. For the wider picture, see the complete guide to claims process automation and intelligent document processing in insurance.

Common questions

Frequently asked questions

What is FNOL in insurance?

First notice of loss (FNOL) is the first report to an insurer or MGA that a loss has happened. It usually arrives as an email, a form, a phone call or a document from a broker, insured or claimant, and it starts the claim.

What is the difference between FNOL software and a claims management system?

FNOL software handles the front door: it reads the notice, builds the claim record and routes it. A claims management system is where the claim then lives, from reserves and payments to closure. Some suites include both; document-intake tools such as Brisc sit in front of the claims system you already run.

Can AI read loss notices that arrive as PDFs, Word files and spreadsheets?

Yes. Document-intake tools read the email and its attachments together. Brisc reads PDF, Excel, Word, PowerPoint and image attachments and extracts one claim record, with every field traced to the document it came from. Test any vendor on your own messiest notices.

Does FNOL automation decide coverage?

It should not. Brisc flags severe-event and exclusion keywords, and the coverage position stays with your handler. Ask every vendor which decisions its tool makes on its own. See what should stay with your claims handlers.

What happens when one email or spreadsheet contains several claims?

Brisc flags a document that describes several losses, and a person decides how to split it. Brisc does not split claims automatically. Lists of many claims in one spreadsheet are read by the Claims Laundry List Analyst; see the guide to reviewing a claims laundry list.

Who sends the acknowledgement to the broker or insured?

With Brisc, your handler, always. The Analyst drafts the acknowledgement from your templates, fills the claim and policy details and highlights gaps. A person reviews, edits and sends.

Do we need to integrate with our claims system before we start?

No. Go-live needs no integration project on day one. The claims system stays the system of record, and the structured record is handed to your handlers and your existing system.

How accurate is AI extraction on claim notices, and how is it checked?

Ask for accuracy measured field by field on your own notices. Brisc reports 99.1% field-level data accuracy across its Analysts in production, and every extracted field shows the source document so a person can check it.

Can it handle notices from many carriers or brokers in different layouts?

It should, without a template mandate on senders. Brisc reads notices in whatever layout arrives, groups acknowledgement templates by carrier, and produces the same record shape for every sender.

How do TPAs handle loss notices from many carriers?

Each carrier and broker sends notices in its own format, and each expects its own acknowledgement. Good intake software takes every format as it comes, groups acknowledgement templates by carrier, flags a document that describes several losses, and gives every sender the same record shape on the way out. Brisc’s claims customers today are MGAs and MGUs rather than TPAs.

Is our claims data used to train the model?

Not with Brisc. Each customer runs in a dedicated tenant on Microsoft Azure, and customer data never trains a model. Brisc is SOC 2 Type II, GDPR and CCPA compliant. Ask every vendor the same question in writing.

Bring your own notices. Watch the claim open.

30 minutes, no slide deck. We run real notices and show the record, the flags, and the drafted acknowledgement.

Book the walkthrough

Not ready for a call? Get the MGA operations report →