Products/Isomer Actions

From signal to done, with your adjusters in charge.

Adjusters carry more files than they have hours. Isomer™ Actions helps them keep up: it routes each signal to the right person, sets out the next best actions as an action plan, and takes on routine work, with the adjuster in charge.

Route

A critical signal reaches the handling adjuster

CriticalTime-limited demand

Dana Lee · policy limits · due Nov 14 · cited p. 9

Routed toK. Ramos, the handling adjuster

Brief

The evidence and context, from the claim graph

Demand letterp. 9

…policy limits if paid within 30 days of this letter.

DeadlineNov 14, 30 days from the letter
CounselJ. Ortiz · 3 prior claims on your book
RelatedDeleted texts flagged Oct 9

Action plan

The next best actions; the adjuster approves

Respond to counsel before Nov 14
Confirm limits with underwriting
Notify the excess carrier
K. Ramos · adjusterApprove 3 tasks✓ Approved

Record

Written to your claim system, with an audit trail

DiaryNov 14 · Demand expires, reminder Nov 7
TaskRespond to counsel · K. Ramos
NoteTime-limited demand received, cited p. 9
AuditApproved by K. Ramos · replayable

From a notification to a workflow.

Start by routing signals, add action plans for what to do next, and hand off routine work when you’re ready.

Route

Notify the right person

Each signal goes to the handler, the supervisor, the litigation team or the recovery unit, by line, severity, and threshold.

Action plan

Recommend the next best actions

An action plan for each critical finding: tasks for the people on the file, each with an owner and a due date, tracked until done.

Workflow

Do the routine work

Multi-step work run for the team: drafting, checking, and entering it in your systems, by API where there is one and through the same screens your team uses where there isn’t. Some tasks start a workflow on their own.

An action plan for every critical claim, from your own guidelines.

When a signal lands, Isomer reads the whole claim and recommends the next best actions as tasks, so deadlines are met, evidence is kept, and costs land where they belong. Routine tasks run on their own and come back for review. Each task cites its signals and guideline, and the plan updates as the claim changes.

Slip and fall at a grocery store · General liabilityAction plan · 4 tasks · 2 by Isomer Agent

Request the vendor’s certificate of insurance 1 signal

Isomer AgentOct 17Done

Draft a preservation letter for the store video 1 signal

Isomer AgentOct 18To review

Tender the claim to the mat vendor’s carrier 2 signals

R. PatelDue Oct 22Open

The service agreement (p. 6) makes the vendor responsible for the entrance mats and names the store as an additional insured. The vendor’s certificate of insurance is now in the file. Tender the defense to its carrier.

Risk signals · 2

Vendor contract names the store as additional insured

Incident report notes a curled entrance mat

Guideline

Contractual Risk Transfer Guidelines

Confirm attorney representation 1 signal

K. RamosDue Oct 24Open

Based on 2 guidelines: Evidence Preservation Letter Procedure, Contractual Risk Transfer Guidelines

Workflows in production.

Some start from a signal; others run on the inbox as work arrives.

First notice · MSIG USA

FNOL intake

New-loss emails become claims in ClaimCenter, with documents uploaded and a status email sent. Incomplete ones go to a person with the reason. 70% straight-through, $500K+ a year saved, and a 100% audit trail.

Defense cost

Legal invoice review

Every line checked against your billing guidelines and what counsel actually filed: 50 to 100 invoices a day.

Expense

Field adjuster invoices

Independent adjuster bills checked against the assignment, the agreed fee schedule, and the reports in the file, before they’re paid.

Recovery

Closed-claim subrogation

A review of closed claims for recoveries that were missed, alongside the subrogation signals that route new opportunities as they arrive.

Built from how your team already works.

No requirements project. Action plans follow your own guidelines, and each workflow learns from the work your experienced staff have already done, so what they know stays with the team.

Step 1

Train

Replay past work and compare the results with what your team actually did.

Step 2

Shadow

Run on live claims, read-only, next to your team’s decisions.

Step 3

Produce

Go live. Your rules set what runs on its own, and the rest goes to a person to approve.

You keep control of policy rules and approval authority. Every step is logged and replayable, and results go where your team works: the claim system, the document store, or email, through an API or the same screens your team uses, so there’s no integration project to start.

Walk through an action plan.

Thirty minutes with our team on synthetic claims: a signal, the action plan it sets out, and the record it leaves. Most customers start with Signals and add Actions when they’re ready.