Home One / WarrantyBase

Home One (formerly marketed as WarrantyBase) is warranty administration software built specifically for home warranty companies, policy sales and configuration, contract management, claims processing, and automated renewals, running since 2012. ProPay integrates with Home One / WarrantyBase 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 Home One / WarrantyBase

ProPay reads coverage and claim context from Home One / WarrantyBase, policy contracts, renewal schedules, and claim records, 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 Home One / WarrantyBase 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 Home One / WarrantyBase.

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 Home One / WarrantyBase as the record of what happened.

How the Home One / WarrantyBase connection works

Home One exposes claims and policy data through its platform API, which is where ProPay reads coverage and writes claim outcomes.

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

What stays in Home One / WarrantyBase

Policy sales, contract configuration, and renewal automation all remain inside Home One exactly as configured today.

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

Frequently asked questions about ProPay and Home One / WarrantyBase

Does ProPay replace Home One / WarrantyBase?

No. Home One remains the system for policy sales, contracts, and renewals; ProPay executes the claim workflow against the coverage it holds.

How does ProPay connect to Home One / WarrantyBase?

Home One exposes claims and policy data through its platform API, which is where ProPay reads coverage and writes claim outcomes. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

What does Home One / WarrantyBase still control after ProPay is connected?

Policy sales, contract configuration, and renewal automation all remain inside Home One exactly as configured today.