Driving Customer Trust: How a Regional Auto Group Modernized the Service Bay

The brief

A regional group of independent service centres for luxury and import vehicles came to us with a problem they couldn’t fix by hiring more staff. The mechanical work was excellent; the communication around it was falling apart as the business grew.

The workflow was entirely analog. A technician wrote findings on a paper repair order, walked it to the front counter, and handed it to a service advisor. The advisor then phoned the customer and tried to translate brake-wear measurements and suspension diagnostics into a reason to approve an $800 repair — over a noisy phone line, often catching a voicemail instead. By the time the customer called back, the lift was occupied by the next car, the technician had moved on, and the context was gone.

In our first workshops with the advisors and shop foremen, the same three frustrations came up again and again:

• Status calls swallowed the front desk. Advisors spent a large share of every day answering one question — “is my car ready?” — instead of helping the next customer or quoting new work. The phone never stopped, and every interruption pulled someone away from a job that actually moved the business forward.
• Approvals stalled in voicemail. When a tech found a worn part mid-inspection, getting a yes meant leaving a message and waiting hours, with a bay tied up the whole time. A ten-minute fix could sit half a day waiting on a callback.
• Customers couldn’t see what they were paying for. Asked to trust a recommendation they couldn’t see, many declined necessary maintenance — and quietly assumed the worst about the upsell. Good shops were being penalized for being honest, because honesty over the phone sounds the same as a sales pitch.

For a group built on a premium reputation, that last point was the real wound. The work was first-rate; the experience around it made customers feel like they were being managed, not served.

Mapping the work before writing any code

Rather than start from a feature list, we spent the opening weeks of the engagement on the floor of two locations — following a repair order from drop-off to pickup, timing how long status calls actually took, and noting every place a piece of information had to be re-typed, re-explained, or re-found. That groundwork shaped the whole build: the platform had to fit the existing rhythm of the bay, not force technicians to become data-entry clerks. If updating a car’s status took more than a tap or two, we knew the techs would route around it and the data would rot.

What we built

We replaced the paper trail with a single real-time platform spanning three roles — technician, advisor, and customer — built on React and Node.js with a PostgreSQL data layer, deployed on AWS. The engagement ran about six months from discovery to rollout across the network.

• A bay-side tablet for technicians. Techs update a vehicle’s stage with a single tap — In Bay, Inspection, Awaiting Parts, Final Wash — and, crucially, can record a short video of a problem (a torn serpentine belt, a leaking seal, worn pads) and attach it straight to the vehicle’s digital file. The interface is deliberately spare: big targets, glove-friendly, readable under shop lighting.
• A live dashboard for advisors. Every car in the shop, with its current stage and any pending approvals, on one screen — no more walking back to the bays to check progress before returning a call. Advisors can see at a glance which vehicles are waiting on a customer decision and which are ready for pickup.
• A no-app tracker for customers. On drop-off, the customer gets a secure SMS link to a mobile status page — a simple progress bar showing exactly where their car is. No download, no account, no password. It works on whatever phone they already have.
• Video approvals. When a tech flags extra work, the customer gets a text, watches the clip of their own car, and approves or declines with one tap. The decision lands back on the advisor’s dashboard instantly, and the bay can keep moving.

Under the hood, the platform ties each video, status change, and approval to the vehicle’s record, so there’s a clean, timestamped history of everything that happened on a job — useful for the advisor on the phone, and useful later if a customer ever asks why a repair was recommended.

Rolling it out without disrupting the shop

We piloted at a single location first, with a handful of technicians and one advisor, and tuned the workflow around what they actually did — shrinking the number of taps, adjusting the status labels to match the shop’s real vocabulary, and making the video capture faster. Only once it was genuinely saving that first team time did we roll it across the rest of the network, location by location, with the pilot crew helping onboard their peers. Because the tool mirrored work the technicians were already doing, adoption was quick; nobody had to be talked into a system that made their day shorter.

How it landed

Letting customers see the problem for themselves did more than streamline a workflow — it removed the argument. When someone can watch the tear in their own belt from their phone, the conversation stops being a sales pitch and starts being obvious. Advisors told us the tone of their calls changed: less convincing, more confirming.

The operational gains compounded from there. Routine status calls dropped off as customers checked the tracker themselves, freeing advisors to focus on the work that needs a human. Bays turned over faster because approvals came back in minutes instead of hours. And authorized repairs went up, not because anyone pushed harder, but because the trust was built into the experience.

A traditional, deeply paper-based trade now runs on a workflow customers actually enjoy using — and the group has a single, consistent service experience it can carry into every new location it opens.