Jobber

Jobber is scheduling, quoting, and invoicing software built for home service businesses, popular with small teams across trades beyond just appliance and HVAC, cleaning, lawn care, and general field services. Polygrade sits in front of Jobber 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 Polygrade does with Jobber

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

Before Jobber ever sees a work order, Polygrade 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 Jobber at all: 7.9 percent of submitted claims are resolved without a truck roll.

As the job moves through Jobber, quotes, job schedules, and invoices, Polygrade 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 Jobber connection works

Jobber’s API covers job and client data, which is where Polygrade reads and writes.

Where Jobber doesn’t expose a field Polygrade needs, a Forward Deployed Engineer builds the mapping during deployment. Triage, authorization, and payment can each go live against Jobber independently of one another.

What stays in Jobber

Quoting, scheduling, and the business’s client relationship management stay inside Jobber.

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

Data handling and security

The connection to Jobber runs on a company-specific Polygrade instance, one client’s job data and customer records are never accessible to another. Polygrade 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 Jobber.

Deploying the integration

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

Frequently asked questions about Polygrade and Jobber

Does Polygrade replace Jobber?

No. Jobber keeps handling scheduling and dispatch execution; Polygrade decides upstream what should reach it and enriches the job before it does.

How does Polygrade connect to Jobber?

Jobber’s API covers job and client data, which is where Polygrade reads and writes. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.

Does Polygrade reduce truck rolls sent to Jobber?

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