ClaimFlow · Claims operations
44 → 11 days

The claim cycle the operation is built to reach on ClaimFlow.

Every claim, first notice of loss to settlement.

An adjuster opens a file already scored for severity, matched to policy and coverage, and routed to the right queue. Every supplier runs against the service-level (SLA) clock, and an AI co-pilot drafts the assessment. Ten carriers run motor claims across the VinFast service-centre network on ClaimFlow.

claimflow.trisilva.ai
ClaimFlowOverview
Search⌘K 3
Operations overview
NationwideNorthCentralSouth
Live · 60s February 2026
On-time rate
94.2%
above target
Breach rate
5.8%
within target
Return time
11.3d
down from 44d
Open claims
4,712
14 service centres
Unmatched
23
4 over 24h
Claims value
512Bđ
MTD · VND
Priority queue1 breached · 3 at risk
VF 8 · Rear collision
CLM-24187 · Carrier A · 180M đ
12m overdue
VF 9 · Flood damage
CLM-24191 · Carrier B · 240M đ
18m left
VF e34 · Windscreen
CLM-24203 · Carrier C · 65M đ
42m left
VF 5 · Side impact
CLM-24210 · Carrier D · 40M đ
1h 10m left
VF 6 · Minor dent
CLM-24226 · Carrier E · 12M đ
3h left
VF 3 · Bumper scrape
CLM-24231 · Carrier F · 35M đ
4h 20m left
SLA breach by touchpointinsurer × step
Notify
Approve
Pay
Match
Carrier B
5.6
8.2
4.1
3.4
Carrier D
4.8
7.1
3.0
2.1
Carrier A
3.1
6.4
2.0
1.2
Carrier C
2.2
3.9
1.5
0.8
Carrier F
2.6
3.4
1.8
0.9
Carrier E
1.9
2.8
1.0
0.5
Avg cycle time44d → 11d · 12 mo
Mar 2025Feb 2026
Insurer scorecardshare · on-time
Carrier A30%92%
Carrier C23%96%
Carrier D14%91%
Carrier E12%97%
Others21%96%
Unmatched claimsneeds review
No claim filed in 24h14
Multiple policy matches6
Certificate not found3

The command centre a claims operation runs its day from. Illustrative interface; the figures are constructed and are not drawn from a live account.

The Vietnam insurer panel

PVIMICPJICOBSHDBV InsuranceVBIBảo ViệtPTIBảo MinhLPBank Insurance PVIMICPJICOBSHDBV InsuranceVBIBảo ViệtPTIBảo MinhLPBank Insurance

Ten of Vietnam's insurers on the platform's carrier panel.

The problem

Claims is where insurance keeps its customers, and where it loses them.

A motor claim touches a service centre, a workshop, a parts supplier, and an insurer, each on its own system and its own clock. Four structural gaps stretch the cycle and leak margin.

Cycle times that run long

A claim moves by phone, email, and spreadsheet between parties who cannot see each other's status.

The customer waits weeks for a car they needed the same day

Partners digitised at different rates

Service centres, workshops and suppliers each digitised for their own business, on their own timeline.

Work that should flow through stalls at the least-ready link

SLA breaches nobody sees coming

Service-level clocks are reconstructed after the fact rather than watched while the claim is running.

Breaches surface as penalties, not as warnings in time to act

Fraud and leakage unchecked

Severity and repair costs are assessed by hand, claim by claim, against whatever documents arrive.

Inflated and duplicate claims pass through the queue unchecked
What fixing this takes

Four non-negotiables at once.

  • One shared view of claim status across service centre, workshop, supplier, and insurer.
  • A live service-level clock that warns before a breach, not after it.
  • Severity and fraud assessed on every claim, not sampled by hand.
  • A clean audit trail, with each insurer's data walled off from the next, that a carrier can read end to end.
Read the deep-dive: from FNOL to settlement
How it works

One claim file, three guarantees around it.

The walkthrough below follows a single claim from first notice to a reconciled payout. These three are true for every claim and every carrier on the platform. Each is a live surface in the product, not a slide.

Breach warnings, not penalties

01

Every service-level touchpoint is watched live across the whole book, so a breach shows as a warning while there is still time to act.

SLA amber before breach42m left

A clean audit trail, per carrier

02

Every action lands on an audit trail kept separate for each carrier, one an insurer or auditor can read end to end.

Action history, tenant-scopedExportable

One adapter library, every carrier

03

Carrier systems connect through the same normalised adapter library that runs the Vietnam insurer panel, so bringing a new carrier onto the platform takes days rather than months.

Carrier onboardedDays, not months
See the integration fabric and the adapter pattern
How it runs · ClaimFlow

Watch a claim run, first notice to settlement.

Every stage on one AI-native platform, with the audit trail writing itself.

01
First notice of loss

The first notice of loss is captured at the service centre and matched to the policy and its coverage in seconds.

CLM-4821 · MotorAuto-captured
02
Severity triage

AI scores severity and routes the claim to the right queue and the right adjuster the moment it lands.

SeverityHigh · fast-track
03
Adjuster co-pilot

The adjuster works with an AI co-pilot that drafts the assessment and flags fraud signals against the file as it builds.

Co-pilotAssessment drafted
04
Supplier orchestration

Workshops and parts suppliers are dispatched and tracked against a real-time service-level clock, job by job.

WorkshopDispatched · on track
05
Settlement

Payout approved and reconciled, with the SLA met and every action on an audit-clean trail.

Paid · 11.3dSLA met
The commitment

The cycle time, the clocks, and the network size.

44 → 11 days
The cycle an operation on ClaimFlow is built to reach, from a starting point of 44 days when no single platform holds the claim.
Watched live
Service-level clocks tracked in real time on every claim, so adherence is managed before breach, not measured after it.
420+ centres
Built to run the full VinFast national service-centre network.
In production

Running claims across the VinFast service-centre network with BeeVN.

BeeVN · VinFast after-sales network · Vietnam

The challenge

A motor claim in the VinFast after-sales network touches a service centre, a broker, an insurer, a workshop and parts suppliers, each running its own system for its own part of the job. No party in that arrangement owns the whole claim, so status lives in whichever conversation last happened and the service-level clock is only readable once it has run out. BeeVN, the broker managing the claims, wanted one operation the whole network could run on.

What we run

ClaimFlow runs the whole operation, and a ten-carrier Vietnamese insurer panel sits on the platform, so a claim reaches the right carrier without ever leaving the system.

The outcome

The operation is built to bring the cycle from 44 days to 11. Service levels are managed before breach rather than measured after. The operation is extending across the full VinFast national network of more than 420 sites. One claim file, first notice to settlement, on one platform.

How the engagement works

Paid on the outcome, on a trail an auditor can read.

Outcome-based feesAligned
The fee is tied to the claims result delivered, not to seats, hours, or activity.
Tenant-isolated dataWalled
Each carrier's data is walled from the next on a multi-tenant platform, isolated by design.
Audit-clean trailTraceable
Every action is logged and traceable, so a carrier or an auditor can read any claim end to end.

Outcome-based fees and an audit-clean trail are the two things a carrier checks before it trusts an operation with its claims. The full residency and compliance posture lives on the technology page.

See ClaimFlow run a real claim.

Bring a claim you settled last month, and we will show you the same claim on ClaimFlow, first notice to settlement.

Singapore · Vietnam · Indonesia · Philippines