First notice of loss from any door
How do we take first notice of loss from an app, an agent, an AI assistant or an outside AI agent as one complete, governed claim that lands in the claims system with its skill and due date?
Run one first notice behind every door. Callvu identifies the policyholder and prefills the policy, the vehicles or the property and the coverages, classifies the loss from the first answers (the line, the cause, the severity, the parties, the injury flag, the catastrophe code) into a unit of work with a skill and a due date, asks only the questions the loss type needs, chases the photos, the police report number and the other party's details on a clock, applies the state's claim handling rules from the moment of notice, and writes one complete claim to the claims system with the acknowledgment sent and the adjuster assignment made by skill. Live at an insurance customer.
Live at an insurance customerComplex: multi-party handoffsCallvu moves: prefill, classify, chase and verify, write back
Last updated November 7, 2026.
The problem today
Three first notices for the same accident: the app's, the agent's and the AI assistant's, each with different facts and a different claim number.
A policyholder reports a loss in the app, calls the agent to make sure it went through, and asks the AI assistant for a status. Each door has its own intake, its own questions and its own write to the claims system; the adjuster finds three claims, merges them, and starts by calling the policyholder to ask again what happened. The first notice is where the claim's cycle time and the customer's trust are set, and it is the most fragmented step in the business.
The state unfair claims settlement practices acts set the obligations from the moment of notice: the acknowledgment within a set number of days, the claim forms and instructions, the investigation's start, the recorded reasons for decisions; the claims system needs a claim with the right coverage, parties, severity and assignment; the adjuster needs the facts once. An AI assistant or an outside AI agent can start the claim, but the sensitive data, the statements and the governed steps must run on process-controlled screens with the same enforcement.
One notice, classified on landing, with its skill and due date, is the claim the rest of the process can run.
How it runs
From the requestto the system of record.
A loss is reported in the app, on the website, to an agent on a call, to the insurer's AI assistant, or by an outside AI agent over MCP. Callvu opens one first notice and prefills it.
- Policyholder or claimant
- Reports the loss, answers only the questions the loss type needs, uploads photos and documents on their phone.
- Agent
- Works the same record on a call, co-browses, and sends the link to finish.
- Claims
- Receives one complete claim with its skill and due date; the adjuster is assigned by skill.
- Callvu
- Prefills, classifies, asks the right questions, chases, applies the state's rules, routes and writes.
Prefill and classify
The policyholder is identified and the policy, the vehicles or the property, the coverages and deductibles, the prior claims and the catastrophe declarations for the location and date are prefilled; the first answers (what happened, when, where, who was involved, injuries, drivable or habitable) classify the loss into a unit of work: the line and cause, the severity, the parties, the injury flag (which routes to the injury intake with its consent), the catastrophe code, the skill required and the due date under the state's rules.
Ask only what applies
The questions the loss type needs are presented (a collision asks about the other vehicle and the police report; a water loss asks the source and the mitigation; a theft asks the police report number and the inventory) on a secure screen in whichever channel the policyholder is in; sensitive answers and statements never go into an AI chat, which hands the policyholder to a process-controlled screen.
Chase and verify
The photos with guidance (the damage, the scene, the documents), the police or fire report number, the other party's and the witnesses' details, and the receipts or inventories the loss type requires are requested through a link and chased on a clock; each upload is read and checked (the date and location data, the vehicle or address match) and the claim shows what is outstanding.
Write back
One complete claim is written to the claims system with the coverage, the parties, the severity, the skill and the due date, the acknowledgment with the claim number and the next steps goes to the policyholder within the state's period, the adjuster is assigned by skill, and a conflict between two notices for the same loss or a coverage question at notice goes to the claims supervisor in the Decision Desk with only the allowed outcomes.
Where it ends: One governed claim reached the claims system from whichever door it started, classified with its skill and due date, with the facts, the photos and the reports attached, the acknowledgment sent and the adjuster assigned. The Decision Trace shows the classification, the questions asked and any decision; the Audit Trace shows each party's steps by channel and the write.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The app, the website, an agent on a call, the insurer's AI assistant, or an outside AI agent over MCP; sensitive data and statements stay on process-controlled screens.
The back office
Claims receives one complete claim with its skill and due date; the adjuster starts from the facts, not from a call.
The Decision Desk
- A conflict between notices for the same loss, or a coverage question at notice, goes to the claims supervisor in the Decision Desk with the record and only the allowed outcomes.
Proof
Live at an insurance customer.Published results only.
Each result is a published claim, with its code on agents.callvu.com, where its status, source and last verified date are kept.
Callvu classifies each request into a unit of work (work type, skill, effort, due date) the moment it lands.
HND-02 · Self-asserted · verified 2026-11-02
A process can be started by the customer's server, a webhook from any system, a phone menu that texts the caller a link (Visual IVR), the Callvu AI chat, an outside AI agent over MCP, a campaign spreadsheet, a public link or an inbound email.
CAP-01 · Self-asserted · verified 2026-11-02
Any AI agent, including the customer's own, can start a Callvu process over MCP, and the same evaluation and enforcement apply. Sensitive data never goes into an AI chat; must-not-skip steps stay on a process-controlled screen.
ENF-04 · Self-asserted · verified 2026-11-02
Callvu integrates with the insurance core systems Guidewire, Duck Creek Technologies, Majesco, Insurity, Sapiens and FIS Insurance Solutions.
INS-09 · Self-asserted · verified 2026-11-05
Questions
What buyers ask next,answered plainly.
Can an AI agent file the claim?
Yes, over MCP or through the insurer's AI assistant. The agent starts the notice; identity, sensitive answers, statements and uploads happen on process-controlled screens with the same enforcement.
How is the claim classified?
From the first answers into a unit of work: the line and cause, the severity, the parties, the injury flag, the catastrophe code, the skill required and the due date under the state's rules, the moment it lands.
What does the adjuster receive?
One complete claim in the claims system with the facts, the photos and the reports attached, assigned by skill, with the acknowledgment already sent.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.