Assurant

Assurant is a global provider of extended warranty and device protection programs, underwriting and administering protection plans across mobile, appliance, and other consumer product categories. ProPay integrates with Assurant 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 Assurant

ProPay reads coverage and claim context from Assurant, protection plan terms, underwriting data, and claim history across programs, 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 Assurant 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 Assurant.

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 Assurant as the record of what happened.

How the Assurant connection works

Assurant’s scale means integration is typically negotiated per program and built through a custom connector or file exchange, set up by a Forward Deployed Engineer.

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

What stays in Assurant

Underwriting, program terms, and Assurant’s own risk management stay exactly where they are.

What changes is how much of the routine claim work a person has to do by hand inside Assurant. 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 Assurant, 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 Assurant’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 Assurant connection, mapping fields and handling the edge cases specific to how your program is configured inside Assurant today.

Frequently asked questions about ProPay and Assurant

Does ProPay replace Assurant?

No. Assurant continues to underwrite and hold program terms; ProPay executes the claim workflow for programs configured to use it.

How does ProPay connect to Assurant?

Assurant’s scale means integration is typically negotiated per program and built through a custom connector or file exchange, set up by a Forward Deployed Engineer. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

What does Assurant still control after ProPay is connected?

Underwriting, program terms, and Assurant’s own risk management stay exactly where they are.