Yazh (Yaal), our Integration Gateway, gives every broker, TPA, MGA and vendor one self-service route into ClaimCenter. First notice of loss arrives in the format ClaimCenter expects.
The Problem
FNOL and TPA Submissions Reach ClaimCenter Through Too Many Custom Builds
First notice of loss arrives from TPAs, brokers, MGAs and vendors. ClaimCenter’s own rules decide whether each submission becomes a claim.
Every Sender Builds Its Own Connector
Each sender builds its own module to map fields and call Guidewire APIs, without built-in security, auditing, or monitoring, requiring coordination for every change.
FNOL Takes More Than One Call
Guidewire’s Cloud API creates a draft claim first, then submits it to become an open claim. Each sender has to build and maintain both steps.
Submissions Have to Meet ClaimCenter’s Rules
Cloud API will not create a claim against a policy that was not in force on the loss date. The claim must also reach the required validation level, so incomplete submissions stall.
The Solution
How does InsOps Help?
Yazh (Yaal) Gets Claim Submissions Into ClaimCenter Faster
Self-service sign-up
Senders register with a one-time passcode, receive an API username and key, and choose their line of business.
Payload upload with syntax checks
A sender uploads a sample FNOL or TPA payload, and Yazh (Yaal) checks its syntax before mapping starts.
Suggested mapping, confirmed by a person
LiLa suggests how each sender field maps to ClaimCenter. A person on your team reviews and confirms it.
Value translation
Yazh (Yaal) translates each sender’s values into the values ClaimCenter expects.
Test calls before go-live
Senders and your team test the route end to end before any live claim is sent.
Secured requests, one dashboard
Every request passes a firewall, authentication, authorization and validation. Requests, responses and audit entries stay on one dashboard
FAQ