AI agents that handle
your insurance
company’soperations

Request a demoSee what it does

Built by a team from

  • Google
  • Microsoft
  • Amazon
  • Heroku
  • Salesforce
  • Docker
  • PayPal
  • University of Chicago
  • Stanford University
  • The Wharton School
  • PwC
  • FOSSA
  • Khan Academy
  • SailGP
  • LexisNexis

Product capabilities

Four parts of claim work. One source record.

Choose a workflow and inspect the evidence, deadlines, prepared work, and named human review boundary. Every file shown is fictional.

Loading capability demo

What it does

First notice of loss, taken by an agent

Sentanis answers the phone, in English, Spanish, or Mandarin, records the loss the way an intake specialist would, and opens the file. It notes where the story changes between the first telling and the second, and routes those calls to a person before anything else happens.

Inbound call · 2 min 40 sFICTIONAL

JamieWas anyone in either car hurt?

CallerNo, nobody was hurt. It was a tap at the light.

JamieHas anyone seen a doctor since?

CallerMy passenger went to a chiropractor Tuesday.

InconsistencyInjury: none at 0:48, treatment at 2:10. Routed for staff review.
Evidence lineage preserved

Every claim, already read

A standing brief on every open file: what it is, where it stands, what it needs next. It is built from everything in the file, estimates and claims-history reports included, and it orders the adjuster's worklist. It never disposes of anything; it tells the adjuster where to look first.

Standing brief · 25GENTX2008614FICTIONAL

Rear-end at a controlled intersection, TX, clear liability. Claimant represented since day 9. Bills $21,400 against $6,900 paid; treatment cadence outruns the reported impact.

Needs next: confirm the tender position before Mar 21.

Decision ready66 files read · Mitchell estimate · ISO ClaimSearch report · 41 billing lines
Evidence lineage preserved

Demands answered, not just received

The deadline is read out of the letter and calendared before anyone opens the file. The bills are taken apart line by line. A response is drafted with every authority verified, and it waits for counsel to sign.

Time-limited demand · received Feb 16FICTIONAL
Deadline30 days from receipt. Expires Mar 18. Calendared on day 0.
Bills$18,240 billed, $6,910 paid, four duplicate lines.
ResponseDrafted. Three authorities verified. Waiting for counsel’s signature.
Named professional required

One file for the adjuster and the lawyer

Every claim is read from a legal and litigation perspective from the day it opens. Counsel and adjusters work from the same brief, the same chronology, the same deadlines, each with their own gate. There is no handoff, because nothing has to be handed over.

Shared claim viewFICTIONAL

Adjuster

Records the tender decision.

Counsel

Reviews, edits, and signs the response.

Both see: the standing brief, the chronology, the deconstructed demand, the calendared deadlines, and every decision recorded so far.
Named professional required

How it works

Paper goes in at the bottom. Decisions come out at the top. People stay in charge. Pick a layer.

Runs on your infrastructure. Nothing leaves on its own.

Claims intelligence

The standing brief on every claim. The deadline watch. Fraud signals and SIU triage. Demand deconstruction and drafted responses. Citation verification on every authority. All of it advisory: it tells a person where to look and what it found.

  • Standing brief
  • Deadline watch
  • Fraud signals
  • Demand deconstruction
  • Draft responses
  • Citation verification

Safety and trust

The AI never denies a claim, rejects a demand, contacts a claimant, files with a court, releases a document, or signs anything. That is wiring, not policy. So is the rest of this. Read the trust pages

Documents are evidence, never instructions

A demand letter is written by someone who would like your system to do what it says.

  • Every model call runs through one gateway with a registered task profile and a policy no prompt can override. Undeclared tools are refused before anything leaves.
  • Correspondence, attachments, tool results, and the model's own earlier output enter every call labeled as untrusted evidence with their lineage attached.
  • Capabilities are checked at the moment of use against the person's actual claim scope. Model-written arguments cannot widen it, and a report needs a person to ask for it.

Nothing unverified leaves the building

More than 1,500 court decisions now involve fabricated AI citations.

  • An independent assessor may call a proposition supported, contradicted, or unchecked. It cannot invent a source, a quote, a pinpoint, or currency; deterministic server checks decide.
  • Verified means one canonical source, complete versioned text, the passage at the pinpoint, matching jurisdiction and date, current treatment, and grounded facts. Anything less is needs-review.
  • Every sentence of the draft is inventoried, and each proof binds to the exact revision counsel signs. Edit the letter and the proof is void.

Secure by construction

The database enforces access, not the interface.

  • Names, contacts, source records, and document text are encrypted at the field level; row-level security and per-claim grants decide who sees what.
  • Every decision and every look at a file lands in an append-only audit trail tied to a named person.
  • Party names are redacted before any external model call, and again on the way back, so a name reconstructed from context never becomes the first unredacted copy on file.

Weeks to value, not quarters

The foundation is not on the schedule. The workspace, document intelligence, the deadline watch, and demand deconstruction are built and running. What remains is tuning to your book.

  1. Week 1

    Your closed files land on infrastructure you control. Outcome labels agreed.

  2. Week 3

    The scorecard: every demand caught or missed, every call right or wrong, on your own history.

  3. Week 20

    Full deployment, every phase gated on measured accuracy rather than the calendar.

Your claims platform

A source adapter reads claims and attachments from the system you already run, so nothing is re-keyed. Snapsheet today; the same adapter takes the next one.

Your data lake

Documents stay in your own object storage. Sentanis reads from it and writes lineage back; it does not become a second copy of your book.

Your cloud account

Deploys into customer-isolated AWS accounts with your own keys, backups, and logs. Claim data never leaves infrastructure you own.

Human review begins here

See it on a claim file that looks like yours.

A demo walks through first notice, the standing brief, a demand and its response, and the shared view counsel and adjusters work from. Then, if you want the numbers, a shadow evaluation on your closed files replaces every figure on this page with your own.

Request a demo