WarrantyHub

WarrantyHub bundles claims management, a customer-facing portal, and reporting analytics for home warranty and service contract operators into one platform with published, self-serve pricing. Polygrade integrates with WarrantyHub so that the claim itself, intake, triage, authorization, parts, and payment, is executed on top of it, rather than replacing it.

What Polygrade does with WarrantyHub

Polygrade reads coverage and claim context from WarrantyHub, claim tickets, customer portal sessions, and reporting dashboards, and writes the resulting claim progress back as the work happens. At first notice of loss, Polygrade captures claim data 24/7 through web form, chat, SMS, and voice, and validates that coverage against what WarrantyHub holds before dispatch.

Polygrade’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 WarrantyHub.

Where a truck roll is warranted, Polygrade 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 WarrantyHub as the record of what happened.

How the WarrantyHub connection works

WarrantyHub’s claims module is API-accessible, which is what Polygrade reads and writes against for claim status and coverage validation.

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

What stays in WarrantyHub

The customer portal experience and WarrantyHub’s own reporting dashboards stay exactly as your team and your homeowners already use them.

What changes is how much of the routine claim work a person has to do by hand inside WarrantyHub. Polygrade 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 Polygrade client, including the connection to WarrantyHub, runs on a company-specific instance, one carrier’s claim data and contract terms are never accessible to another. Polygrade is SOC 2 compliant, with both Type I and Type II audits complete.

Every recommendation Polygrade makes against WarrantyHub’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 WarrantyHub connection, mapping fields and handling the edge cases specific to how your program is configured inside WarrantyHub today.

Frequently asked questions about Polygrade and WarrantyHub

Does Polygrade replace WarrantyHub?

No. WarrantyHub’s portal and reporting stay in place; Polygrade handles the triage, authorization, and parts work behind the claims it tracks.

How does Polygrade connect to WarrantyHub?

WarrantyHub’s claims module is API-accessible, which is what Polygrade reads and writes against for claim status and coverage validation. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

What does WarrantyHub still control after Polygrade is connected?

The customer portal experience and WarrantyHub’s own reporting dashboards stay exactly as your team and your homeowners already use them.