Repair status by stage
Owners see each step from diagnosis to ready for pickup, with the date the stage last changed.
A customer portal for diesel repair shops lets owners and fleet managers approve estimates, follow the repair stage and download invoices without a phone call. SIZ Group builds the portal so the operations manager can keep heavy-truck jobs moving through the bays.
A diesel job starts with a call or a truck pulled onto the lot. The service writer records the fault, runs diagnostics and may find that a failed injector has damaged a fuel rail. That discovery turns a small estimate into a larger one, and the owner must approve it before parts can be ordered.
Delays come from approval. Estimates travel by email, parts go on order before the owner signs off, and a truck can sit on the lot while a fleet manager is in a meeting. Each change then needs a phone call, and the operations manager ends up tracking paperwork by hand.
The portal gives each stage a status, puts approvals in one place and keeps diagnostic photos and invoices attached to the truck.
Because each stage has a status, the operations manager can see at a glance which trucks are waiting on the owner and which are waiting on parts.
Owners judge a shop on responsiveness and clarity. A fleet manager wants an estimate in writing, photos of the failed part and a plain explanation of the next step, without a long call to get them.
Those expectations shape the portal. Fleet customers want approval limits, documents they can file and a record they can pull for an audit. Owner-drivers want a clear total and a way to approve from the cab. The same portal has to serve both without becoming complicated.
Owners who try the portal from a phone, often in a parking lot after a breakdown, need the approval buttons to sit where a thumb can reach them.
Sign-in, estimates with line-item approval, a status that follows the shop's stages and invoices filed by truck make up the first version. Each of those features is tested against a real repair before anything goes live.
Messaging extras, parts tracking dashboards and fleet analytics wait until the basics run smoothly. A simpler release is easier to train staff on and easier to repair when something breaks.
Owners see each step from diagnosis to ready for pickup, with the date the stage last changed.
Every line item can be approved or declined, with a note for the service writer.
Documents are filed against the right truck and can be downloaded at any time.
A fleet account shows every truck on one login, each with its own service history.
Fleet managers can set spending limits so routine work moves while larger jobs need a named approver.
Each approval records the approver's name and the time, which makes disputes easier to settle.
Many diesel shops run a shop management package for repair orders and an accounting system for billing. The portal should draw job and invoice data from those records rather than asking the front office to enter everything again. The integration step is confirmed on the scoping call, so no one is surprised by a connection that needs extra work.
Where there is no system of record, the portal keeps job data itself and exports it to the bookkeeper's file on a schedule. Technicians keep working in the tools they know, and the owner's view updates as the work moves.
Portal data includes customer names, addresses, vehicle identification numbers and, where invoices are paid online, billing details. Agree with the accountant how long estimates and invoices must be kept, and set the portal to follow that rule rather than keeping everything indefinitely.
Where card payments run through the portal, the provider should meet PCI DSS and the shop should never store full card numbers. Sign-in and approval screens should meet WCAG 2.2 AA so every account holder can use them.
Keep an access log for staff logins, so the shop can show which person opened a file and when if an owner ever disputes a charge.
Staff adoption matters more than the software. Walk the service writers through each status change before launch, so updates happen as part of the normal workflow rather than as an extra task.
Invite a small group of regular owners first. Their notes on sign-in, approvals and invoice layout will point to fixes before the wider list gets an invitation.
Keep support questions in one shared document, and turn the repeated ones into a short help page inside the portal.
Yes. The owner signs in, opens the truck and sees the current stage, the last update and any documents the shop has shared. The service writer changes the stage once, and the owner's view follows it.
Each login sees only the trucks linked to its account. A fleet account sees every truck it owns, while an owner-driver sees one. Staff permissions decide which jobs each person can open.
No. It works beside the systems the shop already runs and reads job and invoice records from them where possible. The bay schedule and the books stay where they are.
Yes. Limits can be set by truck, cost band or type of repair, so routine work moves quickly while safety-critical jobs need a named approver.
The build sits between $300 and $2,200 depending on how many account types, systems and approval levels the portal needs. We settle those on the first call and confirm the total in writing.
Walk us through your account types and approval rules, and we will send a scope with a price for your review.