Claims Analyst · Job one

First notice of loss intake. Read, opened, acknowledged.

Brisc reads first notices of loss as they arrive, email plus attachments, and extracts the record your handler needs to open the claim. It drafts the acknowledgement, flags severe events and possible exclusions, and queues anything that needs senior eyes.

FNOL-0182 Record extracted email + 2 attachments
InsuredMeridian Coastal Homes Ltd
Policy no.POL-88213-B
Date of occurrence2026-06-14 · 03:40
Damage summaryRoof collapse, unit 4; no injuries reported
Severity3 / 6 editable
severe-event keyword: collapse exclusion scan: clear
Acknowledgement drafted · awaiting analyst review and send
The claim record

Open the claim from the notice itself.

One extraction pass across PDF, Excel, Word, PowerPoint and images. Every field carries its source document, so the record can be checked.

insureddate & time of occurrenceclaimant names reported datemade datepolicy number external claim numberincident descriptiondamage summary city / state / country

Severe-event flags

Severe-event keywords are flagged on arrival, so the file that needs a senior handler surfaces first.

Exclusion keywords detected

Wording that may touch an exclusion is surfaced. The coverage call stays with your handler.

Multi-loss detection

One document describing several losses is flagged as such. Splitting stays a human decision, deliberately.

The acknowledgement

Drafted by the Analyst. Sent by your analyst.

Five templates, auto-filled with claim and policy variables, grouped by carrier, gaps highlighted. Edit, then send. A human is in the loop on every one.

Open

The standard acknowledgement, variables filled from the record.

Open with schedule

Acknowledgement plus the document schedule you need back.

Close

Closure confirmation, drafted from the file’s final state.

Reservation of rights

Drafted for the handler; the position itself is always theirs.

Denial

Drafted only on your handler’s instruction. Never automatic.

The lifecycle

Every transition audited. Every severity yours to set.

Every transition is recorded: who, when, from what state. Severity sits on an editable one-to-six scale, and the detected keywords behind a flag are one click away.

FNOL acknowledged escalated closed
One Analyst, two jobs

Notice in. Laundry list screened.

FNOL intake is job one. Job two reads bulk claims laundry lists and finds the claims that matter.

Common questions

Claims intake, answered

What if one email carries five notices?

Honest answer: your handler splits them today. The Analyst reads each notice it is given and flags multi-loss content it detects inside a document, but it doesn’t automatically split one submission into five claims. Splitting stays a human decision.

Does it decide coverage?

No. The Analyst extracts the record, drafts the acknowledgement, and surfaces severe-event and exclusion keywords it detected. Coverage positions, reservations and denials are your handler’s call, made with the evidence in front of them.

Who sends the acknowledgement?

Your analyst, always. Brisc drafts it from the right template, fills the claim and policy variables, and highlights any gaps. A person reviews, edits if needed, and sends.

What file formats does it read?

The notice email plus whatever rides with it: PDF, Excel, Word, PowerPoint and images. No template for brokers or cedents to fill in, no format mandate.

How is our data handled?

SOC 2 Type II, GDPR and CCPA compliant. Every customer runs in a dedicated tenant on Microsoft Azure, your data never trains our models, and every lifecycle transition is audited and exportable.

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