Every claim in the network, visible until the vehicle is back.
A service network answers for vehicles it does not insure, repaired with parts it does not price, on cover placed across carriers it does not select. ClaimFlow runs the claim across every party in it, so a promise made to a customer is one the network can see and measure. Live today across a national automotive network in Vietnam.
One claim, one record, from the moment it opens to the moment the vehicle goes back to work
See the claim, not only the step in front of it.
A network is accountable for a vehicle from the moment it stops earning to the moment it goes back to work. That span crosses a carrier, a workshop and a parts operation, and it is longer than any one party's own system covers.
The whole claim on one record.
01First notice, assessment, approval, repair and release sit on a single claim record. The state of a vehicle is a fact on a screen rather than a phone call to whoever touched it last.
Status that survives handover.
02Sight of the claim continues past carrier approval, through the workshop and back out again, which is the stretch where a network answering for the vehicle most often stops being able to answer.
Waiting on a part is a tracked stage.
03Waiting on a part is a stage with a state and an expected date, so the single largest driver of how long a vehicle sits still is something the network can see and plan around.
A trail an auditor can read.
04Every decision, timestamp and document stays attached to the claim, so a question asked six months later is answered from the record rather than reconstructed from inboxes.
Connect the systems already in the operation.
Every party in a claim runs something of its own, and each of them keeps it. ClaimFlow connects to those systems rather than replacing them, so the operation gains a shared view without anyone changing how they work.
One adapter per carrier.
01Carriers connect through a carrier-API adapter library rather than a bespoke integration each time, which is how a ten-carrier Vietnamese insurer panel runs on one claims operation today.
Built on open standards.
02The claim, the policy and the coverage follow OPIN, the open insurance standard, and the market profile Trisilva authors for each market. The data model a network builds against is one it keeps.
Days rather than months.
03Because the adapter work is a library rather than a project, a new carrier joins the panel in days. See the architecture.
Measure the time before setting a target.
Networks arrive at this from two directions. Some already have a delivery standard and need evidence that it is being met. Others have never counted what a late release costs, so the number comes first and the standard follows from it. The instrument is the same either way, and the order matters more than the target.
Time on every stage.
01Each stage of a claim carries its own elapsed time, so the question shifts from how long claims take in general to which stage, in which region, with which party.
A standard per stage and party.
02Once the stages are measured, a target can be set against each one and against the party who owns it, which is what turns a shared intention into something a network can actually hold.
Evidence both sides accept.
03Because every party works on the same record, performance is read from one source rather than reconciled between spreadsheets, and a conversation about a late claim starts from agreed facts.
Automotive claims in Vietnam, on the same platform.
Built to reach 11 days from 44, across an automotive service network.
VinFast and BeeVN run motor claims across the service-centre network on ClaimFlow, from first notice of loss through to settlement, on an outcome-based commercial model. The insurer panel runs to ten carriers, each connected through the same adapter library.
Service levels managed before breach, on a trail an auditor can read
The network is scaling toward 420 or more service centres. That is the target being built to, not a current count.
Read the full story →Priced on the cycle time, not on seats.
Three things are fixed by the model, whatever the commercial terms turn out to be.
Commercial terms are set per network in the engagement conversation, not published here.
From first conversation to a claim on the record.
Walk the claim as it runs now.
01Which party opens a claim, where it changes hands, and which stage the network stops being able to see it.
Map the parties and their systems.
02Carriers, workshops and the parts operation, and what each already runs, so the connection plan starts from the real estate rather than an ideal one.
Start with a region.
03A single region or a set of centres goes live first, which produces the measurement a wider rollout is then argued from.
Scale on evidence.
04Centres are added against measured results rather than a fixed schedule, which is how the Vietnamese network is being extended today.
Answer for the vehicle with the claim in view.
Tell us how a claim moves through the network today, and we will show you where sight of it is lost and what it takes to keep.
Brokers · Insurers · The ecosystem