AI inspections for Fullbay

Overview

A Fullbay service order is a complete record of what the shop did to a unit; the photos on it are the only record of what the unit actually looked like, and almost nobody opens them. The service order carries the unit, the complaint, the diagnosis, the parts, the labor hours, the tech notes and the pictures the tech took while working, and Fullbay shows those pictures to the customer in the Customer Portal. What it does not do is read them. RapidEye connects the two halves: it reads your unit list and service order dates from Fullbay along with the photos your techs take, and returns one finding per problem, hung on the right unit, with the frames that prove it.

How it works with Fullbay

Fullbay hangs everything off two objects, the unit and the service order it is on, and the photos a tech takes land on the service order. So the checks follow the same shape the shop already works in.

• The walk-around before the wrench turns. The unit rolls in for one complaint and arrives with five. RapidEye reads the arrival photos against the last photos of the same unit and reports what is different: a cracked marker light, a mudflap gone, a fresh dent in the quarter fender, a fluid trail under the drive axle that was not there in June. On a customer's truck that is a documented starting condition; on your own fleet it is a defect nobody had to notice.
• Diagnosis, where the tech is already photographing. Fullbay's workflow has the tech diagnose the complaint and note anything else the unit needs. Photos taken at that step are the ones RapidEye reads hardest, because they show the parts of the truck a tech was looking at anyway and the parts they were not.
• The repair itself. Fullbay says notes, statuses and pictures collected during the process are kept together on the service order. RapidEye reads the finished-work frames against the note: torque marks, a hose routed clear of the exhaust, a fitting seated, the panel back on with all its fasteners. Where the photo does not show what the note says was done, that comes back as a finding rather than a comeback.
• Pending repairs, the ones the customer declined. Fullbay keeps a running list of repairs a customer put off, and surfaces them when the unit comes back. RapidEye reads whether the deferred item got worse between visits, so the follow-up conversation is a photo from July next to a photo from September instead of a note that says the customer said no.
• Inbound DVIR defects. When a reported defect arrives from a connected inspection platform, Fullbay brings the unit, the issue and the supporting photos in with it. RapidEye reads that inbound set too, which means the driver's report and the shop's own photos of the same unit sit on the same finding.
• PM and inspection jobs. Fullbay triggers preventive maintenance by mileage, engine hours or the applicable meter, and canned jobs make a PM the same set of steps every time. Photos from a PM are the cheapest kind of surveillance a fleet has, and RapidEye reads them against the previous PM on the same unit rather than against a checklist.

Every finding names the unit, where on the unit, what kind of problem it is (damage, defect, safety, or work that does not match the note), how bad it looks, the frames that show it, and a suggested next step. It turns up in the RapidEye dashboard, or in Slack or the service manager's inbox. What happens next in Fullbay is yours: a new service request, a line on the estimate, a note for the customer. Photos are the first input most shops use, not the last. Shops that film a walk-around instead of shooting stills, or that want findings scored against their own inspection form or their fleet's own out-of-service standard, get that set up with us on the first call.

How to connect Fullbay to RapidEye

1. The units you service, on their own unit records. Fullbay keeps each unit's service orders, usage readings and completed work tied to the same asset, and that is what a finding attaches to. Any unit can be excluded from reading.
2. Photos on the job. If your techs already attach pictures to the service order while they work, RapidEye reads those and nothing changes. If they do not, RapidEye supplies a capture link that opens in any phone browser with nothing to install: a fixed set of angles per unit, shot on arrival and again at completion.
3. Add RapidEye as a user in Fullbay. Fullbay's software settings let an owner or admin add an employee and tick the parts of the software that user can view. Add Rapid Eye with view access to service orders and unit history; the modal has the details.

That is the whole setup. Techs keep the same service order and the same phone, and the first findings follow the first jobs that close.

How a Fullbay service order moves, from request to invoice

Checked against Fullbay's product documentation, September 2026.

According to Fullbay's own product documentation (fullbay.com), the workflow is a fixed sequence of six to eight steps depending on whether the parts are already in the shop, and the point of the sequence is that you cannot move on until the step you are on is signed off. Requests arrive through the Customer Portal, phone, email or text, or as a defect from a connected inspection platform, and from there the job runs the ladder below. It is worth reading as a photo ladder as much as a repair one, because two of these steps are the only moments anyone points a camera at the truck.

1. 1AssignService order opened

   The complaint is written up and the job goes to a technician. Fullbay shows the service manager who is on what and who has capacity.

2. 2DiagnoseThe camera comes out

   The tech works out the cause and notes anything else the unit needs, including preventive maintenance that is due. Fullbay's own framing is that the workflow exists so a repair need is never missed.RapidEyeReads the diagnosis photos against the last photos of the same unit and reports what changed.

3. 3Quote partsPriced in the order

   Parts in inventory get priced automatically; anything else is handed to the parts manager without the tech chasing them.

4. 4AuthorizeThe customer decides

   The estimate goes out by phone, email or a text link to the Customer Portal, where the customer sees the notes and images from the repair. Anything declined here becomes a pending repair.RapidEyeThe photo behind a declined item is kept, so the next visit can show whether it got worse.

5. 5Order and receiveParts in hand

   Parts are ordered if they are not in stock, then marked received. The job cannot advance until they are.

6. 6RepairThe camera comes out again

   The tech clocks into the job, works it with labor guides and procedures inside the order, and adds notes and photos from the shop floor.RapidEyeReads the completion photos against the note, and flags work the frames do not show.

7. 7InvoiceClosed on the unit

   The invoice goes out and the whole job, parts, labor and usage reading, stays attached to the unit's history for the next tech and the next audit.

Workflow steps as documented by Fullbay; the indented lines are where RapidEye reads. Shops that do not need every step can customise the sequence.

Where the photos actually live

On the service order, and in the Customer Portal. Fullbay's service order documentation says status, notes and pictures collected during the process are kept in one place, and its customer communication documentation says customers can track repair progress and see images and notes provided by technicians. Its DVIR documentation says supporting notes and photos stay attached to a reported issue as it flows into the repair workflow, so an inbound defect arrives with its own frames. Fullbay describes where those images go and who can see them. It does not describe anybody reading them, which is the honest state of every shop system we have looked at: the picture is captured for the customer conversation, not for a quality check.

Can Fullbay tell you the repair was done right?

It can tell you it was done, thoroughly. The service hub gives a service manager a real view of the shop, and that view is built out of statuses, hours and dollars rather than condition.

Every one of those is a record of activity. A job marked complete says a tech signed off on the step, the way a checklist item says somebody ticked it; Fullbay is explicit that the value of the workflow is that nothing gets skipped, which is a claim about sequence, not about the quality of the weld. The one artifact on a service order that can settle the quality question is the photograph, and it is the one artifact the system was never built to look at. That is the gap this integration fills, and it is a gap in the shop's day rather than in the software: nobody has an hour to open sixty jobs' worth of pictures. RapidEye does.

Fullbay integration FAQ