Estimating & data integration
Ishqkala + CCC ONE
Auto physical damage estimates from CCC ONE, structured for demand packages and arbitration.
Overview
CCC ONE is the estimating and claims platform used widely across US auto physical damage by carrier appraisers and repair facilities. Ishqkala reads the CCC ONE estimates, supplements and total loss valuations your organization already receives, as CIECA BMS estimate data or estimate reports stored in your claim system or staged by your team. Line items, labor operations, parts and point of impact feed both the liability analysis and the damages section of an Arbitration Forums filing or a direct demand.
Use cases
- Confirm a rear-end impact from the point of impact and rear body damage before demanding 100% liability.
- Build an Automobile Subrogation Forum filing with repair, rental and towing damages broken out.
- Net salvage proceeds out of total loss recoveries so the demand matches actual loss.
- Recover the insured's deductible on clear-liability collisions within days of the final supplement.
Architecture & data flow
How data moves between CCC ONE and Ishqkala.
01
Estimate received
Your existing CCC ONE workflow delivers the estimate to your claim system, or your team stages it over SFTP.
02
Parse
Ishqkala reads BMS data or the estimate report into header, line items, supplements and totals.
03
Cross-check liability
Point of impact and damage pattern are compared with notes, statements and the police report.
04
Damages model
Repair or total loss damages are combined with rental, towing and deductible payments from your claim system.
05
Package
The estimate, supplements and photos become indexed exhibits for the demand or arbitration filing.
API data flow
Objects read and written.
| Object | Direction | What Ishqkala does with it |
|---|---|---|
| Estimate header | Read | VIN, year, make, model, point of impact and loss date. Point of impact is checked against the adjuster's account of a rear-end or side impact. |
| Line items and labor operations | Read | Parts, labor and refinish hours, with OEM and aftermarket parts identified, the fields adverse carriers commonly challenge. |
| Supplements | Read | Each supplement kept in sequence with the original estimate, so the demand reflects final paid damages. |
| Total loss valuation | Read | Actual cash value, taxes and fees, and salvage, used to compute the net recoverable after salvage proceeds. |
| Damage photos | Read | Photos attached to the estimate, included as exhibits in the demand package. |
Security & data governance
Controls on this connection.
- Read-only: Ishqkala never edits estimates or sends data back to CCC.
- Files received over SFTP with key-based authentication, or read from your claim system with a scoped service account.
- AES-256 at rest and TLS 1.3 in transit, US AWS regions only.
- Zero model training on your estimates or claim files.
- Access to estimate data limited to roles your administrators assign in Ishqkala.
Setup timeline
From kickoff to first findings.
Week 1
Source confirmation
Confirm whether estimates reach your claim system as BMS data, PDF reports or both.
Week 2
Parse validation
Parse 200 recent estimates and reconcile totals with paid amounts.
Week 3
Production
Estimates feed scoring and packages for every auto claim in scope.
FAQ
CCC ONE integration FAQ
No. Ishqkala reads estimate data your organization already receives. It does not sign in to CCC ONE, and no partnership with CCC is implied.
CIECA BMS estimate data and PDF estimate reports. Most carriers already store one or both with the claim.
Supplements are linked to the original estimate by their document identifier and sequence, and the demand uses the final paid figures.
No. It presents the estimate as paid. Your appraisers and recovery staff decide how to answer a damages dispute.
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.