Zero-Hour Processing
How Isomer structures claims data at the moment of arrival — and why timing changes what signals are possible.
Isomer processes and structures every inbound communication at the moment it arrives. There is no overnight batch, no manual trigger, no retroactive pass. The claim graph reflects the current state of every claim in your book as of the most recent message received.
This property — zero-hour processing — is what makes certain classes of detection possible.
The problem with delayed structuring
Most claims systems receive a message and store it. Structuring happens later: an adjuster reads it, a downstream process picks it up, or a batch job runs overnight. During that window, the message sits unprocessed.
For time-sensitive signals, that window is the exposure. A time-limited settlement demand has a deadline. A spoliation notice requires immediate action. A bad faith trigger has statutory timelines. An adjuster who reads the email two days late has already lost time that cannot be recovered.
Delayed structuring means delayed detection. And delayed detection means the signal arrives after the window to act has narrowed — or closed.
How zero-hour processing works
When a message arrives, Isomer immediately:
- Ingests the full original content — email thread, attachments, images, everything.
- Runs document understanding across all content.
- Updates the claim graph with new entities, events, and relationships.
- Evaluates applicable detectors against the updated graph.
- Emits any signals and routes configured actions.
This happens before the message reaches an adjuster's queue. The signal fires the same hour the message arrives.
Lossless evaluation
Zero-hour processing is only as good as the content being evaluated. Isomer evaluates the full original content at the point of receipt — no preprocessing step strips or summarizes the source before structuring runs.
This matters for complex inputs that carry evidence in non-obvious places:
- A forwarded email chain where the relevant language is in a nested attachment three levels deep
- A scanned fax of a handwritten note attached to a PDF packet
- An image of a damaged property embedded in a portal submission
Summarization or preprocessing before structuring would discard this evidence. Lossless evaluation means every byte of the original source is available to document understanding.
Compounding intelligence
Each message that arrives deepens the claim graph. Detection improves over the life of a claim as more context accumulates.
A new competitor starting detection on day one of a customer relationship starts with an empty graph. Isomer's graph for an existing customer reflects every processed message since onboarding. Day-one value plus compounding advantage — a competitor cannot replicate accumulated graph depth retroactively.
This also enables claim-lifecycle detection: signals that require observing how a claim develops over time, not just what a single document says. Escalating medical records following a benign FNOL. Attorney involvement appearing after an initial low-severity report. These patterns only emerge across a populated timeline.
What this means in practice
| Scenario | Without zero-hour | With zero-hour |
|---|---|---|
| Time-limited demand arrives Friday afternoon | Adjuster reads it Monday; deadline has passed | Signal fires Friday; supervisor notified immediately |
| Spoliation notice buried in email attachment | Missed until manual review | Detected at arrival; legal hold initiated same day |
| Attorney representation in a low-severity WC claim | Routed to standard queue | Flagged for specialized handling before first adjuster touch |
| Fraud ring pattern across 12 claims | Identified in quarterly review | Detected as the pattern forms across claims |