How to Automate FieldServio

FieldServio treats a generator as an asset with a service history

FieldServio is field service ERP for the companies that sell, install and maintain industrial equipment: air compressors, generators, forklifts and batteries, industrial boilers, and fire suppression and life safety systems.

That customer list matters more than it looks. A home service platform is organised around an address and a visit. A dealer is organised around a unit. The thing being tracked has a serial number, a warranty, a parts list, a preventive maintenance agreement and often a rental history, and it will still be on that site in fifteen years.

So the software holds several businesses at once. FieldServio puts service management, the field technician mobile app, inventory, contracts, CRM and sales, rental fleet management and a full accounting suite behind one login.

It does that because a dealer has to answer one question about any serial number: what it earned, and what it cost. Split that across four systems and nobody can.

Every unit in the field is watched on a screen FieldServio cannot open

The equipment does not report to FieldServio. It reports to the manufacturer.

A standby generator at a hospital runs its exercise cycle at two in the morning and throws a low coolant alarm. That alarm lands on the manufacturer's own remote monitoring portal and, if somebody configured it, in an email. It becomes a work order when a person types it in.

The rest of the desk work has the same shape. Warranty registration and claim status sit on the OEM's dealer portal, and a claim filed late is a repair the dealer quietly paid for. A part is on backorder at the distributor with an ETA that has moved twice. Load bank tests and annual inspections are due on units under contract, and those dates live in a spreadsheet. A large customer will not pay an emailed invoice, and wants it entered in their own payables portal.

None of that is on the dispatch board, and all of it decides what the board should say.

FieldServio

Faults triaged before the phone rings Alarms and fault codes read off the manufacturer's monitoring portal each morning and matched to the serial numbers you hold a contract on.

Warranty claimed inside the window Coverage and claim progress checked on the OEM dealer portal, so a technician quoting a repair knows who is paying for it.

Delays that reach the customer early Backorders and revised ETAs pulled from the parts distributor, so a two-week slip is known before the date you promised arrives.

Work orders and service contracts are the solved half

FieldServio handles the operating core of a dealer properly, and it is worth setting up fully before adding anything to it.

Service Management generates work orders and schedules them in seconds, with a Real-Time Job Calendar showing technician availability and scheduling driven by a dispatch map, job duration and technician teams. Proposals are created and signed off electronically. The Field Technician Mobile App captures work order information in the field, and technician checklists can be built for almost any configuration. Contract Management covers service contracts and preventive maintenance agreements along with customer signoff and approvals. Inventory Management tracks parts and how they are used, Rental Fleet Management handles rental and asset jobs, and the accounting suite invoices all of it, with Avalara calculating tax and Payroc taking the card.

Every one of those acts on a record FieldServio already holds: a unit, a work order, a contract, a part.

The manufacturer's monitoring portal holds a record it does not. So do the OEM warranty site, the distributor's stock page and the customer's payables portal, and between them they decide which trucks roll tomorrow.

A fault code can reach dispatch before the phone rings

Reverse that, and a service department stops being reactive by default.

Fault codes and alarms read off the manufacturer's monitoring portal each morning and matched against the serial numbers under contract, so the low coolant alarm from two in the morning is on the board before the customer knows it happened. Units that stopped reporting at all flagged separately, because on standby power silence is the alarming state.

Warranty coverage and claim progress checked on the OEM dealer portal, so a technician quoting a repair knows who is paying for it and a claim goes in while the window is open. Parts backorders and revised ETAs pulled from the distributor, so a two-week slip reaches the customer before the promised date does.

Load bank tests, annual inspections and certification dates gathered against the units under contract, so compliance work lands in a quiet month instead of a scramble. Invoices lodged in a hospital or a municipality's own payables portal, on their cycle, rather than waiting on an email nobody opened.

Keep the acting human. Reading portals, matching serial numbers and building the morning list can run unattended. Dispatching a technician, ordering a part or billing a customer stays somebody's decision.

A generator dealer's morning list can be built overnight

Not every alarm that came in overnight is worth a van, and telling which is which starts on the manufacturer's portal, before dispatch has assigned anyone.

WebRun is an agent that works a real Chrome browser, signed in as you. It opens the monitoring portal, the OEM dealer site, the distributor's parts page or a customer's payables portal, reads what is there, and squares it against what FieldServio already knows about the unit and the contract.

It runs on a schedule you set, in your own private environment, and you can watch a run or stop it. Anything a customer receives, or that commits money, is prepared and waits for approval.

The workflows underneath are already assembled, and each names the portals it reads.