The promise you made your client, on a record that shows it.
A broker holds the mandate. The risk sits with carriers on the panel, the work sits with repairers, and the service commitment sits with the broker who arranged both. ClaimFlow runs the claims operation underneath that commitment, so what happened to a claim is a matter of record rather than reconstruction. Live today on a ten-carrier panel in Vietnam.
One claim, from the panel it was placed on to the answer the client gets
Accountable for a claim the broker neither underwrites nor repairs.
A broker sits between a client who wants a vehicle back and a panel of carriers who each handle a claim their own way. The mandate covers both placement and what happens after a loss, which makes evidence the working material of the job.
Answerable for placement and for what follows.
01The mandate covers where the risk was placed and what happened after the loss, so a broker is asked about outcomes it does not directly control and needs to be able to answer for them.
The record is the evidence.
02Decisions, timestamps and documents stay attached to the claim, so a question about a claim from months ago is answered from the record rather than from three inboxes and a spreadsheet.
Every stage has a time and an owner.
03Each stage of a claim carries its own elapsed time and the party who owned it, which is what makes a conversation about a late claim start from agreed facts.
Capacity spread across the panel, not concentrated.
04Capacity can be spread across carriers as a book grows, rather than concentrating on whichever one was easiest to connect.
One process, whichever carrier holds the risk.
Carriers run their own claims systems and repairers run their own workshop tooling. ClaimFlow connects to them rather than replacing them, so a growing panel does not become a growing number of processes to manage.
A panel on one process.
01A ten-carrier Vietnamese insurer panel runs on one claims operation today. A claim follows the same path whichever carrier is behind it, so handlers learn one process rather than ten.
One client book, one view.
02A client's claims sit together regardless of which carrier wrote which policy, so a review with that client is one conversation rather than a reconciliation between carriers.
Separated by tenant.
03Each carrier and each client sits in its own tenancy with its own scope, so a broker can run a whole panel on one platform without any party seeing another's book. See the security posture.
A motor panel in Vietnam, on one claims operation.
Built to reach 11 days from 44, across a ten-carrier panel.
BeeVN arranges cover and runs claims for the VinFast service-centre network on ClaimFlow, across a panel of ten carriers. Claims move through the same operation whichever carrier holds the risk.
One operation across the panel, on a trail an auditor can read
Read the full story →Three things the model does not change.
Three things are fixed by the model, whatever the commercial terms turn out to be.
Licence and service terms are set per broker in the commercial conversation, not published here.
From one client book to the whole panel.
Walk the panel as it runs now.
01Which carriers sit on it, how each handles a claim, and where the differences between them cost time.
Map the systems in play.
02Carrier claims systems, repairer tooling and the broker's own record, so the connection plan starts from the real estate.
Start with one client book.
03A single client and a subset of the panel go live first, which produces the measurement a wider move is argued from.
Extend across the panel.
04Carriers are added through the adapter library as the book moves, rather than as a fresh integration each time.
Answer for the panel from one record.
Tell us how claims move across the panel today, and we will show you what the operation looks like on one record.
Fleet and service networks · Insurers · The ecosystem