IntelliDealer service work orders: the shop side

What a work order is

A work order is the shop's ticket. It says: this machine, this customer, this problem, this tech, these parts, this many hours. When the job is done, the work order becomes the invoice. If the work order is sloppy, the invoice is wrong, and the customer argues.

What the vendor lists

VitalEdge lists service management as a core IntelliDealer area, tied to parts, billing, and customer history. The value is in the ties: the tech sees the machine's history, the parts come off the shelf onto the ticket, and the bill matches the work.

Questions that expose weak shop software

• Can a tech clock on and off a job from the floor?
• Do parts added to the ticket come out of stock right away?
• Can the writer see the machine's full service history?
• How are warranty jobs flagged and filed?
• Can a customer approve added work by text or email?

Worked example

A compact track loader comes in for a hydraulic leak. The writer opens a work order from the unit record, so the serial number is already right. The tech adds two hoses from stock. The ticket shows the machine had the same repair eight months ago, so the writer checks warranty before billing. One screen, no sticky notes.

The money angle

Service is where hours become dollars. Ask for a report that compares tech hours paid to tech hours billed. If the system cannot show that quickly, your shop's real profit is a mystery.

A worked task: the repeat-repair check

Suggested demo test: open a work order for a machine that had the same repair eight months ago. Inputs: a unit with service history. Expected output: the writer sees the prior repair on screen and checks warranty coverage before billing the customer. The exception to plan for: comebacks, where the same machine returns for the same problem inside your warranty window. Ask how the system flags a comeback so you do not bill the customer twice for your own redo.

Do this week

Ask your service manager for last month's comeback count. If nobody knows it, that is the first report to ask for in the demo.