Use caseAuto insurance

An auto claim handled in full

A car claim arrives with four files and one gap: the driver is not on the policy. The adjuster finds it on day five, and the customer has waited.

The AI checks the file before anyone opens itThe missing document is asked for on day oneA person decides, every time

The verdict on the file

One point needs a person · the AI says which, with its source

Actions on this case file
The assistantCompliance check

The policy is active on the date of loss and the estimate matches the photos. But the driver on the police report is not named on the policy: Ethan Morris.

source · 4 documents on the case file
01

The problem

The whole thing in one move

Day five. Justin opens Claire Morris's claim for the first time and sees what nobody saw at intake: the driver on the police report, Ethan Morris, is not named on the policy. The file was never wrong. It was one signed statement short, and the customer has waited a week for a request that could have gone out the first morning.

Move the check to the door. The AI runs the company rules the moment the claim arrives, names the point that blocks, and drafts the request. The adjuster starts from a verdict and its reasons, and keeps the decision.

Claim CL-26-08817Case management
One gap, named on arrival. The claim fields on the left, the AI verdict on top, the case documents one click away.
My claims queueCase management
Justin's morning queue. The same claim among the others, sorted by AI verdict like any other field.

An adjuster already works with a claim form, a queue, a policy and a draft. The gain comes from the order they arrive in: the claim arrives already checked, the gap is chased the same morning, and the decision is taken on a complete file. The three acts below follow CL-26-08817 until the case closes.

02

The intake

The claim arrives, and the AI has checked it before anyone opens it.

Step 1Intake

The claim arrives through the API, with its documents

Claire Morris reports a rear-end collision from the customer portal and uploads four files. The portal calls the repository API: a claim case is created, and each document is filed under its type.

Police reportTwo damage photosRepair estimate
Claim CL-26-08817 · DocumentsCase management
Each document is typed on arrival, so the checks know what to look for.
The file is in one place from minute oneNo email to forward, no attachment to save. The claim and its documents land together, typed, in the right queue.
Step 2AI check

The AI runs the company rules before anyone else

Before anyone opens it, an AI agent runs the claim against the rules the claims team wrote, in plain language.

Is the driver named on the policy?Was the policy active on the date of loss?Does the estimate match the reported damage?

The result is written onto the case in two fields: a status, and the reasoning in plain words. Here the status is Attention required: the driver on the police report, Ethan Morris, is not named on the policy.

Claim CL-26-08817 · AI analysisAI console
The warning points to the line and page it comes from.
The gap is found at the doorNobody reads the file to discover the problem on day five. The point that blocks is named before the adjuster starts.
Step 3Reporting

The queue arrives sorted by verdict

Justin opens his home page. One of his reports counts the open claims by AI verdict, and his queue can be sorted on that column like any other field.

Complete: 24Attention required: 9Not eligible: 3
My claims queueCase management
The AI verdict is a column you can sort and filter on.
The team lead sees where the human work isThe verdict is a reporting axis. The claims that need a person stand out the moment the day starts.
03

The gap

One point stands between this claim and a decision: a driver the policy does not name. Three steps to close it.

Step 4Viewer

Check the warning in the policy itself

Justin opens the policy in the viewer, next to the case. He asks the assistant which clause covers permissive drivers, and the answer points to the page.

Policy AUT-88213-04.pdfViewer
Each answer cites its page, so the adjuster checks the source in one click.
Time it on your next doubtful claim: how long does the clause that settles it take to find, and how often does the file go back unread?
The doubt is settled in the documentNo second application, no download. The policy opens beside the claim, and the answer comes with its page.
Step 5Assistant

The request is drafted from the file

Justin asks the assistant for a request to the policyholder. The draft names the missing document and explains why, with the policy number already in it. He changes one sentence and sends it.

Claim CL-26-08817Case management
The request is filed in the case history, with its date.
The customer hears about it the same morningThe gap is chased on day one, with a message that says why. Nobody waits a week to learn that a signature was missing.
Step 6AI check

The statement arrives and the check runs again

The next morning the signed statement comes in from the customer portal. It is filed on the same case, the analysis runs again, and the status moves to Complete.

AI analysis resultsAI console
The earlier warning stays in the history: the trail shows how it was cleared.
The file comes back readyJustin does not reread everything. The claim returns to his queue with the verdict that changed and why.
04

The decision

The claim is complete, and the decision belongs to the adjuster.

Step 7Assistant

A summary to decide on the whole file

Justin asks for a summary of the claim. It lists what happened, who drove, what was received and when, each line with its source document.

Claim CL-26-08817AI console
The summary helps the reading. The decision fields stay with the adjuster.
The decision is taken on all of itNot on the part someone had time to read. Every line of the summary can be checked against its document.
Step 8Workflow

Above the adjuster's limit, the file moves up whole

Had the amount been above Justin's authority, one action would have launched a supervisor review as a child case. Every document and every field travel with it.

Authority limit: $5,000This claim: $1,840
ProcessCase management
Each stage is a workflow task with its owner and its date.
Escalation is one choiceThere is no email with five attachments to put together. The process carries the case and everything in it.
Step 9History

The case closes with its full trail

Justin validates. The case closes, and its history keeps every document version, every AI analysis and every human action, dated and attributed.

Claim CL-26-08817 · HistoryCase management
The trail is part of the case, readable by whoever opens it next.
Audit questions are answered from the fileWho checked what, when, and on which document: the history answers before the auditor finishes asking.
More on thisContent governance
05

The outcomes

There is no score out of a hundred here. Each claim gets one of three verdicts, and Justin's queue treats each one differently.

Complete

Every rule passes

Policy, period, driver, damage. The case records in one line that each rule held.

Next: the adjuster checks, decides and closes.
Attention required

One point needs a person

A driver not on the policy, a document missing. The analysis says which, with its source.

Next: the adjuster requests the piece; the check runs again when it arrives.
Not eligible

A rule fails, and you know which

The AI lists what is fine first, then names the point that blocks.

Next: a letter drafted from the file, reviewed and signed by the adjuster.
What the AI does not do

It refuses nobody. It pays nobody. It closes no file. Across the nine steps on this page, the only binding decision is taken by the adjuster, with their own rights and their own trace.

The AI checks, drafts and summarizes. The control is in how the process is written, so it holds when volumes rise.

06

What it saves

Counted on Claire Morris's claim, four files and one missing statement. Your own volumes and checklist will move these counts.

0 linesretyped from the documents. The claim fields come from the portal and the analysis.
Day 1when the missing document is requested, instead of the day the file is first read.
1 clickto escalate with every document attached, when an amount is above the adjuster's limit.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

The three principles behind those numbers

Zero wasted readingProductivityThe check runs before the human review. The adjuster starts from a verdict and its reasons.
Zero lost documentsProcess reliabilityRequests, replies and analyses live on the case. No file sits in someone's email.
Decision supportA person decidesSummaries and answers cite their sources. The decision fields stay with the adjuster.
07

Who it is for

An adjuster, a team lead and a CIO each have to be convinced before a claims check moves to the door.

Business operations

Claims adjusters

Reading and chasing eat the day, and deciding gets squeezed into the last hour.

  • The claim arrives checked, with the point that blocks already named.
  • The request to the customer is drafted with the right numbers.
  • The policy opens next to the claim, and answers cite their page.
  • The summary lists every fact with its source document.
Risk and compliance

Team leads and compliance

Approving something you cannot inspect is a hard sell to your own committee.

  • The AI decides nothing. The decision is human, with its rights.
  • The verdict is a sentence that names the rule it checked.
  • Every analysis stays in the case history, dated.
  • The rules are yours, written in plain language.
IT and architecture

CIOs and architects

So far, every AI proposal arrived with another platform to run.

  • The claim comes in through the API, from your existing portal.
  • The AI check runs as one step of your claims process.
  • The check answers in real time, or in batches when the queue is long.
  • Install it on your own servers or run it in your cloud.

Where to start

With one rule. Take the check your adjusters do by hand on every claim, and move it to the door. A single rule shows its worth within a month of claims.

Your customer portal, your case files and your documents keep their place. The check plugs into them.

Next step

See it on your own claims

Bring a few anonymized claims and your checklist. We will check them at the door with you, and leave every decision to your adjusters.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.