Brokers and MGAs send their own payload to one InsOps endpoint. PolicyCenter receives a submission in the format it expects, and carriers add distribution partners without new IT work.
The Problem
Insurance data migrations are slow and expensive
Every sender builds its own connector
Brokers, MGAs and TPAs spend months building custom PolicyCenter integrations, while carriers handle each sender’s queries individually without built-in security, auditing or monitoring.
One change reaches every sender
When endpoints change or Guidewire releases updates, all 50 sender connectors may need retesting. Submissions slow as senders rework modules, consuming carrier IT time.
Growth waits on IT capacity
Each new partner requires IT support and testing, limiting onboarding capacity. Fewer partners mean fewer submissions and less premium written.
How does InsOps Help?
How Yazh (Yaal) Moves Submissions Into PolicyCenter
Self-Service Sign-Up
A partner registers with 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 PolicyCenter fields and lists the ones it could not match for a person to resolve.
Value Translation
Source values become PolicyCenter codes, so a partner’s “Commercial Property” arrives as the code your instance expects.
Test Before Live
Partners run submission clearance, account creation and submission creation in a test environment, then check the result in PolicyCenter.
Incomplete Payloads Returned
A payload with gaps goes back to the sender to complete instead of reaching your queue.
Changes Handled Once
When PolicyCenter or a carrier endpoint changes, InsOps updates the mapping in one place. A new mandatory field raises an alert, and a default value keeps submissions moving.
FAQ