AI Agents

Operations

Claims Intake Agent

Takes the first notice of loss on any channel and opens a complete claim file the adjuster can work.

In productionReviewed September 3, 2026
WhatsApp · Claims Intake
Demo data
  1. Policyholder

    Somebody hit my car in the parking lot. I have photos but I do not know what else you need.

  2. Agent

    The three photos are legible. For this coverage I still need the other driver's plate and a photo of your license, and then I can open the claim now.

  3. Claims system · claim 2026-40871 opened · 5 documents attached · checklist complete · adjuster assigned
  4. Handoff to a person

    Whether the claim is covered is never stated by the agent: the adjuster gets the complete file and makes that call.

WhatsAppClaims systemCore / policy adminTelephony
KPI it moves
Intake in 6 to 11 minutesMeasured
Channels
VoiceWhatsAppEmail
Integrates
  • Claims system
  • Core / policy admin
  • Telephony
  • Shared folders / API
A driver photographing a dented car on the shoulder of a highway
Operations

What it does

First notice of loss on any channel. A complete file for the adjuster.

Where it lives

Your cloud, your repo, your IP.

1. Receives 2. Looks up 3. Decides 4. Acts 5. Escalates 6. Learns

Channels

  • Voice
  • WhatsApp
  • Email

Claims Intake Agent

03Decides

Systems it integrates

  • Claims system
  • Core / policy admin
  • Telephony
  • Shared folders / API

A person on your team

01

Receives

Takes the first notice by phone, WhatsApp or email and identifies the policy and the coverage.

02

Looks up

Reads the policy, its status and the document checklist that this claim type requires.

03

Decides

Asks only what is missing, checks each photo or file is legible and flags the inconsistencies.

04

Acts

Opens the claim in the system of record with the file attached and tells the person what follows.

05

Escalates

Routes injuries, suspected fraud and anything above the amount you set to an adjuster at once.

06

Learns

Turns every returned file into a checklist fix so the same document stops going missing.

KPI it moves

Measured, with the source.

Every figure has a row in the Proof Ledger: source, date, owner and client permission.

Proof Ledger
Measured

Measured

6 to 11 minutes

Time to a complete claim file

Range observed across deployments of this agent, Sep 2026

Measured

70% to 88%

Files complete at first pass

Range observed across deployments of this agent, Sep 2026

Measured

Down by half or more

Rework caused by missing documents

Range observed across deployments of this agent, Sep 2026

Before

Baseline

After

Half or less

Reviewed September 3, 2026

How it is governed

Every action has an owner, an eval and a limit.

Set in the Blueprint, enforced by the Govern layer of the platform.

Govern · Approval queue
Demo data

Waiting for a person

Reserve amount on claim 3391 · the adjuster decides

File complete · 14 photos, 2 documents

Weekly eval

Passing

File completeness against the checklist

96.7%

Last 8 runs
93.6% → 96.7%

Empathy and script compliance · weekly sample

Limit, enforced

Coverage question routed to the adjuster

Human approvals

  • Coverage decisions, always by an adjuster
  • Any payment or reserve amount

Typical evals

  • File completeness against the adjuster checklist
  • Extraction accuracy on documents and photos

Limits

  • It never states whether a claim is covered
  • PII and medical data masked before any model call

Time to production

8 to 12 weeks

of pilot to production under a KPI Contract, after a Blueprint of 1 to 2 weeks

The agent already runs in production elsewhere, so the 2 to 4 weeks of tuning inside the pilot go to your policies, your data and your systems, not to the model.

DaCodes delivery standard, Sep 2026. Integration is the long pole, not the model.

How we deploy
The four phases
Commitment gate
  1. 01Discovery Express

    2 sessions, no cost

  2. 02Blueprint

    1 to 2 weeks

  3. 03Pilot

    8 to 12 weeks

  4. 04Scale & Managed

    Continuous

  • Pilot, first 8 weeks
  • Up to week 12 of the pilot
  • This agent: 2 to 4 weeks of tuning, inside the pilot
  • Commitment gate: the KPI decides Scale

Proof and demo

What backs the label.

Proof Ledger note

In production

Measured in a real deployment and logged in the Proof Ledger with source, date and owner.

Reviewed September 3, 2026

Where this agent sits on the maturity policy

  1. Reference architecture
  2. Pilot
  3. In productionToday

The Discovery Express shows this agent on your data, live. Two sessions, no cost.

See this agent with your data

Related agents

Same function or industry.

All agents
A maintenance technician checking readings on a tablet beside a CNC machine
Reference architecture

Operations

Telemetry Watch Agent

KPI it movesTypical target

Unplanned downtime 15 to 25% lower

A dispatcher on the phone at dawn, trucks parked outside the window in Monterrey
Reference architecture

Operations

Fleet Check-Call Agent

KPI it movesTypical target

80 to 90% of check calls automated

FAQ

Direct answers.

Never. It captures, validates and opens the claim. Coverage, reserve and payment stay with an adjuster, and the limit is enforced by the platform, not by the prompt.

Injury, distress and emergencies route to a person immediately with everything already captured. Those thresholds are set in the Blueprint with your claims team.

Yes. It checks legibility, extracts the fields the file needs and asks again when an image will not hold up in the file, before the adjuster ever sees it.

Which process do we automate first?

Two discovery sessions, no cost, and you leave with two or three quick wins whether or not you build with us.

We reply in under one business day.

Loading the form