Skip to main content
Every claim arrives with a stack of documents — FNOL forms, police reports, medical bills, repair estimates, photos, and correspondence. Adjusters spend significant time simply identifying what each document is before they can process it. When documents are mislabeled or filed incorrectly, it causes delays downstream: the adjuster looking for the police report does not realize it was uploaded as “miscellaneous attachment #3.” This use case deploys an agent skill that reads uploaded documents, identifies their type, and categorizes them in the claims management system. When a claimant uploads a batch of files, each one is automatically labeled and linked to the correct claim section. Missing required documents are flagged immediately so the adjuster can request them before the claim stalls.

​
What you need

Data sources

  • Claims management system — Claim records with document attachment fields and required document lists by claim type
  • Document management system (if separate) — Repository where uploaded documents are stored with metadata fields

Knowledge spaces

  • Claim documents — The uploaded documents themselves (FNOL forms, police reports, medical bills, repair estimates, photos, correspondence)
  • Document classification guide — Upload your document type definitions, naming conventions, and examples of each document type
Semantic layer: Define these in your ontology before setting up the agent.
ComponentNameDefinition
ObjectClaim DocumentMaps to document attachment records. Represents a single uploaded file with type, status, and linked claim
ObjectClaimMaps to the claims management system. Provides context on what documents are required for each claim type
MetricDocument CompletenessNumber of received required documents divided by total required documents, as a percentage
MetricClassification ConfidenceThe confidence level of the automated document type assignment
DimensionDocument TypeCategories: FNOL form, police report, medical bill, repair estimate, photo/video, correspondence, identity document, other
DimensionDocument StatusTracks whether a document is received, classified, reviewed, or missing
See building a semantic layer for a step-by-step guide.

​
Agent setup

1

Create the agent

Go to Agent Space > New agent.
FieldValue
NameDocument Classifier
RoleClaims document classification specialist
GoalAccurately identify, categorize, and organize uploaded claim documents
2

Set the description

You classify documents uploaded to insurance claims. Read each document and assign it to the correct document type category. Use the document classification guide as your reference. When confidence is low (the document does not clearly match a known type), assign it as “other” and flag it for manual review rather than guessing. After classifying all documents on a claim, check the required document list for the claim type and identify any missing documents. Be precise with document type labels — use the exact categories from the classification guide.
3

Scope data access

Grant access to:
  • Claims management system data source (claim records and document lists)
  • Document management system data source (if separate)
  • Claim documents knowledge space
  • Document classification guide knowledge space
  • Claim Document and Claim objects in the semantic layer
4

Add skills

Trigger: New documents uploaded to a claim or user asks to classify documents
  1. Retrieve the uploaded documents from the knowledge space for the specified claim.
  2. Read each document and analyze its content, structure, and formatting to determine the document type.
  3. Assign each document to a category: FNOL form, police report, medical bill, repair estimate, photo/video, correspondence, identity document, or other.
  4. For each classification, note the confidence level: high (clear match), medium (likely match), or low (uncertain).
  5. Flag any document classified as “other” or with low confidence for manual review.
  6. Update the document record in the claims management system with the assigned type and confidence level.
Trigger: After documents are classified or user asks about missing documents
  1. Look up the required document list for the claim type from the claims management system.
  2. Compare the list of received and classified documents against the required list.
  3. Identify any required documents that have not been received.
  4. For each missing document, note the document type and its importance to claim processing.
  5. Generate a missing document request listing exactly what the claimant needs to provide.

​
Automation

​
Playbook: Auto-classify on upload

1

Set the trigger

Set the playbook to trigger on a document upload event from the claims management system or document portal.
2

Build the workflow

The playbook classifies each uploaded document and updates the claim record immediately.
  1. Query step — Pull the uploaded document and the associated claim details (claim number, claim type).
  2. AI step — Analyze the document content and classify it into the appropriate document type using the classification guide.
  3. Action step — Update the document record in the claims management system with the assigned type and confidence level.
  4. Query step — Check the required document list for the claim type and determine if any required documents are still missing.
  5. Condition step — If all required documents are now received, update the claim status to “documents complete.” If documents are still missing, add a note listing what is needed.
3

Configure delivery

When all required documents are received, send a notification to the assigned adjuster that the claim is ready for review. If documents are missing after 48 hours, send an automated request to the claimant listing the specific documents needed.
4

Test and activate

Click Run now to test with live data, then toggle to Active.

​
What’s next

Policy coverage verification

Cross-reference claim details against active policy terms to confirm coverage.

All insurance use cases

See the full list.