---
title: "Insurance claims intake | Mirai360"
description: "AI systems for insurers. Each first notice of loss becomes one claim, with the policy attached and missing documents listed. A handler decides."
canonical: https://mirai360.ai/industries/insurance/
---

Insurance

# Your handlers open claims ready to decide.

Before a handler opens a claim, our AI system has found the policy, gathered the documents and fraud-screen hits, and listed what is missing.

[Tell us your claims problem by email](mailto:contact@mirai360ai.in?subject=The%20problem%20(insurance)) [Find your bottleneck](https://mirai360.ai/tools/bottleneck-finder/)

**Who decides**

Your handler decides cover and payment on every claim. Pricing, payouts and any bindable commitment stay with your people.

**Where it runs**

Built and run in your cloud. Every step the system takes is logged, so any decision can be reconstructed for an auditor, a regulator or a reinsurer.

**What we measure**

Time from first notice of loss to a handler's decision, and how often a handler changed the system's coverage note.

## What the queue costs you

**The policyholder chases.** While a claim waits for someone to open it, the policyholder may phone to ask where it is, and a handler stops to look it up. ICOBS 8.1.1R requires you to handle claims promptly and fairly, and to give the policyholder appropriate information on progress.

**Late payment can cost damages.** For policies made since 4 May 2017, section 13A of the Insurance Act 2015 lets a policyholder claim damages for loss caused when a valid claim is not paid within a reasonable time. The Act sets no number of days and allows time to investigate. A claim left unopened in a queue is harder to defend.

Where handler hours go

## Handler hours on one claim

One example claim, from first notice of loss to the handler's decision, with the handler's minutes at each step today and what the system takes on.

45 min

### First notice of loss

Today a handler reads the broker's email, keys the claim in and chases what is missing. The system assembles the claim and drafts the request for anything missing.

65 min

### Policy and cover

Today a handler finds the policy and checks dates, excess and exclusions. The system drafts a coverage note citing the clauses it relied on, for the handler to check.

60 min

### Verification and fraud screen

Today a handler gathers the documents and reviews the fraud-screen hits. The system gathers both and lists anything it could not verify.

35 min

### Decision

A handler decides

The handler reads the prepared claim and decides it. This step stays with your people.

Illustration. Not a client system. The minutes are an example claim before the system: 3.4 handler hours in all (45 + 65 + 60 + 35). Your own figure comes from your claims.

**Every week**

Your claims lead gets the time from first notice to decision against the figure measured before launch, and every claim where the system could not complete a check, with the reason.

## What do slow claims cost you?

The first fix takes 2–3 weeks of build, after the data agreement is signed. If the problem is not clear yet, discovery comes first.

[Find your bottleneck](https://mirai360.ai/tools/bottleneck-finder/) [Book a 30-minute fit call](https://calendly.com/shivang-mirai360/30min)