Fleets
Delivery firms, contractors, municipal fleets: many vehicles, one payer, and priorities unlike a retail customer's.
A vehicle fleet belongs to a company rather than a driver: approvals, due dates and returns to service follow a contract.
7 days, 20 answered calls, no card
A fleet behaves nothing like retail customers. A driver brings a vehicle in, yet a driver does not authorize spending; a manager authorizes, yet a manager heard no noise and saw no warning light. Between them, a shop burns days hunting for whoever decides.
This add-on organizes fleet maintenance as what it is: a contract. Vehicles belong to a company, decision authority is named, spending ceilings are written up front, and service due dates group by depot or by territory.
It includes circulating the estimate and recording the approval: you do not add Estimates and approvals for those same vehicles. What stays separate is collecting money — approving work triggers no payment.
Company, covered vehicles, authorized people, spending ceilings, priorities and territories: a frame written once governs every order afterwards.
A driver's call attaches to a correct vehicle and contract. An approval request goes to a named authority rather than whoever holds a steering wheel.
Services due, manufacturer recalls, a season changeover: work falling due together is planned together, per depot, so fewer vehicles sit idle.
A vehicle back in service is announced to a company and a driver, with work done and what remains owed under a contract.
The Garages & auto repair base serves one shop and its retail customers: identify, book, inform, answer on known status. Fleet contracts, authority per company, work assignment and grouping get added here.
This add-on includes Estimates and approvals for covered vehicles: they are not billed twice. Approving work stays approving work: payment requests run through the Deposits and payments add-on.
Delivery firms, contractors, municipal fleets: many vehicles, one payer, and priorities unlike a retail customer's.
A neighbourhood shop serving three local firms already runs fleets unnamed: a written frame replaces verbal understandings.
Service travels to a customer's depot. Territory, travel and capacity for a day decide what can honestly be promised.
You write a contract, its ceilings and its priorities. Zenvox diagnoses nothing over the phone, sets no repair price, and declares no vehicle ready unless a shop said so.
This add-on is included in the free trial, like every add-on. After that, you add it to your Garages & auto repair base whenever it is useful.
Onboard telematics, fuel cards and a company's own fleet management systems stay theirs.
With no connected software, the fleet contract lives in Zenvox. With your shop software, the connection works under the authorization you give from your account.
Not by default. A driver's call attaches to the right vehicle and contract, and the approval request goes to the authority named on that contract rather than to whoever holds the steering wheel.
No. This add-on includes circulating the estimate and recording the approval for covered vehicles: they are not billed twice.
No. Approving work stays approving work, and payment requests run through the Deposits and payments add-on.
By grouping due dates. Services due, manufacturer recalls, a season changeover: work falling due together is planned together, per depot or per territory.
Yes, like every add-on. After that, the add-on carries its own monthly volume of vehicles under management, tracked repair orders and document pages, which you follow in your app; calls and service texts stay included in your base, and you add volume whenever you want.
Go back to your shop, or read a neighbouring add-on.
Fleets and mobility