How Isomer Works

A conceptual overview of Isomer's pipeline — from inbound communication to structured claim data, risk detection, and automated action.

Isomer is a managed AI platform for insurance claims operations. Every product in the platform is built on a single pipeline: ingest a communication, understand its content, map it onto a structured claim graph, and surface that structure to detection and workflow layers.

The pipeline

Inbound communication
        ↓
    Ingestion
        ↓
 Document understanding
        ↓
    Claim graph
        ↓
 Signals  |  Actions

Ingestion

Every inbound message — regardless of channel — enters through a single pipeline. Supported channels:

  • Email (Microsoft 365, Google Workspace)
  • Voice transcript
  • Fax
  • API feed
  • Portal submission

Document understanding

Isomer reads the full original content at the point of receipt: complete email threads with nested attachments, scanned faxes, multi-page PDF packets, images of damaged property. Nothing is summarized or stripped before structuring.

Claim graph

Processed content maps onto a pre-built, ACORD-aligned insurance ontology and populates a customer-specific claim graph. The graph spans every claim in a customer's book and captures:

  • Claim and loss details
  • Involved parties (claimant, insured, counsel, providers, adjusters)
  • Policies and coverages
  • Documents and attachments
  • Timeline of events (FNOL, treatments, legal filings, communications)
  • Relationships connecting all of the above

Signals

Isomer Signals evaluates the claim graph against a library of 85+ detectors and emits a structured signal for every match — carrying source evidence, urgency, confidence, and configured action.

Actions

Isomer Actions runs multi-step workflows triggered by a Signal or standalone on an inbound message. Use prebuilt templates or build your own.

Key properties

Zero-hour processing. Structuring happens at arrival, not retroactively. Signals fire the moment a message is received — not after it has sat in an adjuster's queue.

Lossless. The full original content is evaluated at the point of receipt. No summarization, no preprocessing that could drop evidence.

Compounding intelligence. Each processed message deepens the claim graph. Detection improves over the life of a claim as more context accumulates.

Access methods

Isomer Core exposes three access methods, used by both Signals and Actions internally and available to external consumers:

Method Best for
API HTTP access from any language or system
MCP Direct agent integration via Model Context Protocol
CLI Scripted workflows and terminal-driven operations

External teams building their own AI agents can consume Core directly — same ingestion, same ontology, same claim graph — without using Signals or Actions. See Core as infrastructure.

Next steps