Zuper
Field service management with scheduling, dispatch, and customer portal
ProPay integrates with Zuper, a field service management platform. Zuper is field service management software with scheduling, dispatch, and a customer-facing portal, aimed at mid-market service businesses. ProPay's triage decides what reaches it, then reads job status back to drive automated updates.
Zuper is field service management software with scheduling, dispatch, and a customer-facing portal, aimed at mid-market service businesses. ProPay sits in front of Zuper and decides what actually needs to reach it, a work order only gets created after triage has already ruled out a no-truck-roll resolution.
What ProPay does with Zuper
ProPay engages the homeowner over SMS to collect model and serial numbers, photos, and symptom detail, then recommends repair, replacement, or call avoidance, before Zuper is involved at all. Where a truck roll is warranted, ProPay passes Zuper an enriched job: a predicted job code and the parts the technician is likely to need.
Before Zuper ever sees a work order, ProPay has already engaged the homeowner over SMS, collecting model and serial numbers, photos, and symptom detail, with 80 to 83 percent of homeowners responding. That triage is what decides whether a job reaches Zuper at all: 7.9 percent of submitted claims are resolved without a truck roll.
As the job moves through Zuper, job schedules, dispatch assignments, and customer portal activity, ProPay reads status back to drive automated homeowner and contractor updates over SMS, and validates the resulting invoice against the authorization record before payment releases.
How the Zuper connection works
Zuper’s API supports job and scheduling data, which is what ProPay reads and writes against.
Where Zuper doesn’t expose a field ProPay needs, a Forward Deployed Engineer builds the mapping during deployment. Triage, authorization, and payment can each go live against Zuper independently of one another.
What stays in Zuper
Scheduling, dispatch, and the customer portal experience stay inside Zuper.
What changes is how much of a dispatcher’s day is spent on jobs that never needed a technician. ProPay resolves those before Zuper sees them, so the jobs that do reach Zuper are the ones that actually warranted a truck roll.
Data handling and security
The connection to Zuper runs on a company-specific ProPay instance, one client’s job data and customer records are never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.
Every triage recommendation carries a confidence level and the inputs behind it, and is logged. Recommendations outside your configured thresholds route to a person before a job ever reaches Zuper.
Deploying the integration
A dedicated Forward Deployed Engineer builds and maintains the Zuper connection alongside your team, mapping job codes and dispatch fields to how Zuper is configured for your operation.
Frequently asked questions about ProPay and Zuper
Does ProPay replace Zuper?
No. Zuper keeps handling scheduling and dispatch execution; ProPay decides upstream what should reach it and enriches the job before it does.
How does ProPay connect to Zuper?
Zuper’s API supports job and scheduling data, which is what ProPay reads and writes against. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.
Does ProPay reduce truck rolls sent to Zuper?
Yes. Triage resolves 7.9 percent of submitted claims without dispatch, so fewer unnecessary jobs reach Zuper in the first place.
