Review
Start with the request and relationship evidence.
Staff can inspect the customer, vehicle, requested service, timing, notes, and matching state before changing the schedule.
Appointments
VehicleDesk keeps request intake, calendar and workboard state, customer and vehicle matching, capacity context, and internal handoffs together without representing a request as a confirmed booking.

How it works
The feature stays connected to source context and makes each staff-controlled transition visible.
Review
Staff can inspect the customer, vehicle, requested service, timing, notes, and matching state before changing the schedule.
Schedule
Calendar and board controls record the internal appointment state while warnings help staff judge timing without promising real-time bay availability.
Handoff
Tasks, opportunities, reminders, and Today work preserve ownership when the request needs follow-up or preparation.
Connected workflow
The schedule sits between customer and vehicle context, Today work, reminders, and the repair-order board that carries active service forward.
Bring unresolved appointment work into the staff plan without turning the reminder into a customer send.
Explore the connectionReview the relationship, service history, mileage, maintenance, and open work behind the request.
Explore the connectionCarry scheduled customer and vehicle context into the local repair-order workflow.
Explore the connectionLimits and trust
Public request-to-book intake and internal schedule state remain distinct; staff review is required before a booking is represented as confirmed.
Reminder and notification views do not prove that live customer delivery is enabled or that a provider accepted a message.
Practical workflow review
Preview the workflow-review agenda, current product scope, safety boundaries, and implementation questions before public requests open.