Use Cases

Insurance

FNOL and Claims Intake Automation

Connect6 guides policyholders, claimants, agents, or authorized representatives through insurer-approved first notice of loss questions. It can collect loss details, parties, injuries, damage information, documents, photos, contact preferences, and required acknowledgements through a clear conversational AI experience.

Agent6 validates required information, identifies missing or conflicting items, organizes supporting records, prepares the FNOL summary, and routes the intake to the configured claims queue. Claim, coverage, liability, fraud, reserve, settlement, and payment decisions remain with authorized insurer teams.

Why This Use Case Matters

The first interaction shapes downstream claim quality

A clear intake experience helps a stressed reporter understand which details, documents, and immediate actions matter. Better intake gives claims teams a stronger starting point.

Missing information creates recontact and assignment delay

Absent dates, parties, contact details, damage descriptions, police information, or supporting records force claims teams to reopen the intake before handling can begin.

Sensitive reports need controlled escalation

Injury, emergency, legal representation, catastrophic loss, system errors, and unsupported products require clear instructions, rapid human routing, and defined privacy boundaries.

The Business Challenge and the Bay6 AI Solution

See how Bay6 AI guides reporters through loss intake and prepares complete, structured, review-ready information for the appropriate claims team.

A first report can arrive through phone, forms, email, portals, photographs, police reports, estimates, agent notes, or third parties. The quality and urgency of the information vary widely by product, loss type, reporter, and jurisdiction.

Reporters describe similar losses with different terms, detail levels, and supporting records.
Required dates, locations, parties, injuries, damages, policy information, or consent may be missing.
Claims staff repeat questions and rekey information into downstream systems.
Emergency, injury, legal, catastrophe, and complaint conditions require immediate path changes.
Duplicate reports and conflicting values can create multiple records or incorrect routing.
Leaders need visibility into completion, recontact, assignment speed, and downstream correction.

Bay6 creates a guided intake path from first report to claims review. Connect6 asks questions based on the configured product, loss type, reporter, and response. It can explain approved next steps and collect documents or media without implying a coverage or claim outcome.

Agent6 classifies the loss and submitted records, validates required fields, flags conflicts or exceptions, prepares a concise intake summary, and can post approved fields or route the matter when the connected system and review rules permit it.

Operating principle: FNOL automation improves information collection and routing. Claims professionals retain every material decision about the loss and policy.

How the FNOL and Claims Intake Workflow Works

The workflow guides the reporter, validates the intake, and prepares the file before assignment.

Define intake boundaries

Select supported products, losses, reporters, jurisdictions, questions, documents, safety messages, and escalation conditions.

Identify the reporter and policy

Collect configured identity, contact, role, policy, and loss information and verify permitted records where available.

Guide loss reporting

Ask relevant questions about the event, location, parties, injuries, damages, authorities, witnesses, and immediate needs.

Collect supporting records

Receive approved photographs, reports, estimates, receipts, forms, and other evidence and associate them with the intake.

Validate and prepare

Check required fields, duplicates, conflicts, unreadable records, and exceptions, then create a structured FNOL summary.

Create, route, and confirm

After required authorization, post permitted fields, route the intake, and return the system-generated reference where supported.

What Bay6 Helps Claims Teams Manage During Intake

The workflow focuses on complete, structured intake and professional handoff before claim evaluation begins.

Conversational loss reporting

Guide policyholders, claimants, agents, or authorized representatives through insurer-approved questions.

Reporter and policy context

Collect configured identity, contact, claimant role, policy, and insured information and use approved verification paths.

Loss and party capture

Collect event, date, location, vehicle, property, injury, damage, witness, authority, and contact details.

Document and media intake

Accept approved photographs, reports, estimates, receipts, and forms and organize them for the claim file.

Completeness and exception checks

Identify missing fields, duplicate reports, conflicts, unsupported inputs, unreadable records, and escalation conditions.

Structured summary and routing

Prepare a concise intake abstract and route the matter to the configured claims queue or authorized reviewer.

What Insurers Can Improve

Measure whether the intake reaches claims teams faster, with fewer missing items and less repeated work.

Time from first report to review-ready intake
Required-field and document completeness
Intake completion, abandonment, and recontact
Claim setup, assignment, and queue accuracy
Adjuster acceptance and correction volume
Reporter communication, exception handling, and audit readiness

Outcome focus: A governed FNOL workflow collects, validates, organizes, and routes the first report without implying coverage, liability, or claim approval.

Pilot Measurement Areas

Begin with one product, loss type, reporter group, channel, queue, and connected system action.

Measurement Area	What to Track
Intake quality	Completion, required-field coverage, missing information, abandonment, and corrections by loss type and reporter.
Document quality	Successful uploads, classification, readability, duplicate records, missing items, and human-review volume.
Summary quality	Field accuracy, factual consistency, unsupported statements, reviewer acceptance, edits, and corrections.
Processing efficiency	Time to review-ready intake, manual effort, recontact, claim setup, assignment, and throughput.
Routing and escalation	Queue accuracy, emergency and sensitive-case transfers, referral reasons, and downstream reassignment.
Governance	Authentication, consent, source use, system writes, approvals, incidents, complaints, and audit records.

Frequently Asked Questions

Have questions? Browse our FAQs to learn more about how Bay6 AI works and how it supports your organization’s goals.

What is FNOL and claims intake automation?

It uses conversational AI and workflow execution to guide the first report of loss, collect required information and records, validate the intake, prepare a summary, and route the matter for insurer review.

Who can use the intake workflow?

The insurer can configure separate paths for policyholders, claimants, agents, brokers, third parties, or authorized representatives.

Can Bay6 create a claim record?

Yes, where the insurer approves the integration, fields, confirmation, review rule, and system permissions. Creating a record does not confirm coverage or claim outcome.

How are emergencies or sensitive reports handled?

Configured injury, safety, catastrophe, legal, complaint, unsupported, or vulnerable-customer conditions can stop automation and route the matter to the appropriate human path.

What should an initial pilot include?

Use one defined product, loss type, reporter, question set, document set, queue, and system action. Confirm safety messages, required fields, exception rules, ownership, and success measures before launch.

Responsible AI and Claims Intake Oversight

Bay6 AI supports loss reporting, intake preparation, and routing. Coverage, liability, fault, fraud, reserves, severity, settlement, payment, approval, and denial remain with the insurer.

Use only approved products, loss types, reporters, questions, systems, documents, disclosures, and purposes.
Present clear emergency, injury, safety, legal, catastrophic, complaint, and unsupported-situation guidance with human escalation.
State clearly that reporting a loss, receiving a reference, or creating a claim record does not confirm coverage, fault, or payment.
Route missing, conflicting, unreadable, duplicate, low-confidence, sensitive, or legally interpretive information to authorized professionals.
Define authentication, consent, privacy, retention, security, accessibility, state, product, and audit requirements before launch.
Monitor intake quality, summaries, routing, system actions, professional corrections, complaints, and incidents.

Explore More AI Solutions for Insurance

Extend the workflow through counselor task creation, follow-up coordination, system updates, document requests, and enrollment operations handoffs.

EXPLORE agent6

Support lead prioritization, enrollment yield analysis, forecasting, and predictive modeling where usable historical data exists.

EXPLORE model6

Move From First Report to Review-Ready Intake With Less Rework

Review one FNOL workflow and identify where guided questions, document intake, validation, structured summaries, and queue routing can improve the first claims handoff.