Subrogation recovery
Closed claims scanned, the at-fault party's insurer identified, and the demand sent after counsel approval.
Subrogation recovery is an agent scenario in the Insurance sector running on the batch, email, api channels. Trigger: Weekly batch: motor claims closed in the last 90 days. The Subrogation Supervisor coordinates 3 specialist agents (Liability Scan Agent, Evidence Agent, Recovery Agent) across 4 systems (Guidewire ClaimCenter, Document Store (S3), Insurance Registry (SBM), Email (Exchange)); of 10 steps, 1 write to systems and 2 are checks or approvals. Outcome: Recovery case open, demand letter with the counterparty insurer, 30-day follow-up scheduled. Approval rule: Recovery demand > 50,000 → subrogation counsel approval.
Subrogation recovery
- Weekly batch: 1,240 closed motor claims scanned for subrogation
- Claim #CL-2026-104877: 86,000 paid, third party 100% at fault (accident report)
- Plan: evidence pack → counterparty insurer → demand letter → approval → send
- Accident report, photos and repair invoices retrieved (11 documents)
- Third-party vehicle 06 XYZ 456 → liability insurer found in the registry, policy active
- Demand letter drafted: 86,000, interest from 14 Apr, legal basis cited
- Limitation: within 2 years · amount reconciles with the file · legal basis correct
- Demand > 50,000 → subrogation counsel approved the letter
- Recovery case #SR-8817 opened, expected recovery 86,000
- Demand letter emailed to the counterparty insurer, 30-day follow-up scheduled
- ■completed
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
Weekly batch: motor claims closed in the last 90 days
Recovery case open, demand letter with the counterparty insurer, 30-day follow-up scheduled
Agents
Subrogation Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Liability Scan Agent
Scores third-party liability across closed claims
get_closed_claimsscore_third_party_liabilityget_accident_reportEvidence Agent
Summarises evidence and drafts the demand letter with legal basis
fetch_claim_documentssummarise_evidencedraft_demand_lettercheck_limitation_periodRecovery Agent
Finds the counterparty insurer, opens the recovery case, sends the letter
lookup_insurercreate_recovery_casesend_emailschedule_followupSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | Subrogation Supervisor | Weekly batch: 1,240 closed motor claims scanned for subrogation | — | 340 | — |
| 02 | reason | Liability Scan Agent | Claim #CL-2026-104877: 86,000 paid, third party 100% at fault (accident report) | — | 820 | 760 |
| 03 | plan | Subrogation Supervisor | Plan: evidence pack → counterparty insurer → demand letter → approval → send | — | 280 | 200 |
| 04 | retrieve | Evidence Agent | Accident report, photos and repair invoices retrieved (11 documents) | Document Store (S3) | 420 | — |
| 05 | tool | Recovery Agent | Third-party vehicle 06 XYZ 456 → liability insurer found in the registry, policy active | Insurance Registry (SBM) | 460 | — |
| 06 | reason | Evidence Agent | Demand letter drafted: 86,000, interest from 14 Apr, legal basis cited | — | 1,300 | 1,580 |
| 07 | verify | Evidence Agent | Limitation: within 2 years · amount reconciles with the file · legal basis correct | — | 520 | 440 |
| 08 | approval | Subrogation Supervisor | Demand > 50,000 → subrogation counsel approved the letter | — | 3,200 | — |
| 09 | write | Recovery Agent | Recovery case #SR-8817 opened, expected recovery 86,000 | Guidewire ClaimCenter | 480 | — |
| 10 | notify | Recovery Agent | Demand letter emailed to the counterparty insurer, 30-day follow-up scheduled | Email (Exchange) | 260 | — |
End-to-end motor claim: from notice to payment
Voice notice, photo assessment, repair-shop assignment and payment order in one flow; the adjuster steps in only above the threshold.
Voice claims intake (FNOL)
The customer calls and describes it; policy found by plate, cover checked, claim opened and adjuster assigned.
Policy renewal offer
Policies re-priced, sharp increases go to approval; customer accepts with one tap and the policy is issued.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis