Core claims systems integration
Ishqkala + Guidewire ClaimCenter
Event-driven subrogation detection inside ClaimCenter, on Guidewire Cloud or self-managed.
Overview
Ishqkala connects to ClaimCenter through the InsuranceSuite Cloud API, App Events and Integration Gateway on Guidewire Cloud, or through event messaging and web services on self-managed releases. New notes, documents and exposures are scored within minutes of being saved, and findings come back as ClaimCenter Activities, Notes and, where your roles allow, a draft Subrogation record. Closed-claim sweeps read Cloud Data Access Parquet tables or a scheduled SFTP extract, so historical scans never touch production API capacity.
Use cases
- Flag a rear-end collision at FNOL when the first note records that the other driver was cited.
- Sweep 24 months of closed homeowners water claims for failed supply lines and plumber workmanship.
- Route fire claims whose origin and cause report names a contractor to subrogation the same day.
- Prevent SOL expirations with Activities due well ahead of the state limitation date.
Architecture & data flow
How data moves between Guidewire ClaimCenter and Ishqkala.
01
Event capture
App Events sends business events (note added, document added, claim closed) as CloudEvents messages to a Ishqkala webhook or Integration Gateway app.
02
Claim hydration
A scoped service account calls the Claim API for exposures, contacts, notes and document content.
03
Ingestion and NLP
Documents are OCR'd and every liability signal is tied back to its source note or page.
04
Scoring and SOL tracking
Recoverable dollars, win probability and days until SOL expiry combine into one priority score.
05
Write-back or manifest
Open claims get an Activity and Finding note. Closed-claim sweeps read Cloud Data Access or SFTP and return a Recovery Opportunity Manifest instead.
API data flow
Objects read and written.
| Object | Direction | What Ishqkala does with it |
|---|---|---|
| Claim | Read | Loss date, loss cause, loss state, line of business, status and closed date. Loss state and date start the SOL clock. |
| Exposure and Incident | Read | Exposure type, coverage, the linked vehicle or property incident, and paid and reserved amounts. |
| ClaimContact | Read | Involved parties and roles (other driver, contractor, property owner) used to name the adverse party. |
| Note | Read / write | Every adjuster note is parsed. Ishqkala writes one Finding note per opportunity with the cited source text. |
| Document | Read | Police, fire origin and cause, and engineering reports and estimates, pulled for OCR. |
| Activity | Write | A review Activity for the subrogation queue, due ahead of the earliest limitation or notice deadline. |
| SubrogationSummary and Subrogation | Read / write | Reads existing subrogation to avoid duplicates. With editsubrodetails granted, drafts a Subrogation record for adjuster confirmation. |
| Matter | Read | Open litigation matters, so Ishqkala does not flag a recovery your counsel already handles. |
Security & data governance
Controls on this connection.
- Dedicated service account with API roles limited to the endpoints Ishqkala calls; no financial write permissions.
- Service-to-service tokens from your Guidewire Cloud identity provider; no shared user passwords.
- AES-256 at rest, TLS 1.3 in transit, US AWS regions only, AWS GovCloud available.
- Zero model training on claim files; bodily injury documents handled under a HIPAA BAA.
- Every API call and write-back logged for SOC 2 Type II and internal audit review.
Setup timeline
From kickoff to first findings.
Week 1
Access and scope
Confirm release, provision the service account and roles, and agree App Events subscriptions.
Weeks 2 to 3
Mapping and baseline
Map loss cause, line and state typecodes; run a closed-claim baseline.
Weeks 4 to 5
Write-back and UAT
Configure Activity patterns, routing and thresholds; subrogation leads review findings in pre-production.
Week 6
Production cutover
Enable production events and tune thresholds after the first 500 scored claims.
FAQ
Guidewire ClaimCenter integration FAQ
No. Ishqkala uses the Cloud API, App Events and, optionally, an Integration Gateway app in your tenant. It claims no Guidewire partnership; it runs on interfaces Guidewire publishes and roles your team grants.
Yes. Ishqkala reads events from a messaging destination your team configures and calls the web services your release exposes. A nightly SFTP extract works where outbound connectivity is restricted.
No. Guidewire blocks subrogation changes on closed or archived claims. Your team decides which manifest claims to reopen, and normal write-back applies once they are open.
Your licensed claim professionals. Ishqkala never contacts the adverse party or books a recovery.
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.