Brokers and MGAs send their own payload to one InsOps endpoint through Yazh (Yaal), our Integration Gateway. Your policy system receives submissions in the format it expects, and carriers can add distribution partners without new IT work.
The Problem
Submissions Reach Your Policy System Through Too Many Custom Builds
Brokers, MGAs and TPAs each send submissions in their own way, and every new partner adds another integration for the carrier to support.
Every Sender Builds Its Own Connector
Each broker, MGA and TPA builds a custom integration against your policy system's API. It takes months and often lacks built-in security, auditing and monitoring.
One Change Reaches Every Sender
When an endpoint or a vendor release changes, every sender connector may need retesting. Submissions slow down while senders rework their modules and carrier IT time is used up.
Growth Waits on IT Capacity
Each new partner needs IT support and testing, which limits onboarding. Fewer partners means fewer submissions and less premium written.
The Solution
How does InsOps Help?
How Yazh (Yaal) Moves Submissions Into Your Policy System
Self-Service Sign-Up
A partner registers using a one-time password, receives an API username and key, and selects the lines of business it will send.
LiLa-Suggested Mapping
The partner uploads a sample JSON payload. LiLa maps source fields to your policy system's fields and flags any it could not match for a person to resolve.
Value Translation
Source values are converted into the codes your policy system expects, so a partner's label arrives as the correct code.
Test Before Live
Partners run submission clearance, account creation and submission creation in a test environment, then verify the results.
Incomplete Payloads Returned
Payloads with gaps go back to the sender to complete rather than entering your queue.
Changes Handled Once
When your policy system or a carrier endpoint changes, InsOps updates the mapping in one place. New mandatory fields trigger an alert, and default values keep submissions flowing.
FAQ
What happens when a sender sends a submission?
How is this different from a connector?
Who reviews the mapping?