Fleets
Delivery firms, contractors, municipal fleets: many vehicles, one payer, and priorities unlike a retail customer's.
Fleets and mobility
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
The task it takes over
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 an estimate and recording an approval: you do not buy an estimates add-on again for those same vehicles. What stays separate is collecting money — approving work triggers no payment.
Step by step
- Frame
A contract ahead of a vehicle
Company, covered vehicles, authorized people, spending ceilings, priorities and territories: a frame written once governs every order afterwards.
- Intake
A driver describes, a company decides
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.
- Group
Due dates landing together
Services due, manufacturer recalls, a season changeover: work falling due together is planned together, per depot, so fewer vehicles sit idle.
- Hand back
Return to service is an event
A vehicle back in service is announced to a company and a driver, with work done and what remains owed under a contract.
An add-on, not a base capability
An Automotive base serves one shop and 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. It grants no payment — approving work stays approving work — and payment requests belong to a different module.
What this changes for your business
Repair shops
A neighbourhood shop serving three local firms already runs fleets unnamed: a written frame replaces verbal understandings.
Mobile mechanics
Service travels to a customer's depot. Territory, travel and capacity for a day decide what can honestly be promised.
What it receives
- A company contract, its vehicles and its authorized people
- Spending ceilings and agreed priorities
- Service due dates, per vehicle and per depot
- A shop's written estimate for a given job
What it produces
- An order assigned and accepted by a technician or a crew
- Approval obtained from a right person, with its date and time
- Work grouped by depot or by territory
- A return to service announced, with what remains owed under a contract
You write a contract, its ceilings and its priorities. Zenvox diagnoses nothing over a phone, sets no repair price, and declares no vehicle ready unless a shop said so.
What is metered, and what comes from elsewhere
Two allowances travel together: vehicles under management and tracked orders, plus a volume of document pages.
- Vehicles under management, counted while active on a contract
- Repair orders tracked per month, reset at each period
- Supporting document pages filed against those orders
- Inbound calls stay metered on a base, separately
Onboard telematics, fuel cards and a company's own fleet management systems stay theirs, billed by their providers.
With your shop software
A status below comes from qualification research. With no qualified software, a fleet contract lives in Zenvox.
- ShopmonkeyTo qualifyPublic documentation exists; write operations, commercial plan and advanced shop constraints untested.Shopmonkey
- Provider portals and operations softwareTo qualifyA generic category: a public portal is insufficient, a named product plus established rights are required.My software is not in the list
Questions about this add-on
Can the driver authorize the spending?
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.
Do I need the estimates and approvals add-on on top for a fleet?
No. This add-on includes circulating the estimate and recording the approval for covered vehicles: they are not billed twice.
Is approving work the same as paying?
No. Approving work stays approving work, and payment requests belong to a different module.
How do fewer vehicles end up sitting idle?
By grouping due dates. Services due, manufacturer recalls, a season changeover: work falling due together is planned together, per depot or per territory.
What is metered when I turn fleet coordination on?
Two allowances travel together: vehicles under management, counted while active on a contract, and repair orders tracked per month, plus a volume of document pages. Inbound calls stay metered on the base, separately.
Where to next
Go back to your shop, or read a neighbouring add-on.
Fleets and mobility