03 · Insurance operations
For claims, assistance and portfolio operations.
Operations are resolved as journeys on BPMflow: one case file per case, with participants, deadlines, observations and closing evidence someone can review later. All three share the same mechanism, and each keeps its own rules, its own third-party network and its own way of closing.
Journey · Claims
Claims and service coordination
A case can stall because a document is missing, because an adjuster report has not arrived or because an intervention is still pending. The journey organizes that work around the claim file: what was requested, who answers, which observation is still open, which deadline applies and what the next step is, through to a confirmed answer to whoever raised it. Documents, participants, adjusters, workshops and providers stay inside the same case, with traceability of every intervention. Coverage calculation, underwriting, policy administration and fraud detection belong to the insurance core and to its specialist engines: their results enter the case file as recorded decisions, with an owner and evidence.
Explore Claims and Service Coordination → Journey · Assistance and service guarantees
Assistance and services committed with third parties
Roadside, home and health assistance and service guarantees share tasks with a claim, and they have a different trigger, a different buyer and a different closing condition. Each variant is configured with its own provider network, its committed response times and its own way of closing: service accepted, work executed or agreed answer, with the reason and the evidence of the resolution inside the case.
Explore service coordination with external providers → Journey · Portfolio onboarding and review
Onboarding and review of policyholders, brokers and providers
The work continues after onboarding. An expiry, a relevant change or a periodic review may call for new documentation and another authorized decision. The journey receives the request or the event, gathers the information, coordinates the reviews and records the decision with its owner: approval, restriction, suspension, rejection or termination, according to the agreed rules. External verifications contribute their result to the case; regulatory rulings and specialist compliance analysis stay with the owners who sign them.
Explore Customer Onboarding and Review → Agreed scope · On the Operational Graph
When the journey has rules of its own
When the process has rules, participants or evidence specific to the company, scope is agreed process by process on the same Operational Graph: what is reused, what is adapted and what is built. The starting point is one concrete journey — a claim type, an assistance service, a portfolio review — with its trigger, its owners and its closing condition.
See the scoped delivery path →
The mechanism is the same across the three journeys: BPMflow executes the case and the Operational Graph supplies the context of systems, documents and owners. See how a case works →
