Insurance

Claims Adjuster Copilot

Designed for Claims adjuster

Help a claims adjuster reach a defensible coverage and reserve decision faster by unifying the first notice of loss, policy terms, damage evidence, and repair estimates with mandatory human sign-off on payments.

Contract INS-01 · primary aggregate ClaimFile · mode loading

Decision brief

Approve payment or denial: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Claims adjuster and supervisor

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

A hail claim on a commercial roof arrives with 40 drone photos and a 180,000 dollar contractor estimate; the copilot binds the endorsement in force at the loss date, flags the cosmetic-damage exclusion, shows a 22 percent labour variance against guideline, and the supervisor approves a reduced settlement with the cited clauses attached..

Decision to make

Help a claims adjuster reach a defensible coverage and reserve decision faster by unifying the first notice of loss, policy terms, damage evidence, and repair estimates with mandatory human sign-off on payments.

Outcome to show

Authorized payment or issued denial letter gives Claims adjuster and supervisor the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Intake first notice of loss
  2. 2Bind policy terms in force at loss date
  3. 3Analyze damage evidence and estimates
  4. 4Draft the coverage position and reserve
  5. 5Approve payment or denial

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Claims adjuster and supervisor verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved ClaimFile evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Help a claims adjuster reach a defensible coverage and reserve decision faster by unifying the first notice of loss, policy terms, damage evidence, and repair estimates with mandatory human sign-off on payments.
Primary aggregate
ClaimFile
Primary container
claimFiles
Hierarchical key
/tenantId + /claimId
Schema version
1

Sample scenario

A hail claim on a commercial roof arrives with 40 drone photos and a 180,000 dollar contractor estimate; the copilot binds the endorsement in force at the loss date, flags the cosmetic-damage exclusion, shows a 22 percent labour variance against guideline, and the supervisor approves a reduced settlement with the cited clauses attached.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
claimFiles Primary /tenantId + /claimId ClaimFile, PolicySnapshot, DamageEvidence, RepairEstimate, CorrespondenceThread, CoverageAssessment

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
ClaimFile claimFiles /tenantId + /claimId claim::{claimId} None
PolicySnapshot claimFiles /tenantId + /claimId policysnapshot::{claimId}::{policyVersion} endorsementTextVector
DamageEvidence claimFiles /tenantId + /claimId evidence::{claimId}::{evidenceId} observationVector
RepairEstimate claimFiles /tenantId + /claimId estimate::{claimId}::{estimateId} None
CorrespondenceThread claimFiles /tenantId + /claimId correspondence::{claimId}::{messageId} bodyVector
CoverageAssessment claimFiles /tenantId + /claimId coverage::{claimId}::{assessmentVersion} assessmentVector

Query patterns