Service Reminders Done Right

Autoflow Best Practices: How to Build a Service Reminder Process That Works

Learn what separates a service reminder that gets a customer back in the bay from one that gets your number blocked.

In this video, you’ll learn the real hierarchy of service reminders, from exit scheduling to routine maintenance reminders to DVI based follow-up, and why building automated reminders on deferred work is the most common mistake shops make. You’ll also see why the Rainy Day Folder approach in Autoflow requires a human checkpoint before anything goes out, and why that step is a feature, not a flaw.

The video breaks down why deferred work alone is a weak foundation for reminders. It only captures items that made it to an estimate, it lumps unrelated jobs into one bucket, and it sends messages to customers who never agreed to hear about that item again. You’ll leave with a clear framework for building reminders your customers actually want to receive.

Good Service Reminders

  • Exit scheduling the customer’s next visit before they leave
  • Reminders built around routine maintenance, like oil changes, tire rotations, and inspections
  • Follow-up based on DVI findings your technician actually documented
  • Photos, videos, and notes included so the customer sees the evidence, not just a message
  • A conversation at drop off that sets the expectation for a future follow-up
  • A human reviewing the item before the reminder goes out to confirm it is still relevant
  • Messages that feel like a continuation of something the customer already agreed to

Bad Service Reminders:

  • Automated reminders built entirely on deferred work
  • Messages about items the customer already declined, with no opt in
  • Follow-up on findings that were never estimated, since they never made it into deferred
  • Generic messages with no photos, notes, or context
  • No conversation with the customer before the reminder goes out
  • No human checking whether the item is still relevant
  • Messages that feel like a random ping instead of a personal follow-up

Want help setting up your DVI data so it connects properly with your follow-up process? Visit our Training section or reach out to our training team for a walkthrough.