Your system stays the record
It does not replace your claims or CRM system. It fills it, through that system's own API.
- Madar
- Insurance claims automation
Every claim email becomes a case.
It reads the incoming email, understands the matter, extracts the details and makes a preliminary assessment. Then it opens the case in your CRM or core system, routes it to the right queue and tells the handler what is expected next.
Arabic and English. Built in Kuwait.
Incoming email → caseSample
Car accident yesterday, policy MTR-48213
My car was hit from behind at the Fourth Ring Road signal. Police report attached.
Extracted
- PolicyMTR-48213
- LineMotor
- IncidentRear-end collision, 4 Oct 2026
- LocationFourth Ring Road
- AttachedPolice report
- MissingPhotos of the damage
Preliminary assessment
Motor claim against a third party. Policy found in the email; photos still needed.
Case
Opened in the core system · Queue: Motor claims · Next for the handler: request photos of the damage
How it works
From the inbox to the right queue.
Reads the request
An email or request arrives in the shared inbox. It is read in Arabic or English.
Extracts and classifies
Policy number, names, dates, places and the type of matter are pulled out and labelled.
Makes a preliminary assessment
What the matter is, what has been provided and what is missing. The decision stays with your team.
Opens and routes the case
The case is created in your CRM or core system through its API and placed in the right queue, with a note on the next step.
Where it fits
It works inside the systems you already run.
Your rules decide the routing
Queues, priorities and what counts as a complete request are set with your team.
Not only claims
The same flow handles service requests, policy changes and complaints that arrive by email.
Questions
Insurance claims automation, answered.
Does it replace our claims management system?
No. It opens and fills the case in the system you already use, through its API, so your team keeps working where it works today.
Does it decide whether a claim is covered?
No. It makes a preliminary assessment: what the matter is and what is missing. Coverage decisions stay with your handlers.
Which systems can it connect to?
CRMs and core insurance systems that offer an API. We confirm the connection when we scope the project.
Can it read Arabic emails?
Yes. Arabic and English, including messages that mix both.
What about the documents attached to a claim?
Attachments such as reports, estimates and invoices are the job of Document Intelligence, which reads, separates and classifies them.
Tell us what lands in your inbox.
Where requests arrive today, who picks them up, and which system the case should open in. We will show you how it would handle them.