Verisk

Verisk is a data analytics and claims tooling provider for property and casualty insurance, supplying the rating, risk, and claims data that much of the industry’s infrastructure, including Punchlist Manager, is built on. ProPay integrates with Verisk so that the claim itself, intake, triage, authorization, parts, and payment, is executed on top of it, rather than replacing it.

What ProPay does with Verisk

ProPay reads coverage and claim context from Verisk, risk and rating data, industry claims benchmarks, and analytics feeds, and writes the resulting claim progress back as the work happens. At first notice of loss, ProPay captures claim data 24/7 through web form, chat, SMS, and voice, and validates that coverage against what Verisk holds before dispatch.

ProPay’s homeowner triage runs over SMS, capturing model and serial numbers, photos, and symptom detail directly from the homeowner’s phone, with 80 to 83 percent of homeowners responding after a claim is opened. That conversation, not a call center script, is what feeds the record in Verisk.

Where a truck roll is warranted, ProPay applies your configured business rules, repair versus replace, auto-approval inside a threshold, then sources parts across suppliers, tracks the order through delivery and return, and validates the resulting invoice against the authorization record before payment releases. Every step writes back to Verisk as the record of what happened.

How the Verisk connection works

Verisk’s data products are typically consumed through structured data feeds or APIs depending on the specific product, which is what a ProPay connection would read against.

Where Verisk doesn’t expose a field ProPay needs, a Forward Deployed Engineer builds the mapping during deployment rather than asking Verisk to change. Modules go live independently, FNOL, triage, authorization, parts, and payment can each be switched on against Verisk one at a time.

What stays in Verisk

Industry rating data, risk analytics, and Verisk’s own data products stay exactly where Verisk maintains them.

What changes is how much of the routine claim work a person has to do by hand inside Verisk. ProPay handles the repetitive execution and routes exceptions to a human, so your team spends its time on the claims that actually need judgment.

Data handling and security

Each ProPay client, including the connection to Verisk, runs on a company-specific instance, one carrier’s claim data and contract terms are never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.

Every recommendation ProPay makes against Verisk’s data carries a confidence level and the inputs behind it, and is logged. Recommendations above your configured thresholds route to a person rather than executing automatically.

Deploying the integration

A dedicated Forward Deployed Engineer works alongside your team to build and maintain the Verisk connection, mapping fields and handling the edge cases specific to how your program is configured inside Verisk today.

Frequently asked questions about ProPay and Verisk

Does ProPay replace Verisk?

No. Verisk continues to supply rating and risk data; a ProPay connection would consume that data as context for authorization decisions, not replace it.

How does ProPay connect to Verisk?

Verisk’s data products are typically consumed through structured data feeds or APIs depending on the specific product, which is what a ProPay connection would read against. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

What does Verisk still control after ProPay is connected?

Industry rating data, risk analytics, and Verisk’s own data products stay exactly where Verisk maintains them.