Use caseHomeowners insurance

Escalated claim summaries

A $23,400 water claim lands on a supervisor who never opened it: 41 events, an inspection report, eleven emails. Her morning goes into reading.

Every sentence of the summary names its sourceWhere the documents disagree is listed before the decisionThe supervisor decides, with her own authority

The assistantSummary for the decision

A pipe under the bathroom floor leaked into the kitchen below. Reported as sudden on 09/22. Estimates total $24,900, the adjuster proposes $23,400 after the deductible.

source · 38 documents on the case file
Actions on this case file
The supervisor's decision

One figure moves · the supervisor writes why on the case

01

The friction

In two paragraphs

"Please decide this week." That is the last line of Derek Holt's three-line note, written the day he left on two weeks of leave. Behind it sit 41 events of history, an inspection report and eleven emails. Supervisors get exactly these cases: above someone's authority, under complaint, owned by someone who is away. So they skim, call the adjuster, or decide on the note alone. The decision is taken on the part of the file someone had time to read.

Rachel starts instead from a reading she can check. The assistant summarizes the case from inside it, with her own rights, and every statement points to its document and page. It also lists where the documents disagree. Rachel checks the points that matter at their source, and keeps the decision.

Claim HAB-26-03178Case management
41 events, one panel. The case history on the left, the summary beside it, each sentence linked to its document.
EscalationsCase management
Rachel's queue that morning. Four escalated claims, each with the reason it left the adjuster's desk.

A supervisor has seen all of these screens. This time they happen within one half hour: the escalation arrives, the file is read with its sources in the first minutes, the disagreements are checked at their page, and the decision is written down with its reasons. The steps below run from 09:05, when the review opens, to 09:26, when Lucas Moore picks the case up.

02

A case she has never seen

The escalation arrives with a short note, and Rachel reads the whole file with its sources.

Step 1Workflow

The escalation lands in the supervisor's queue

Derek Holt proposes a settlement of $23,400 on claim HAB-26-03178. His authority stops at $10,000, so the process routes the case to a supervisor review. Derek starts two weeks of leave the same day, and his note is three lines long.

Above authority: $10,000Complaint received Nov 7Adjuster on leave
Supervisor review · HAB-26-03178Case management
The review is a child case. Data and documents travel with it, nothing is copied by hand.
The case arrives wholeRachel gets the claim with all 38 documents and every field. Nobody forwards attachments or rebuilds the file for her.
Step 2Assistant

A summary built for a decision, with a source on every line

The history holds 41 events since September 22. Rachel opens the assistant on the case and chooses Summarize. The summary reads the loss report, the inspection report, the estimates, the emails and the adjuster's notes, and each sentence names the document and page it comes from.

Claim HAB-26-03178AI console
Each statement links to its document and page, so any line can be checked in one click.

The fraud team keeps notes on this claim. They sit outside Rachel's rights, so the assistant does not read them for her: permissions apply before the call.

The file is read in the first minutesRachel starts from an account of the whole case, and every line of it can be traced to a document she is allowed to open.
Step 3Assistant

Eleven emails become four dates

The complaint says the company promised an answer by October 31. Rachel runs Summarize the email thread on the eleven messages with Linda Ross. The answer gives four dates she can check, and the one that matters points to Derek's email of October 15.

Sep 23: claim acknowledgedOct 15: answer promised by Oct 31Nov 4: settlement proposedNov 7: complaint
Email Oct 15.msgViewer
The email opens in the browser at the cited sentence, without a download.
Ask any claims supervisor: when a complaint lands on the desk, how long does it take to learn whether the customer is right?
The complaint is checked against what was writtenThe promise is in the adjuster's own words, with its date. Rachel knows the complaint is valid on this point before she replies.
03

Checking at the source

Two points decide the case. Rachel reads both in the documents themselves.

Step 4AI check

The points where the documents disagree

Rachel asks the assistant for the points where the documents contradict each other. It returns two, each with both sources. The leak date is the one that weighs: the loss report says sudden, the inspector's wording is cautious.

Inspection report.pdfViewer
The disagreement is listed with its pages. Weighing it is the supervisor's job.
Disagreements are found before the decisionThey do not surface in a Department of Insurance complaint next spring. Rachel sees both sides of each one, with the page, while she can still act on it.
Step 5Viewer

The exclusion clause, read in the policyholder's own terms

Linda Ross's policy uses the 2023 edition of the homeowners form. Rachel opens it beside the case and asks how the gradual leak exclusion reads. The answer quotes clause 6.3 and sets it next to the inspector's finding.

Homeowners policy form, 2023Viewer
The answer gives the clause and the evidence side by side. It gives no ruling.
The doubt is settled in the policyRachel reads the clause herself, at its page, in the edition this customer signed. Nobody quotes the current brochure by mistake.
Step 6Viewer

A note for whoever opens the report next

On page 6 of the inspection report, Rachel drops a note on the ceiling surface: she keeps the inspector's 130 sq ft over the estimate's 150 sq ft. The note carries her name and the time, and the report itself is left untouched.

Inspection report.pdfViewer
Annotations are stored apart from the original file, with author and timestamp.
The reasoning stays on the pageLucas, who takes the case next, sees why the figure moved without asking anyone.
04

The decision and its trail

Rachel decides within her own authority, and the case moves on with everything in it.

Step 7Case file

The supervisor decides and writes why

Rachel accepts the claim. With 130 sq ft for the ceiling, the settlement becomes $22,860 after the deductible. Her authority goes up to $50,000, so the decision is hers to take. She fills the decision fields in her own words.

Supervisor review · HAB-26-03178Case management
The decision fields are filled by the supervisor. The summary is a reading aid.
A person decides, with a reason on fileThe AI proposed nothing on the amount. The figure, the clause and the reason are Rachel's, signed with her rights.
Step 8Workflow

Derek is away, so the case goes to a colleague

Derek's absence is set in the process, so the delegation picks his replacement in the same team: Lucas Moore. The case comes back to him with the decision, the note on page 6 and the email of October 15 flagged for the reply to the complaint.

Claim workflowCase management
Each stage is a task with its owner and its date.
Nobody waits for the adjuster to come backLucas starts from the decision and the next two tasks. He does not reread forty documents to pick up where Derek stopped.
Step 9History

The summary stays in the history, dated

The case history keeps the summary, the email thread summary and the consistency check, each with its question, its answer, the model used and the time. If the decision is questioned later, anyone with access sees what Rachel read and what she decided.

Claim HAB-26-03178 · HistoryCase management
The trail is part of the case, readable by whoever opens it next.
Audit questions are answered from the fileWhat the supervisor read, which model answered and when, and who decided, all in the history with a time stamp.
05

The outcomes

Rachel had three ways to close this review. The assistant prepared the reading for all three. The choice and the signature were hers.

Approve as proposed

The adjuster's figure stands

The summary and the sources support the amount. Nothing in the file disagrees.

After that: the supervisor signs, the case returns for payment.
Approve with a change

One figure moves, with its reason

Two documents disagree. The supervisor reads both and chooses, as here with the ceiling surface.

After that: the reason is written on the case and a note stays on the page.
Send back for more

A document needed to decide is missing

The consistency check names what the file lacks, such as a plumber's report on the leak date.

After that: a request for information leaves from the case; the review waits for the answer.
Where the AI stops

It approves nothing and refuses nothing. It sets no amount. Across the nine steps on this page, the only binding decision is taken by the supervisor, within her own authority and with her own trace.

The assistant summarizes, lists disagreements and answers with the page. It reads only what the supervisor is allowed to read, so restricted notes stay with the team that owns them.

06

The payoff

Three counts from claim HAB-26-03178 on the morning of November 10. A thinner file would cite fewer sources, a messier one more.

38 sourcescited in one summary, each one a click away from the sentence it supports.
2 pointswhere the documents disagree, listed with their pages before the decision is taken.
0 callsto the adjuster on leave. The case, the note and the next tasks carry what he knew.

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

Three principles behind the figures

Read with sourcesProductivityThe supervisor starts from a summary of the whole case, and every line points to its page.
Rights before the callSecurityThe assistant reads only what the person asking may open. Restricted notes never reach her summary.
Decision supportA person decidesSummaries, checks and answers stay in the history. The decision fields stay with the supervisor.
07

Who it helps

The supervisor feels the change first. Her claims manager and the architect behind the case screen decide whether it stays.

Business operations

Supervisors and senior adjusters

You decide on files you did not build, with a three-line note.

  • The summary covers history, documents and emails, with a source on every line.
  • The email thread comes back as dates you can check.
  • Disagreements between documents are listed with both pages.
  • The policy opens at the clause, in the edition the customer signed.
Risk and compliance

Claims managers and compliance

Escalated decisions get challenged, and today the reading behind them leaves no trace.

  • The AI decides nothing. The decision is the supervisor's, with her rights.
  • Every summary keeps its question, answer, model and time.
  • Restricted notes stay restricted: permissions apply before the call.
  • Notes on documents carry their author and date.
IT and architecture

CIOs and architects

So far, every AI proposal has come with one more platform to run.

  • The assistant opens inside the case screen your teams already use.
  • Summaries are named actions in the case menu, with no prompt to compose.
  • The model is chosen per task and can change without a redeploy.
  • Run it on your own servers or in the cloud, as your claims data policy requires.

How to begin

Pick the escalation queue your supervisors find hardest to read, and add the summary action to that one case type. After a month, ask them whether they would give it back.

Nothing moves out of your case files, your documents or your access rights. The assistant reads them where they are.

Next step

See it on your own escalated cases

Pick a few anonymized cases your supervisors found hard to read. We will run the summary on them with your team and check every source together.

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.