Workflow guide
How deferred-service follow-up works
A practical guide to deferred-service pipeline stages, customer and vehicle context, staff preparation, local outcomes, and source-system boundaries.
- Subject owner
- VehicleDesk Product
- Last reviewed
- 2026-07-11
Start from actionable service context
A deferred-service workflow is useful only when staff can understand the recommendation, customer, vehicle, timing, value context, and current state. VehicleDesk keeps those records together instead of reducing the work to a generic reminder.
Use visible stages
Call Today, Waiting, Scheduled, and Completed describe local follow-up state. Movement between them is an explicit staff action and does not imply that the source repair record changed.
- Call Today: ready for staff review
- Waiting: customer or staff follow-up remains
- Scheduled: service has a recorded next appointment or local scheduled state
- Completed or archived: no longer active in the working queue
Prepare, then record
The detail workspace may include notes, reminders, tasks, history, and an AI-assisted call-guide draft. A person reviews the context and records the outcome; generated guidance does not establish contact permission or send a message.
Keep the system boundary clear
Shopmonkey remains authoritative for source repair history. VehicleDesk stores the local workflow state and evidence needed to operate the follow-up process.
Related product detail