Skip to content

The claim is open before
the caller hangs up.

Claims intake with policy lookup and document requests in one call. The policy is checked, the claim opened, the documents requested, and the claim number read back before the call ends.

  1. 01ClientsMetLife · OdysseyRe
  2. 02The taskIntake, lookup, documents
  3. 03The callClaim number read back
  4. 04SystemsPolicy admin, claims, documents
  5. 05ProofWhat a claims build looks like

An illustrative call plays beside this headline. The agent checks the policy, opens the claim, requests the two documents it needs and reads the claim number back before the call ends. A receipt of what the call changed prints at the end.

Clients01 / 05

Who runs it in insurance, and what they run.

The task02 / 05

Intake is not a form. It is a conversation that opens a file.

Policy lookup, claim creation, and the documents, in one call. The policy decides what is covered, the claim number is the thing the caller remembers, and the documents decide whether an adjuster starts on Monday or waits for a call back.

On the runtime, in one call

One call, on the runtime.

The cover is read, the claim is created once, and the documents are asked for by secure link before the call ends.

Three steps, one call

Policy read on the call

The policy is found, and the cover and the deductible are read to the caller as they stand.

Cover read live

Claim opened and numbered

The claim is created once, and its number is read back to the caller before the call ends.

Numbered on the call

Documents sent, adjuster briefed

The document link is sent, and the adjuster opens a file that already holds the policy.

File complete
The call03 / 05

The claim number is spoken before the call ends.

The cover is read, the claim is created once, and the documents are requested by secure link. The adjuster inherits a file that already knows the policy, the damage and what is still outstanding.

Illustrative call, not a recording.

Customer

I need to file a claim. My car was hit in a car park yesterday.

Claim CLM-482913 opened · policy checked · 2 documents requested

Moment 1 of 6: Reports the damage, Telephony

Systems04 / 05

One claim, opened once, in your claims system.

Policy admin is read, the claims system is written, and the documents land in your store. The adjuster’s queue receives a claim that already carries its cover, its description and its outstanding documents.

One claim, opened once, in your claims system.Policy admin is read, the claims system is written, and the documents land in your store. The adjuster’s queue receives a claim that already carries its cover, its description and its outstanding documents. The steps, in order: Your telephony, Voicing runtime, Policy admin, Claims system, Documents, Messaging, The adjuster, Call record.YourtelephonyFirst noticeVoicingruntimeIn your estatePolicy adminRead: the coverClaimssystemWrite: the claimDocumentsCaller uploadsMessagingNumber by SMSThe adjusterCall recordEvery step keptIn your perimeterNothing leaves itPolicy adminRead only, never writtenClaims systemOne claim, created onceThe adjusterLiability stays here

Step 1 of 6: First notice of loss arrives on your own line.

Systems

Guidewire, Duck Creek, Majesco and Salesforce, and whatever else you run.

One runtime, inside your perimeter
  • Guidewire

  • Duck Creek

  • Majesco

  • Salesforce

The policyholder view stays current while the call is still running: the claim created, the adjuster assigned and the interaction logged before the caller hangs up. Nothing waits for a batch.

System marks belong to their owners.

And it does not end here.

  • A documented API

    Every action the agent takes, as a call.

  • An MCP server

    Your tools, over the Model Context Protocol.

  • Webhooks

    Events pushed to whatever listens.

  • Any system with an interface

    Your own claims workbench, same terms.

What it is held to.

  • NAIC model acts

    Insurance conduct

  • Recording consent

    Call disclosure

  • Control audit

  • Data security

Proof05 / 05

Claims intake, measured before and after.

  • 50%faster first notice of lossA claims-intake deployment, as published
  • 24/7claims intake, every hourThe same deployment, after-hours calls answered
  • +12NPS points, policyholdersThe same deployment, the same policyholder base

What changed at intake, before and after.

Five measurements, each with its before. Every row is one claims-intake deployment’s own figure on both sides of go-live, and no change is stated as a percentage because the deployment never published one.

  1. FNOL completion time18 min9 min
  2. Average handle time7.2 min4.7 min
  3. After-hours abandonment34%2%
  4. Claims data accuracy71%96%
  5. Policyholder NPS2840

A claims-intake deployment’s figures as published by Voicing AI; period on request. 50 states compliant, United States insurance regulations.Ask us for the report

Bring us your first notice of loss calls.

An illustrated assist desk: a caller dial ringed with beads on the left, a cable into a white desk with a lavender back panel, five suggestion cubes on a sage platform with a sage cone over the raised one, and a headset on a lavender tile on the right.
Insurance

Claims intake with the answer on the desk

Book a review with the architects who would run it, not a sales call. We will read your call flow, name the systems it touches, and tell you what we would not automate. Then count the claims reopened because intake missed something, and the adjuster hours spent asking for what should have arrived with the file.