To automate claim intake from email, route your claims inbox to Brisc. It reads each first notice of loss with its attachments, extracts the claim record your handler needs to open the claim, flags severe events and possible exclusions, and drafts the acknowledgement for a person to send. It sits in front of your existing claims system, without replacing it.
One extraction pass across PDF, Excel, Word, PowerPoint and images. Every field carries its source document, so the record can be checked.
Severe-event keywords are flagged on arrival, so the file that needs a senior handler surfaces first.
Wording that may touch an exclusion is surfaced. The coverage call stays with your handler.
One document describing several losses is flagged as such. Splitting stays a human decision, deliberately.
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.
The standard acknowledgement, variables filled from the record.
Acknowledgement plus the document schedule you need back.
Closure confirmation, drafted from the file’s final state.
Drafted for the handler; the position itself is always theirs.
Drafted only on your handler’s instruction. Never automatic.
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 intake is job one. Job two reads bulk claims laundry lists and finds the claims that matter.
Route the claims inbox to Brisc, or upload notices. The Analyst reads each notice with its attachments and extracts one claim record, every field traced to its source document. A handler reviews the flags and sends the drafted acknowledgement, and the record goes to your claims system by API, file or pull. Brisc sits in front of your claims system; it does not replace it. More in the claims intake buyer’s guide.
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.
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.
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.
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.
Brisc is a document-intake tool for notices that arrive by email with attachments. Voice and chat tools and claims-suite FNOL modules suit other intake patterns. Our FNOL intake software buyer’s guide compares the options, each described from its own website.
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.
30 minutes, no slide deck. We run real notices and show the record, the flags, and the drafted acknowledgement.
Book the walkthroughNot ready for a call? Get the MGA operations report →