Voyager provides global mobility services: fleet management and leasing for businesses worldwide, plus vehicles for rideshare drivers and local paratransit operators. Collision repair is a permanent cost line in that model, and it was the line Voyager had the least oversight of.

Their repair process was fragmented, which stretched cycle times and raised costs. Approvals, vehicle history, and charges all lived in different places, and no one place showed the whole picture.

What fragmentation actually looks like

A scattered repair process fails in the same few spots, and they are all mundane.

• An estimate sits in one person's email for two days while the vehicle sits in a shop lot.
• Nobody can answer whether this VIN (vehicle identification number) has been in for this same repair before without making three calls.
• Each shop invoices separately, so reconciliation happens at month end, long after anyone could have questioned a line.
• A charge that should never have been there gets paid, because catching it would have required comparing it to work nobody can easily look up.

Voyager needed one place to hold ROs (repair orders), visibility across the vendor network, and an approval path that did not depend on who happened to be at their desk.

What changed in the workflow

One queue instead of many inboxes

All collision repairs moved onto a single platform. Voyager's team tracks the status of every repair in one view, consolidates approvals there, and pulls detailed vehicle history on demand rather than reconstructing it. Recurring issues on a vehicle become visible as a pattern instead of arriving as a surprise on the third repair.

Their own shops, ranked by their own data

Voyager kept their trusted vendor network and gained insight into it. Shops are selected on performance, past repair quality, and the overall relationship, so work goes to the shop most likely to finish it right the first time. The network is not a static directory; it adjusts as performance data comes in.

Approvals that move in hours, not days

Communication with shops and the approval step were the biggest single source of delay, and both now sit in the same hub as the RO. That matters more than it sounds. Approval delay is pure calendar time with no work happening on the vehicle, which makes it the cheapest delay in the whole process to remove.

One invoice instead of a stack

Billing is consolidated, so Voyager stopped tracking separate invoices from separate shops by hand. Finance reconciles one document, and the review happens close enough to the repair that questions still have answers.

The results

Repairs move through the cycle faster because approvals stopped being the bottleneck, and vehicles return to service sooner as a result. Billing collapsed from many invoices into one, which cut administrative work for the fleet team. Vehicle history is available by VIN, so recurring problems get caught rather than quietly paid for twice. And the transparency across the repair network sharply reduced the room for charges that should not be there.

Bennett Harris, Voyager's Director of National Fleet Operations, put it this way.

"Before ServiceUp, managing our collision repairs was a lengthy and complex process... We've seen faster repairs, reduced costs, and have peace of mind knowing everything is being managed effectively."

How to check your own operation

Four questions will tell you whether you have Voyager's old problem.

• How many hours pass between an estimate arriving and someone approving it? Measure it on last month's repairs, not from memory.
• Can you pull every repair on a given VIN in under a minute?
• How many separate invoices did your team reconcile last month for repair work?
• Who reviews estimate lines against your pricing and warranty policy, and what happens to that review when they take a week off?

About ServiceUp

ServiceUp is the agentic repair platform for modern fleets. You bring the system of record, we bring the system of repair: intake, shop routing, estimate review, approval, and payment to the shop, handled by agents that work inside the systems you already run. See what that covers for fleets.