Skedulo

Skedulo is deskless workforce scheduling software used across industries beyond home services, healthcare, telecom, and field sales, anywhere a mobile workforce needs to be scheduled and tracked. ProPay sits in front of Skedulo 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 Skedulo

ProPay engages the homeowner over SMS to collect model and serial numbers, photos, and symptom detail, then recommends repair, replacement, or call avoidance, before Skedulo is involved at all. Where a truck roll is warranted, ProPay passes Skedulo an enriched job: a predicted job code and the parts the technician is likely to need.

Before Skedulo 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 Skedulo at all: 7.9 percent of submitted claims are resolved without a truck roll.

As the job moves through Skedulo, shift schedules, technician availability, and assignment records, 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 Skedulo connection works

Skedulo exposes an API for scheduling and assignment data, which is where ProPay reads and writes.

Where Skedulo 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 Skedulo independently of one another.

What stays in Skedulo

Workforce scheduling logic and availability management stay inside Skedulo.

What changes is how much of a dispatcher’s day is spent on jobs that never needed a technician. ProPay resolves those before Skedulo sees them, so the jobs that do reach Skedulo are the ones that actually warranted a truck roll.

Data handling and security

The connection to Skedulo 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 Skedulo.

Deploying the integration

A dedicated Forward Deployed Engineer builds and maintains the Skedulo connection alongside your team, mapping job codes and dispatch fields to how Skedulo is configured for your operation.

Frequently asked questions about ProPay and Skedulo

Does ProPay replace Skedulo?

No. Skedulo 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 Skedulo?

Skedulo exposes an API for scheduling and assignment data, which is where ProPay reads and writes. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

Does ProPay reduce truck rolls sent to Skedulo?

Yes. Triage resolves 7.9 percent of submitted claims without dispatch, so fewer unnecessary jobs reach Skedulo in the first place.