Estimating & data integration
Ishqkala + LexisNexis Carrier Discovery
Adverse carrier and policy details from LexisNexis Carrier Discovery results, attached to opportunities.
Overview
LexisNexis Carrier Discovery returns insurance carrier information on claimants and other parties in an auto accident: subjects on the policy, carrier name, policy number, effective dates, vehicles insured and coverage types, from a name and address or VIN search. Ishqkala reads the Carrier Discovery results your team orders through OrderPoint, Accurint for Insurance or batch delivery, and uses them to identify the at-fault party's carrier. TPAs and self-insureds using LexisNexis Carrier ID follow the same pattern.
Use cases
- Identify the at-fault driver's carrier on claims first opened as uninsured motorist losses.
- Confirm the adverse policy was in force on the date of loss before sending a demand.
- Help TPAs and self-insureds find adverse carriers through Carrier ID for fleet collisions.
- Clear a backlog of closed-file opportunities that stalled because no carrier was identified.
Architecture & data flow
How data moves between LexisNexis Carrier Discovery and Ishqkala.
01
Gap detection
Ishqkala flags opportunities where the adverse party is known but the carrier is not.
02
Search list
A search list is exported for your team, who run it under your LexisNexis account and permissible use selections.
03
Results returned
Batch result files or attached reports come back to Ishqkala over SFTP or through your claim system.
04
Match and verify
Results are matched to the opportunity by name, address and VIN, and policy dates are checked against the loss date.
05
Rescore
An identified carrier raises collectability and moves the opportunity up the queue.
API data flow
Objects read and written.
| Object | Direction | What Ishqkala does with it |
|---|---|---|
| Search request list | Write | An export of adverse parties missing a carrier (name, address, VIN, date of loss) for your team to submit through your LexisNexis access. |
| Carrier and policy | Read | Carrier name, policy number and effective dates, checked against the date of loss. |
| Subjects on policy | Read | Everyone listed on the policy, to confirm the at-fault driver is a listed operator or household member. |
| Vehicles insured | Read | Insured vehicles, matched by VIN to the vehicle in the police report. |
| Coverage types | Read | Coverage types on the adverse policy, which inform collectability and routing. |
Security & data governance
Controls on this connection.
- Ishqkala does not run LexisNexis searches or hold LexisNexis credentials; your users order every search.
- Results used only for claims purposes permitted under your LexisNexis agreement, never for eligibility or underwriting decisions.
- Search lists and result files exchanged over SFTP with key-based authentication and PGP encryption.
- AES-256 at rest and TLS 1.3 in transit, US AWS regions only, with zero model training on results.
Setup timeline
From kickoff to first findings.
Week 1
Process design
Agree the search list layout, who submits it, and how results return.
Week 2
Validation run
Run 100 adverse parties through Carrier Discovery and validate the matches.
Week 3
Production
Daily or weekly search lists and result loads on a fixed schedule.
FAQ
LexisNexis Carrier Discovery integration FAQ
No. Your users run searches under your LexisNexis account. Ishqkala prepares the list and reads the results.
LexisNexis offers Carrier ID for TPAs and self-insured organizations, with private passenger and commercial vehicle policy information. Ishqkala handles its results the same way.
No formal partnership is implied. Ishqkala works with results your organization lawfully obtains.
The opportunity stays open with a no-carrier flag. Your team decides whether a direct claim against the individual is worth pursuing.
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.