Estimating & data integration
Ishqkala + Verisk ISO ClaimSearch
ClaimSearch match reports and carrier notifications folded into every subrogation score.
Overview
ISO ClaimSearch is Verisk's all-claims database, used by contributing insurers for claim matching, fraud detection and, through its Subrogation Solutions features, identifying other carriers on a claim. Ishqkala reads the match reports, Carrier Identified Notifications and Policy Insights Reports your organization already receives under its own ClaimSearch subscription. Those results name the adverse carrier, confirm coverage and surface related claims, which Ishqkala combines with note and document evidence before it scores the file.
Use cases
- Name the adverse carrier at FNOL so the subrogation demand goes out with the first payment.
- Find the at-fault party's carrier on claims first opened as uninsured motorist losses.
- Spot related claims from other insurers on the same property loss to coordinate recoveries.
- Confirm third-party policy effective dates before investing in an arbitration filing.
Architecture & data flow
How data moves between Verisk ISO ClaimSearch and Ishqkala.
01
Your claim system reports
Your existing ClaimSearch integration reports the claim. Ishqkala does not submit, change or contribute ClaimSearch data.
02
Reports land
Match reports and notifications arrive in your claim system as documents or structured data.
03
Ingestion
Ishqkala reads the reports with the rest of the claim file.
04
Adverse carrier resolution
Carrier identity from ClaimSearch is reconciled with notes and the police report to name the adverse party and carrier.
05
Scoring
An identified, confirmed carrier raises collectability, and the claim is routed toward a direct demand or inter-company arbitration.
API data flow
Objects read and written.
| Object | Direction | What Ishqkala does with it |
|---|---|---|
| Match report | Read | Prior and related claims matched on parties, vehicles and addresses, including other insurers' claims on the same loss. |
| Carrier Identified Notification | Read | Alert that another carrier is on the claim, with the third party's adjuster contact information when available. |
| Policy Insights Report | Read | Third-party coverage details, address, vehicle, driver and lienholder information, where your organization subscribes. |
| Claims Coverage Identifier results | Read | Other involved insurer identified from name and address, VIN, or plate and state, where subscribed. |
| ClaimSearch reference | Read | The ClaimSearch reference and report status on each claim, showing whether it was reported and matched. |
Security & data governance
Controls on this connection.
- ClaimSearch data used only for your claims and only within the scope of your ISO ClaimSearch agreement.
- Never pooled across customers; each tenant's ClaimSearch results stay in that tenant.
- Read-only access through your claim system connector or SFTP extract.
- AES-256 at rest and TLS 1.3 in transit, US AWS regions only.
- Zero model training on ClaimSearch results or claim files.
Setup timeline
From kickoff to first findings.
Week 1
Source confirmation
Confirm where ClaimSearch reports land in your claim system and which Subrogation Solutions features you subscribe to.
Week 2
Mapping
Map report fields to adverse party and carrier records; validate on 200 recent claims.
Week 3
Production
ClaimSearch results feed every score and demand package in scope.
FAQ
Verisk ISO ClaimSearch integration FAQ
No. Ishqkala reads results your organization already receives under its own subscription. It is not a Verisk partner integration and does not query ClaimSearch itself.
Ishqkala works with match reports and Carrier Identified Notifications alone, and fills adverse carrier gaps from notes and police reports.
Never. Results stay in your tenant and are used only for your claims.
Yes. A confirmed adverse carrier and active coverage raise collectability, which raises the priority of the opportunity.
More estimating & data
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.