Insurity
Cloud insurance software and analytics for property and casualty carriers
ProPay integrates with Insurity, a policy, risk, or CRM platform. Insurity is cloud insurance software and analytics used by P&C carriers, MGAs, and risk pools for policy administration, claims, and underwriting analytics. ProPay authorizes claims against the context it holds and writes decisions back.
Insurity is cloud insurance software and analytics used by P&C carriers, MGAs, and risk pools for policy administration, claims, and underwriting analytics. ProPay reads the context Insurity already holds and authorizes the claim against it, writing the decision, and everything that led to it, back as the record of what happened.
What ProPay does with Insurity
ProPay captures claim data 24/7 through web form, chat, SMS, and voice, and validates it against the coverage Insurity holds, policy data, claim files, and underwriting analytics, before authorizing repair versus replace, or approving inside your configured thresholds.
The context that reaches Insurity isn’t a call transcript, it’s a structured SMS conversation. ProPay triages the homeowner over text, with 80 to 83 percent responding, and that exchange is what populates the fields Insurity needs to authorize the claim correctly the first time.
From there, ProPay sources parts across suppliers, tracks the order, and validates the resulting invoice against the authorization record before payment releases, with every decision written back to Insurity alongside the confidence level it was made at.
How the Insurity connection works
Insurity’s platform exposes an API for policy and claims data, which is where ProPay reads and writes.
Where Insurity doesn’t expose a field ProPay needs, a Forward Deployed Engineer builds the mapping during deployment rather than asking Insurity to change. Authorization, parts, and payment can go live against Insurity independently of each other.
What stays in Insurity
Underwriting analytics and policy administration stay inside Insurity.
What changes is how much of the authorization decision a person has to make by hand. ProPay applies your business rules against the context in Insurity and routes only the exceptions to a reviewer.
Data handling and security
The connection to Insurity runs on a company-specific ProPay instance, one carrier’s policy and claim data are never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.
Every authorization decision carries a confidence level and the inputs it drew from Insurity, and is logged. Decisions above your configured value or confidence thresholds route to a person before anything executes.
Deploying the integration
A dedicated Forward Deployed Engineer works with your team to build and maintain the Insurity connection, mapping the specific fields and authorization rules your program already runs on.
Frequently asked questions about ProPay and Insurity
Does ProPay replace Insurity?
No. Insurity remains the system of record for the underlying policy and case data; ProPay executes the authorization decision and the work that follows it.
How does ProPay connect to Insurity?
Insurity’s platform exposes an API for policy and claims data, which is where ProPay reads and writes. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.
Are authorization decisions against Insurity auditable?
Yes. Every decision carries a confidence level and the specific inputs from Insurity it was based on, and is logged for review.
