Use case · Subrogation

The recovery was in the file. It just closed first.

The fault you set to pay the claim is the same one that proves recovery. Mysa re-reads the closed file and hands your team a demand ready to send — the call stays theirs.

See how
Send a batch of closed files · first sweep on us
On this closed file
1
Re-read it for recovery
Pull the report, statements and estimate already in the file into Recovery Review.
Gap agent — reads every data point in the file and flags what's missing or unclaimed: diminished value, storage, the second estimate.
2
Set the liability call
Apply your state's rule to the fault already established.
Research agent — cross-checks the adverse carrier and the last twelve like it on your book into Liability.precedent.
3
Assemble & route the demand
Compose it with proof of payment and exhibits into Demand — blocked until it's whole.
Dispatch agent — sends each piece where it's owed: the demand to the adverse carrier, the filing to the Forums, before the deadline.
Suggested by your decision graph
Reopen for recovery before this stays closed.
Source the at-fault third party here is the named insured on 2 other files you've already paid.
Why the recovery only appears when the three closed files are read together.
Recovery deskLIVE
Re-readDecideDefendRemember
Automated · agentsYour call

Identification, the liability call and the demand ran on their own, off the evidence already in the file. What's left is your call.

Recovery readiness
Recoverable file identified
Third party at fault · adverse carrier found
Liability call set for recovery
TP 100 / insured 0 · comparative rule · 0.94
Demand assembled
Proof of payment · 4 exhibits · complete
Deadline
SOL 14 months · Arbitration Forums window open
Next actions queued
File with the Forums · notify adverse carrier
Diminished value not claimed on 3 similar files last quarter. Worth adding here.
Recovered in 11 of 12 matched rear-enders on your book.
Recovery-ready

Finding it is hard. Keeping it on the rails is harder.

Spotting the recoverable file among hundreds of closed ones is real work — and it's only the start. Then the priority slips, the statute clock runs, and the demand lands half-built. Mysa surfaces it, tracks every deadline, and chases what's missing until it's ready to send.

ClaimPaidFaultRecoverable
RE-44716,200Insured
RE-44729,840TP 100recoverable
RE-44734,110Split
RE-44747,530Insured
RE-44758,420TP 100DV unclaimed
RE-44765,190Insured
Recovery opportunity · RE-4475~1,900

unclaimed diminished value, on 8,420 paid

Why it's recoverable

11 of 12 comparable rear-enders on your book recovered diminished value. This one closed without claiming it.

Next steps

Add diminished value to the demand, file with the Forums before the 8-month clock, and notify the adverse carrier.

Surfaced by the Research agent — from the pattern across your book.
How it works

Every fact in the file, wired to the call it proves.

Drawn from the evidence you already gathered — and the last twelve like it on your book.

Re-read

The file that closed no-sub

The recovery you lose is the one that closed before anyone read it for recovery. Mysa re-reads every closed file for the fault it already established.

Recovery review
Closed-file sweep
RE-4471 · closed, no-sub
RE-4472 · third party at fault
RE-4473 · closed, no-sub
1 recovery still live
Decide

The same call, every time

The fault that paid the claim proves the recovery. Mysa applies your state’s rule the same way on every file, and cites the precedent behind it.

Research agent
Liability, for recovery
Rear-end · TP ran the light
Comparative rule applied
11 of 12 like it recovered
TP 100 / 0 — every time
Defend

Complete before it’s sent

Recoveries lose on a gap, not in argument. Mysa won’t release the demand until the proof, the exhibits and the deadline are all in place.

Recovery agent
Completeness check
Proof of payment
Exhibits attached
SOL / Forums window clear
Demand complete

Starts with your rules. Sharper every file.

Day one it runs your guidelines — no data of yours needed. Every call your team makes, it captures. Over time it comes to decide like your book, and that judgment stays when your people leave.

Day one Your rules, encoded
Your guidelines, applied the same way from the first file. No data of yours to start.
Every call Their judgment, captured
Every call your team validates is remembered — the senior instinct, written into the graph.
Over time Decides like your book
It comes to call it like your best people would — and it stays when they leave.
day oneevery calldecides like your book
On your terms

Your files. Your call.

Sovereign by design

Your cloud, on-prem, or your VPC. Closed files never leave.

Your team keeps the call

Mysa assembles; your team signs off. Nothing sent on its own.

Defensible by construction

Every call cites its evidence and rule, logged for the Forums.

Common questions

How does Mysa find recoveries we missed?

It re-reads your recently closed files with the recovery question the original adjuster never had time to ask, and surfaces the ones where a third party is at fault and a recovery is still live — before the deadline passes. Subrogation

Is this accurate, or just another liability score?

US fault is a judgment call, not a lookup, so we don’t claim "accuracy" against a number that doesn’t exist. We deliver consistency: the same fact pattern gets the same call every time, measured against your own settled outcomes. Liability decision

Does Mysa file or send anything on its own?

No. It assembles the demand and the proof chain and hands it to your team; the decision to pursue and send stays with a human. It is a human-in-the-loop system. Human in the loop

How do we start without handing over data?

Send a batch of recently closed files and we run the first sweep on us — you see the recoverable ones with the liability already worked, before any commitment.