How deferred-service follow-up works

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

Open, Needs Follow-Up, Contacted, and Scheduled describe the active local recovery state. Movement between them is an explicit staff action and does not imply that the source repair record changed.

• Open: imported recommendation is ready for review
• Needs Follow-Up: staff outreach is the next deliberate step
• Contacted: a conversation is open or awaiting its next outcome
• Scheduled: the recommendation has recorded scheduled-work context
• Completed or archived: retained outside the active recovery board

Prepare, then record

The detail workspace may include notes, reminders, tasks, history, and assistive call guidance. A person reviews the context and records the outcome; generated guidance does not establish contact permission or send a message.

Connect the next operational step

Scheduled recovery work can move into the appointment and advisor-day context. If the customer is not ready, a task or reminder preserves the responsible next step without pretending the work is booked.

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.