Inline Admin

Inline Data Systems’ Inline Admin is extended warranty claims processing software used across home, automotive, and consumer product warranty programs, handling claim intake through adjudication. ProPay integrates with Inline Admin 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 Inline Admin

ProPay reads coverage and claim context from Inline Admin, claim intake forms, adjudication decisions, and program-level claim history, 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 Inline Admin 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 Inline Admin.

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

How the Inline Admin connection works

Inline Admin supports structured file and API-based claim data exchange, which is what ProPay reads and writes against.

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

What stays in Inline Admin

Claim adjudication rules and the historical claims ledger for each program stay inside Inline Admin.

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

Frequently asked questions about ProPay and Inline Admin

Does ProPay replace Inline Admin?

No. Inline Admin continues adjudicating claims against program rules; ProPay handles the triage and execution work that feeds it.

How does ProPay connect to Inline Admin?

Inline Admin supports structured file and API-based claim data exchange, which is what ProPay reads and writes against. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

What does Inline Admin still control after ProPay is connected?

Claim adjudication rules and the historical claims ledger for each program stay inside Inline Admin.