Autoflow
Autoflow integrationAuto service and vehicle rentalShop CRM and inspection platform

AI inspections for Autoflow

RapidEye reads the photos and videos your technicians attach to each Autoflow DVI and QC sheet, and returns a finding for what the sheet did not say.

How the three Autoflow worksheets fit together

Overview

An Autoflow DVI is a record of what a technician chose to report, and a very good one; it is not a record of what the camera saw. A finished sheet carries a status per line, notes, markups and video, and it goes out to the customer as a branded Report Overview. What no sheet carries is a second pair of eyes on the pictures themselves, especially on the lines nobody set a status on. RapidEye reads every photo and video attached to a DVI or a QC sheet, along with the vehicle, the visit and the date, and returns a finding for each thing the images show: a fresh scuff on a rocker panel, a fluid trail under the pan, a wheel that is not the wheel that was on this car in March. Autoflow keeps the ticket. RapidEye tells you what is in the pictures on it.

Every DVI, not the ones you spot-checkEach inspection your shop finishes gets its photos read, whether that is nine cars today or ninety across four stores.
This visit against the last oneAutoflow's vehicle profile repopulates each time the car comes in. RapidEye compares the two photo sets and names what changed.
Autoflow stays the recordNo sheet, note, markup, status or ticket is changed. RapidEye reads and reports; your people decide what happens next.

How it works with Autoflow

Autoflow gives a vehicle three worksheets in one visit, and photos land on all three. The checks follow that shape rather than inventing a new one, so nobody in the shop has to learn a second process.

  • The vehicle profile. Autoflow encourages a set of profile photos and suggests all four corners, the VIN sticker and the tire placard, and that record populates with each visit. RapidEye treats it as the baseline for the car: a dent on the passenger door that is in today's corner shot and not in February's comes back as a finding, with both photos and the two visit dates.
  • Inspection lines with a status. A red line means urgent, a yellow line means it can wait, and the picture is the evidence the advisor sells from. RapidEye reads that picture and says whether it supports the line: a brake photo where the pad is not in frame, a leak photo where the leak is off the edge, a caption that says one thing and shows another.
  • Inspection lines with no status. A line left blank never appears in the customer report at all, which is correct behaviour for something not inspected. It also means a rushed sheet and a thorough sheet look the same downstream. RapidEye reads whatever photos are on that sheet regardless, and a finding on a component nobody graded is often the most useful thing that comes back.
  • The concern lines. A customer's stated concern can carry its own images. RapidEye reads them next to the rest of the sheet, so "pulls to the right" and a photo of the inside edge of one front tire end up in the same finding.
  • The QC sheet before delivery. Autoflow's QC step exists to catch what the repair itself left behind. RapidEye reads the QC photos against the intake photos from the same visit: a scuffed wheel that was clean at intake, a trim clip left out, a shop rag still under the hood.
  • Videos and other formats. Autoflow supports video on the DVI, and RapidEye reads video the same way it reads stills. If your shop documents in a way that is not on this list, a walkaround clip at drop-off, a 3D scan of a body panel, an inspection format you built yourself, that is a setup conversation and not a limit.

Every finding names the vehicle and the visit, the spot on the car, the type of problem, how serious it is, the earlier photo next to the current one, and a suggested next step. It lands in the RapidEye dashboard and, if you want it there, a Slack channel or an inbox the service desk already watches. Nothing moves in Autoflow unless a person moves it.

How to connect Autoflow to RapidEye

  1. An Autoflow account with the sheets your shop actually runs. Your administrator may have renamed green, yellow and red to your own words and built your own DVI notes and recommendations; RapidEye reports against your names, not the defaults.
  2. The photos you already take. Autoflow photos go from the camera button straight to the sheet in the cloud, or up from the device gallery when the tech was out of wifi range in the lot. RapidEye reads that set. If a lane in your shop does not run a DVI at all, a RapidEye capture link opens on any phone with no app to install, with a fixed set of angles.
  3. A user for us. Add Rapid Eye as a service advisor from the Admin menu; the modal has the two fields. Technicians keep working the same sheet on the same tablet and never see us.

The three worksheets on an Autoflow visit

Checked against Autoflow's help centre, September 2026.

Autoflow is a shop CRM and workflow platform that sits alongside your shop management system rather than replacing it, and a vehicle in the shop today has three worksheets open on it. According to Autoflow's help centre documentation (autoflow.com), the vehicle detail header is unified across all three, so data entered on one updates the others, and any of them can be opened from the workflow without changing the vehicle's status.

Shared vehicle headerYear, make, model, VIN, plate, mileage. Fill a gap on any sheet and it updates the others.
DVIthe technician's finding
  • Vehicle profile, filled once and repopulated each visit
  • Reason vehicle is here: concern, service, info
  • Tire sizes and tread depth, carried forward
  • A status, notes and recommendations per line
  • Photos with markups, and video
Work orderwhat was authorised
  • Parts and labour, generated from your shop management system or from the approved DVI items
  • Packages you add by hand, with estimated time
  • A DVI sheet attached back onto it as a line
  • Sign-off by the tech who did the work
QC sheetthe last look before delivery
  • An automatic flag that the DVI and work order are signed off
  • Line items your admin can require before submit
  • Red items marked addressed but left red
  • Submit is internal; sharing is optional
  • Images and video with captions and markup
The blue dots are where photos live. All three sets sit under the same vehicle in the visit history, which is what makes them comparable.

Autoflow's own QC guidance is unusually honest about why the step exists: it tells the person running it to be honest, says it is good to catch things, and tells them to leave an item marked red even after it has been addressed, so the record of what was wrong survives the fix. Submitting a QC sheet is internal only, and Autoflow notes most shops keep QC to themselves rather than sharing it with the customer. That makes the QC photo set the most candid image library in the building and the one nobody has time to re-read.

What a status on a DVI line means, and what a blank one means

A technician taps one of three states per line. Autoflow's defaults are below; an administrator can rename them to whatever your shop calls them, and the tire inspection shows the same three as a check mark, an exclamation mark and an X.

Green good items Yellow requires future attention Red requires urgent attention Blank not inspected, or not applicable

The fourth chip is the interesting one. Autoflow's documentation is explicit that a line left blank does not appear in the client report, which is the right call: a customer should not read a grade nobody gave. The consequence inside the shop is that a blank line and a good line are indistinguishable once the sheet is sent, and the only place the difference survives is the photographs. Autoflow also repopulates previous notes on a line when an item flagged for future or urgent attention was not marked authorised last time, so the sheet already carries some memory across visits. Photos are the part of that memory nobody re-reads.

Do the photos on an Autoflow DVI get looked at twice?

Once, by design, and Autoflow is clear about the path. A photo taken from the camera button is not stored on the device; it uploads directly to the sheet in the cloud, and Autoflow notes the advisor can watch the DVI fill in as the technician works. Once the technician signs off, the DVI button turns orange, the advisor's send buttons unlock, and the sheet goes out by text or email to a Report Overview the customer opens with no password; the buttons turn green so nobody wonders whether it went. Autoflow keeps all of it: inspections, work orders and QC sheets are catalogued by visit date under the vehicle in the client profile, and an advisor can resend a DVI from there. So the archive is complete and the review is a single human pass at the moment the sheet is finished. RapidEye is the second pass, on all of it, including the visits that closed months ago.

Autoflow integration FAQ

Does RapidEye integrate with Autoflow?

Yes. RapidEye reads the photos and videos your technicians attach to each Autoflow DVI and QC sheet, along with the vehicle, the visit and the date, and returns a finding for each thing the photos show: a fresh dent, a fluid trail, a wheel that changed between visits, a red item that still looks red. Your DVI sheets, notes, markups, statuses and Report Overview in Autoflow are not changed.

Where do the photos come from?

From where your technicians already take them. Autoflow's help centre describes photos taken with the camera button on a tablet or phone that upload straight to the DVI sheet in the cloud, and photos uploaded from a device gallery when the tech was out of wifi range. RapidEye reads that set. If a lane in your shop does not run a DVI at all, a RapidEye capture link opens on any phone with no app to install and supplies the same set of angles.

Can RapidEye check a DVI that a technician already signed off?

Yes, and that is the point. Sign-off in Autoflow is a person saying the inspection is finished; the DVI button turns orange and the advisor can send it. RapidEye reads the photos on that sheet and says what is in them, including things nobody gave a status to. Items left blank never reach the customer report, so a blank line and a clean line look identical to everyone downstream except the camera.

Will RapidEye edit anything in Autoflow?

No. Autoflow stays the system of record for the sheet, the note, the markup, the status and the ticket. RapidEye reads and reports. If a finding means an item should move from green to red, a person makes that change in Autoflow.

Does this help with a customer who says the shop damaged their car?

It gives you the comparison you already half have. Autoflow's own advice is to photograph all four corners of the vehicle, the VIN sticker and the tire placard in the vehicle profile, and that record populates on each visit. RapidEye lines up the intake photos against the delivery photos from the same visit and against the same vehicle's last visit, and points at what is different, so the conversation is about two pictures instead of two memories.

Does it work for a three-bay shop, or only a multi-shop group?

Both. A three-bay shop has nobody spare to re-open finished sheets, so RapidEye is the second look. A group running Autoflow MSO with shared sheets across locations gets the same reading applied identically at every store, which is the only way to tell whether one location's inspections are thinner than the rest.

Other shop software RapidEye reads photos from

Platforms where a technician's inspection photos land on a ticket, the same way they land on an Autoflow DVI.

Sources

  • Autoflow help centre, service advisor and administrator training documentationautoflow.com
  • Autoflow product pages, digital vehicle inspection and quality controlautoflow.com
  • Tekmetric product pages, digital vehicle inspectionstekmetric.com
  • Shopmonkey product pages, digital vehicle inspectionshopmonkey.io
  • AutoVitals product pages, digital vehicle inspectionsautovitals.com
  • Shop-Ware product pages, features overviewshop-ware.com
  • Protractor product pages, features overviewprotractorsoftware.com

Sources are named at the publisher level and were checked against the publisher's live pages before this page was published.