How to Choose a CPI Provider for BHPH Dealers and Auto Lenders

Start with the portfolio problem the CPI provider must solve.

A BHPH dealer may need to stop chasing insurance proof, reduce uninsured total losses, avoid losing sales to insurance friction, improve account corrections, obtain better claim support, lower total program cost, or participate in results. A finance company may prioritize data controls, scale, security, state coverage, reporting, vendor oversight, and implementation governance.

Write those outcomes before reviewing providers. Otherwise, the comparison will follow the vendor’s sales presentation rather than the dealer’s or lender’s risk. Use the CPI provider evaluation scorecard to assign a priority, owner, measurement, and completion standard to each desired outcome.

Know which company performs every regulated and operational role.

A CPI presentation may involve a carrier, licensed producer or agency, program manager, administrator, insurance-tracking company, claims handler, technology provider, mailing vendor, data processor, reinsurer, and dealer-facing relationship company. The names and responsibilities should appear in written documents—not remain implied by one brand logo.

Verify authority, licensing where applicable, appointments or relationships, state availability, policy and certificate forms, administrator responsibilities, subcontractors, complaint ownership, and escalation paths. Auto Capital Protection identifies its coordination and dealer-relationship role while documenting the approved insurance and administrative parties for the actual program. For the same evidence-first diligence on the company publishing this guide, review what to evaluate about Auto Capital Protection before treating any public statement as decision evidence.

• Who is the carrier and which entity issues the policy or certificate?
• Who sells, solicits, negotiates, administers, tracks, notices, adjusts, and handles claims?
• Which parties receive compensation and for which service?
• Which entity has authority to approve placement, cancellation, claim, refund, or exception decisions?
• Which licenses, approvals, agreements, and state availability support those roles?

Read the policy, finance agreement, and program documents together.

The product comparison should identify the insured interest, covered losses, collateral, effective-date rules, valuation, limits, deductible, exclusions, other insurance, salvage, claim prerequisites, termination, and state-specific forms. The finance agreement should support the insurance requirement and permitted remedy, while notices and account treatment should match the approved program.

Avoid descriptions such as “full coverage,” “guaranteed compliance,” “automatic claim payment,” or “covers everyone.” Require the provider to mark which statements are policy terms, program procedures, service commitments, legal interpretations, or sales estimates.

Test how the provider handles evidence before and after placement.

Ask for a live demonstration of evidence intake, matching, exception reasons, borrower communications, document upload, manual review, suppression, placement approval, proof received after placement, cancellation, effective-date correction, credit or refund, complaint escalation, and audit history. A screenshot of a dashboard is not the same as testing the workflow.

Evaluate the borrower experience in plain language: what the customer receives, how proof is submitted, which status is visible, how quickly evidence is reviewed, who answers questions, and what happens when the customer disputes the date or charge. Accurate correction is as important as accurate placement.

• Evidence standards and exception taxonomy.
• Communication channels, language options, approved templates, and delivery evidence.
• Submission accessibility, review turnaround, escalation, and status history.
• Placement authorization, suppression, cancellation, credit, refund, and reconciliation controls.
• False-positive, aged-exception, correction, complaint, and service-level reporting.

Follow a sample claim from first notice to the servicing account.

Request separate examples for a repairable collision, total loss, theft, other insurance, coverage dispute, missing document, deductible, salvage, and denial. Identify who receives the claim, what documentation is required, when status updates occur, who has authority, where proceeds go, and how the settlement affects the receivable.

Review claim frequency, severity, cycle time, closure reasons, denials, disputes, recoveries, salvage, and unresolved aging. Testimonials about “fast claims” are not a substitute for policy terms, service levels, reporting, and references that match the dealer’s portfolio.

Make the integration and data-security promises testable.

Define the lender’s systems, fields, format, cadence, validation, error handling, access controls, encryption, retention, incident response, business continuity, record ownership, and data return. Determine whether the provider uses secure files, an API, a portal, or manual processes and which capabilities are production-ready for the dealer’s actual DMS or loan-servicing platform.

Security due diligence should cover the provider and relevant subcontractors. Ask for current evidence appropriate to the relationship, documented incident-notification terms, least-privilege access, user administration, audit logging, data location, backup and recovery, testing, and a plan for terminating access.

Require metrics that reveal quality, not just production.

A useful CPI report should include accounts onboarded, evidence match rate, exceptions by reason and aging, borrower communications, placements, suppressions, cancellations, date corrections, credits, refunds, claims, complaints, service levels, data errors, and unresolved issues. Management should be able to trace summary numbers back to the underlying account history through authorized systems.

The provider agreement should define reporting cadence, data definitions, delivery format, record retention, access, audit rights, issue remediation, change notices, regulator support, and exit data. If the dealer cannot verify the numbers, the dashboard is decoration rather than control evidence.

Compare total program cost and dealer economics under multiple scenarios.

Normalize coverage, deductible, limits, services, volume, staff responsibilities, claims, state scope, contract term, fees, and retained risk before comparing price. Include setup, integration, tracking, notices, postage, documents, transactions, claims, cancellation, reporting, minimums, termination, data return, and internal staff work.

For participation, identify the exact formula, claims, reserves, expenses, fees, calculation period, adjustments, distribution conditions, termination, and downside treatment. Compare contractual participation and dealer-owned reinsurance against their actual documents, roles, ownership, capital, and risk. Neither structure guarantees a profit.

A capable provider should configure the program around the portfolio—within approved boundaries.

Customization can include solution mix, workflow responsibilities, evidence channels, integrations, exception routing, reporting, training, escalation, claims support, rollout sequence, participation path, and approved product options. It cannot override licensing, policy forms, state availability, underwriting, borrower protections, reserve requirements, or contract authority.

Require a dated implementation plan with discovery, documentation, data mapping, integration, notice and borrower-experience review, accounting, claims, security, testing, training, controlled conversion, reconciliation, and post-launch QA. Each dependency needs an owner and measurable acceptance criteria. If the unresolved question is product fit rather than provider execution, compare adjacent auto-finance protection categories before scoring companies.

Use the framework to compare CPI, tracking, participation, reinsurance, VSI, warranty, GAP, technology, reporting, and supporting categories against the actual program, provider, role, contract, and state evidence.

Judge the provider by how it handles a transition and a future exit.

An existing-program transition may involve in-force policies, evidence history, open claims, notices, account charges, cancellations, credits, refunds, complaints, historical reporting, participation rights, reserves, data conversion, vendor access, and borrower communications. The incumbent and new provider responsibilities should be written before conversion.

The new agreement should also define termination notice, data export, record format, open claims, run-off, reserves, unpaid fees, borrower support, access shutdown, transition assistance, ownership of reports, and survival of audit or complaint obligations. A provider that cannot explain exit is not ready to own implementation.