The complete solution for
modern claims management

We don't replace your systems. We connect them, fill the gaps, and build on top of them. From first notification to payout, in one working environment, together with your team.

We automate process-related contact, so there is more room for meaningful personal contact.

App visualApp visualApp visual

The foundation for modern claims management

Four pillars that make your organisation ready for growth and innovation.

Transparency

Every step in the case file visible to those allowed to see it. Claims handler, customer, injured party, partner and management work from the same factual picture, each from their own role.

Automation

Routine tasks run by themselves. Notifications, status updates, document routing, follow-ups. Time that goes back to the claims handler, for the work that requires their expertise.

Integration

API-first orchestration across policy, claims and partner systems. Existing systems stay in place; we make them talk to each other. No replacement projects, no lock-in.

Security

ISO 27001 certified. GDPR by design. Audit trail per case and per automated action. Ready for DORA vendor assessment.

Transparency for everyone in the process

Policyholders, service providers and internal teams work together in one environment.
  • Status and next step visible 24/7 to the claimant and their representative.
  • One statement of loss: claimed, demanded and acknowledged side by side.
  • Permissions per role and per head of damage.

Automate where possible, escalate where needed

Leave repetitive tasks to smart workflows and make sure complex cases get the right attention.
  • Deadlines per head of damage set and monitored, including the GBL deadlines.
  • Tasks and reminders automatically with the right role.
  • Every document straight to the right head of damage.

Connect everything, without replacement projects

Integrate effortlessly with existing policy and claims systems. Our API-first architecture makes integrations simple and scalable.
  • Connects to Axon, CCS, Guidewire and in-house core systems.
  • Writes back to the core system, nothing entered twice.
  • Chain partners through one API or through the portal.

Protect sensitive data, today and tomorrow

Our solution meets the highest standards for security and compliance.
  • ISO 27001:2023 certified, hosted in the Netherlands.
  • Audit trail per file and per automated action.
  • Documentation ready for a DORA vendor assessment.

The chain

From notification to settlement, in five steps

What Claim360 does at each step.

Step 1 of 5

Notification

Question tree per type of claim, required fields. Incomplete does not get in, and what comes in arrives as fields instead of attachments.

Step 2 of 5

Liability and position

The deadline for the position is a task with a date and an owner, including the Dutch GBL deadlines. The draft position is ready with sources, the handler takes it.

Step 3 of 5

Medical track

The medical adviser gets secure access to exactly the documents needed. The report lands straight in the right file, access is logged and revocable immediately.

Step 4 of 5

Statement of loss and advances

Every document at the right head of damage. Claimed, demanded and acknowledged side by side in one statement of loss, advances and reserve per item.

Step 5 of 5

Settlement

The settlement agreement drafted from the file. The final payment goes back to the core system without retyping.

The handler decides. With personal injury a decision never goes straight through. The gain is in all the work around it.

How the solution is built

Four layers, one file

Every layer rests on the one below, and together they hand control back to the handler. Bottom to top: your core system stays, Claim360 connects the chain, the portal captures the data properly, the workflow keeps it current, and only then does AI work.

How it is built

AI

  • summary
  • flagging
  • drafts
  • triage

Only once the file is right does AI work. Summarising, flagging, drafting, with the user's permissions and every question logged.

Workflow automation

  • deadlines
  • tasks
  • documents
  • payments

Deadlines, tasks, documents and payments run by themselves. What the system knows, nobody has to watch.

Self-service portal

  • fields instead of attachments
  • only what each role needs
  • one file

Claimant, representative, chain partners and handler work in the same file. Everyone sees only what their role needs.

Claim360, the orchestration layer

  • direct API per chain partner
  • permissions and logging
  • writes back to the core

The layer over your core system that connects the chain. Work fully in Claim360, or hybrid alongside it: the core system stays.

Your core system

Keylane Axon, Novulo, CCS, UBench and Guidewire or another: it stays. Claim360 connects to it and writes back. See the integrations

Without a portal and an orchestration layer, no AI at scale. Only with one file and one truth can AI work on every file, and only then does the handler get the time for the claimant.

See our AI solutions

Works with your core system

Claim360 connects to the system that is already there and writes back. The core system stays in the lead.

  • Axon NL · BE

    Vendor: Keylane

    Connects via the Claim360 API

  • Novulo NL · BE

    Vendor: Novulo

    Connects via the Claim360 API

  • CCS NL · BE

    Connects via the Claim360 API

  • UBench NL · BE

    Connects via the Claim360 API

  • Guidewire NL · BE

    Vendor: Guidewire

    Connects via the Claim360 API

Is your system not listed? Claim360 is API-first and also connects to in-house and other core systems.

See all integrations

Claim360 as orchestration layer

From sixty-six lines to one hub

Three to twelve parties in a heavy file. Today almost all communication is bilateral, by email, letter and phone.

Today
66 possible communication lines email, post, phone, loose attachments, reminders, lost versions
With Claim360
12 lines, one truth one file, one statement of loss, permissions per head of damage, deadlines monitored, audit trail

Claimant · representative · handler · legal aid · medical advisers · occupational expert · loss adjuster · outsourcing · recourse parties

Without a self-service portal and an orchestration layer underneath, AI at scale in personal injury is not possible. Claim360 connects the chain: every chain partner connects through a direct API on Claim360, or Claim360 connects to that party. Only then can AI work on every file, and only then does the handler truly get control and the time to focus on the claimant.

How we apply AI

Workflow automation

Eight areas, all on the same file

What the system knows, nobody has to watch.

  • Intake and validation

    Question tree per type of claim, required fields, incomplete does not get in.

  • Deadlines and GBL

    Deadline per head of damage set and monitored, escalation when it runs over.

  • Tasks and workload

    Task with the right role, workload per handler and per team.

  • Document flows

    Every document attached to the item it belongs to, with version history.

  • Chain connection

    Add a party with permissions per role, access logged, revocable immediately.

  • Payments and reserves

    Advances, balance and reserve per item, written back to the core system.

  • Communication

    Messages per head of damage, status for the customer, no loose email.

  • Management information

    Lead time, reminders, costs and complaints measurable per file.

Measured together: administrative time per file, phone traffic, number of reminders, lead time per head of damage. A baseline up front, so the conversation afterwards is about figures.

−30% fewer incoming messages and phone calls, at minimum

Our products and services

Handling claims faster, smarter and more transparently, together.

Claim360

the orchestration layer, core of the platform
Process icon
Claim360 is the engine behind everything we do. An API-first orchestration layer that connects policy, claims and partner systems. Legacy systems stay in place, external partners don't need access to your core systems, and all case data comes together in one structured flow. Claim360 is not a claims system and not a policy system. It is the layer that makes all systems work together the way you intended.

Azori

optional working environment on top of Claim360
Process icon
Azori is the white-label user environment you can put on top of Claim360. If you don't yet have a strong user interface for claims handlers, customers, injured parties and partners, Azori provides one out of the box, in your own house style. If you already have your own environment, we connect Claim360 to it and Azori stays out of the picture. Azori is a choice, not an obligation.

Solution-Hub

accelerators per claim domain
Process icon
Solution-Hub contains field-proven building blocks: intake, assessment, communication, reporting. For each claim domain (AOV, SVI, personal injury, material damage) 80 per cent is ready to deploy. The remaining 20 per cent we fill in together. Co-creation, not template work.

Custom work

Where standard is not enough
Process icon
Where the standard falls short, we build custom solutions on Claim360 that fit your processes exactly. Not a separate product, simply an extension of what is already running. Maintenance and further development stay with us, or we hand them over to your team. Both are possible.

One ecosystem, tailored to every user

Our platform gives every stakeholder an environment that fits their role exactly. Everyone works together efficiently, while all data stays in sync in one central system.

Simple, clear insight for customers and clients

Fast reporting, a clear follow-up, no waiting for phone calls. One secure portal for all communication and documents.
  • Report and track a claim quickly
  • Secure document exchange
  • A transparent process without noise

Frequently asked questions about personal injury in Claim360

Not seeing your question?

Ask your question on the contact page

Can AI assess a personal injury claim?

No. With personal injury the decision never goes straight through. AI prepares: it puts the accounts side by side, tests heads of damage against policy and standards, and writes a draft position with sources. The handler takes the position. The gain is in all the work around it, not in the decision.

Do we have to replace our claims system?

No. Claim360 is an orchestration layer that runs on top of existing systems. We connect via API to legacy policy systems, claims administrations and more. No rip-and-replace, no two-year programme.

How do you monitor the deadlines of the Dutch GBL code?

The GBL deadlines are tasks with a date, an owner and a counter: acknowledgement, position, payment and contact moments are monitored rather than tracked by hand.

How does this fit an insurer with many outsourcing partners?

That is where we excel. Claim360 as an orchestration layer lets external assessment agencies, recovery partners and medical advisers work securely with your core systems, without needing access to them. One standardised exchange layer, for all partners.

Demo

Want to see how a personal injury file runs?

One intake and one technical walkthrough in a production environment at a Dutch insurer. After that you know what it means for your chain.

Request a demo