These interactive scenarios use synthetic sample records—not customer records, a live repair or native-app release evidence. No live records are created or modified and no provider calls are made.
Voice intake produces a structured draft for a person to review before confirming. AI suggestions are not an authoritative diagnosis: a qualified person must review repair and safety decisions. Fleet AI is optional; voice recordings use shop credits.
Verizon Connect Reveal periodically syncs mapped vehicles and supported diagnostic codes, subject to account, plan, hardware and API access. Last-known location is not live GPS tracking. Rand McNally is planned, subject to approved access and validation.
Guided Interactive Preview
Follow one repair workflow from the driver's first report to the fleet dashboard using pre-loaded sample data. This is a guided interactive product preview—it creates no live records and makes no provider calls.
More High-Impact Workflows
A driver's spoken report can become a reviewable Work Order draft with the asset, issue, and confirmed context kept together.
Supported Reveal fault-code events can open a Work Order and alert the team, connecting telematics signals to maintenance follow-through.
When an asset is already down for repair, its upcoming preventive maintenance remains visible alongside its service history and compliance picture.
Guided product preview with pre-loaded sample data. No live records are created or modified, and no provider calls are made.
Guided interactive preview
Follow one repair workflow from the driver's first report to the fleet dashboard using pre-loaded sample data. The interactive demo remains on the product-tour page; this overview keeps all five stages in view.
A roadside safety issue is logged via voice transcript and DVIR. A spoken report supplies context; reviewed voice intake is not automatic approval of a repair.
The failed DVIR becomes maintenance work with the reported defect and useful source context. Voice-generated drafts require a person to review before confirmation.
The shop manager reviews priority, relevant asset history, and the recorded activity trail before assigning a technician.
The technician records parts, labor, cause, and correction from the bay. The sample repair illustrates documentation, not verified automatic stock consumption.
Recorded repair activity feeds downtime, costs, PM completion metrics, and asset history. Sample outcomes are illustrative, not measured customer results.
Follow a failed driver inspection through work-order creation, manager assignment, technician documentation, and the updated fleet record.
Try the defect-to-repair scenarioTurn a synthetic spoken defect report into a structured draft. Review the issue and source before confirming the work and its responsibility in the queue.
Try the reviewed voice scenarioReview a supported diagnostic-code event, triage its linked work order, and follow the event in asset history. The sample makes no provider calls and does not demonstrate live GPS.
Try the Verizon alert scenarioSpot upcoming preventive maintenance while an asset is already in the bay for a repair. Coordinate service during the current shop window rather than assume a guaranteed savings outcome.
Try the PM opportunity scenarioGuided product previews use synthetic sample data. No live records are created or modified, and no provider calls are made. They are not customer records, evidence of a completed live repair, native-app release evidence, or a verification of stock and receiving workflows.
Real web screens
The inspection finding, the work order and the parts behind it, as they appear in the web interface.
Screenshots show the real DZ Fleet Suite web interface populated with fictional demo data. They are not customer records or results, and not a native app.