Tavant

Tavant’s warranty platform pairs OEM warranty administration with a service contract module and AI-driven claims analytics, including duplicate-claim detection, built for manufacturers running standard warranty and paid service contracts side by side. Tavant also powers Falcon, a dealer-facing claims transaction system used across automotive OEM networks. ProPay integrates with Tavant 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 Tavant

ProPay reads coverage and claim context from Tavant, warranty claim submissions, dealer transaction records, and duplicate-claim flags, 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 Tavant 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 Tavant.

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

How the Tavant connection works

Tavant’s platform is API-driven for claims submission and status, the layer ProPay reads and writes against.

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

What stays in Tavant

OEM warranty terms, dealer network records, and Tavant’s own duplicate-claim detection stay exactly where they are.

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

Frequently asked questions about ProPay and Tavant

Does ProPay replace Tavant?

No. Tavant continues to administer OEM warranty terms and dealer transactions; ProPay adds triage, authorization, and parts execution on top.

How does ProPay connect to Tavant?

Tavant’s platform is API-driven for claims submission and status, the layer ProPay reads and writes against. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

What does Tavant still control after ProPay is connected?

OEM warranty terms, dealer network records, and Tavant’s own duplicate-claim detection stay exactly where they are.