Core claims systems integration
Ishqkala + Insuresoft Diamond Claims
Subrogation detection for Diamond Claims carriers, on Azure-managed or on-premise deployments.
Overview
Diamond Claims is Insuresoft's web-based claims administration module, built on Microsoft .NET and used by P&C carriers, MGAs and MGUs across personal auto, commercial auto, homeowners, farm and workers' compensation. It runs inside the Diamond suite or alongside another policy system. Ishqkala connects through the Diamond APIs your implementation exposes, or a scheduled extract from the Diamond database, and returns findings as a claim note and task. Diamond's subrogation and salvage records stay the system of record.
Use cases
- Find third-party liability in farm and rural property claims, such as equipment fires and contractor damage.
- Score regional personal auto collisions nightly for at-fault drivers with identified carriers.
- Sweep closed workers' compensation claims for third-party actions against drivers and equipment makers.
- Hold SOL dates for every open opportunity until a recovery is booked in Diamond.
Architecture & data flow
How data moves between Insuresoft Diamond Claims and Ishqkala.
01
Change capture
Ishqkala polls Diamond APIs for changed claims, or receives a nightly delta extract over SFTP.
02
Ingestion
Claims, notes, documents and financials load into your isolated Ishqkala tenant.
03
NLP and scoring
Notes and documents are read for liability signals and scored on recoverable dollars, win probability and days to SOL.
04
Write-back
A finding note and task post through the API, or a findings file returns for your team to load.
API data flow
Objects read and written.
| Object | Direction | What Ishqkala does with it |
|---|---|---|
| Claim | Read | Loss date, loss state, cause of loss, line and status, with coverage verified at the date and time of loss. |
| Claimants and parties | Read | Involved parties and their roles, used to identify the adverse party and carrier. |
| Claim notes | Read / write | Adjuster and automatic notes parsed for liability signals; Ishqkala adds a finding note with cited text. |
| Claim documents | Read | Police reports, estimates, photos and expert reports from Diamond's document management. |
| Payments and reserves | Read | Paid and reserved amounts by coverage for the recoverable estimate. |
| Subrogation and salvage | Read | Existing subrogation and salvage activity, so open recoveries are not flagged again. |
| Task | Write | A review task assigned to the subrogation adjuster, due ahead of the SOL date. |
Security & data governance
Controls on this connection.
- Dedicated Diamond service account, or SFTP with key-based authentication and PGP encryption.
- Least-privilege access to claim, note, document and task data only; no write access to financials.
- AES-256 at rest and TLS 1.3 in transit, hosted only in US AWS regions.
- Zero model training on your claim files.
- Audit log of every record read and every note or task written.
Setup timeline
From kickoff to first findings.
Week 1
Scope
Confirm Azure-managed or on-premise deployment, available APIs and extract options with Insuresoft or your IT team.
Weeks 2 to 3
Mapping and baseline
Map loss causes and lines, then run a closed-claim baseline on 24 months of history.
Week 4
UAT
Adjusters review findings and agree thresholds and task routing.
Week 5
Production
Change capture and write-back enabled.
FAQ
Insuresoft Diamond Claims integration FAQ
No formal partnership is implied. Ishqkala uses the APIs or extracts your Diamond implementation already supports, under credentials your team controls.
Yes. Ishqkala only needs claim, note, document and financial data, so the policy system behind Diamond does not matter.
No. It writes a note and a task. Your adjuster opens the subrogation record in Diamond once they decide to pursue.
About five weeks from access to production for most carriers, with the closed-claim baseline delivered in the first three.
More core claims systems
Find the millions hiding in your closed claim files before the Statute of Limitations expires.
We'll scan a batch of 500 closed claims for free and deliver an itemized recovery manifest within 5 business days.