Operations guide
Turn appointment requests into confirmed bookings
A practical guide to appointment requests, scheduling, customer and vehicle matching, capacity context, reminders, and handoffs.
- Written by
- VehicleDesk Product
- Content updated
- September 17, 2026
Track the request and the booking as separate states
VehicleDesk organizes request-to-book intake. The team reviews the customer, vehicle, service request, timing, and capacity, then confirms the booking. The appointment record is VehicleDesk work built on the imported relationship record.
Keep the customer and vehicle attached
Matching and creation flows keep the relationship record beside the schedule, so the advisor sees prior work, open recommendations, and the reason for the visit.
Coordinate the handoff
Appointment work creates or connects tasks and opportunities. Reminders and notifications queue on the plan and go out consent-checked.
Use explicit schedule state
Calendar and workboard controls record the team's decision. Capacity warnings show how full the day already is.
Worked example: from request to confirmed booking
A request arrives with the customer, vehicle, requested service, and preferred timing.
The team confirms the customer and vehicle match existing records, checks shop capacity, and accepts the request.
The booking appears on the schedule, and a reminder queues to go out consent-checked before the visit.
Checklist: request-to-booking
Confirm these before the appointment is promised.
- Customer and vehicle are matched to existing records, not duplicated
- Capacity for that day is checked before confirming
- The reason for the visit is written on the appointment
- Reminders are consent-checked before they send
Common questions
Are appointment requests the same as booked appointments?
No. A request is intake. The team reviews and confirms it, and the confirmed booking becomes its own schedule record linked to the customer and vehicle.
Where does the appointment data live?
The appointment record is VehicleDesk work built on the imported relationship record. It links to the customer and vehicle that came from Shopmonkey.
More guides
Other operations guides
- Plan an advisor follow-up day from the timeline: A repeatable process for reading scheduled follow-ups, triaging the unscheduled tray, placing work on open time, and recording the next action.
- Check CRM data quality before you trust a report: A practical checklist for import freshness, customer contactability, vehicle completeness, record linkage, errors, and decision confidence.
- Keep parts and vendor costs accountable: Enter every vendor invoice, link parts to the repair order, and keep returns, cores, credits, and aged open costs visible until they close.
- Resolve data-quality findings that change the day: Work from import confidence and provenance into contact, duplicate, linkage, and merge findings, and apply the inspected correction.