FieldEdge
Field service management for HVAC, plumbing, and electrical contractors
Polygrade integrates with FieldEdge, a field service management platform. FieldEdge is field service management software for HVAC, plumbing, and electrical contractors, with a dispatch board and technician tracking built specifically for those trades. Polygrade's triage decides what reaches it, then reads job status back to drive automated updates.
FieldEdge is field service management software for HVAC, plumbing, and electrical contractors, with a dispatch board and technician tracking built specifically for those trades. Polygrade sits in front of FieldEdge 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 FieldEdge
Polygrade engages the homeowner over SMS to collect model and serial numbers, photos, and symptom detail, then recommends repair, replacement, or call avoidance, before FieldEdge is involved at all. Where a truck roll is warranted, Polygrade passes FieldEdge an enriched job: a predicted job code and the parts the technician is likely to need.
Before FieldEdge 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 FieldEdge at all: 7.9 percent of submitted claims are resolved without a truck roll.
As the job moves through FieldEdge, dispatch board entries, technician locations, and job history, 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 FieldEdge connection works
FieldEdge supports API access to job and dispatch data, which is what Polygrade reads and writes against.
Where FieldEdge 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 FieldEdge independently of one another.
What stays in FieldEdge
The dispatch board, technician tracking, and trade-specific job history stay inside FieldEdge.
What changes is how much of a dispatcher’s day is spent on jobs that never needed a technician. Polygrade resolves those before FieldEdge sees them, so the jobs that do reach FieldEdge are the ones that actually warranted a truck roll.
Data handling and security
The connection to FieldEdge 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 FieldEdge.
Deploying the integration
A dedicated Forward Deployed Engineer builds and maintains the FieldEdge connection alongside your team, mapping job codes and dispatch fields to how FieldEdge is configured for your operation.
Frequently asked questions about Polygrade and FieldEdge
Does Polygrade replace FieldEdge?
No. FieldEdge 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 FieldEdge?
FieldEdge supports API access to job and dispatch data, which is what Polygrade reads and writes against. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.
Does Polygrade reduce truck rolls sent to FieldEdge?
Yes. Triage resolves 7.9 percent of submitted claims without dispatch, so fewer unnecessary jobs reach FieldEdge in the first place.
