The follow-up should begin from a real workshop event
A useful reminder workflow starts from an approved event such as a completed job, a confirmed service date or another workshop-defined milestone. It should not guess that work was completed because a conversation became quiet.
Three separate workflows are often better than one
- Job-completion update: tell the customer when an approved status says the vehicle is ready or the job is complete
- Review request: send an approved feedback or Google review link after the service event and any chosen delay
- Future service reminder: use an approved date or interval from the customer/vehicle record rather than an AI guess
What to control before switching reminders on
- Which customer records are eligible
- Which event starts each reminder
- How long to wait
- Which communication channel and template are approved
- How opt-outs and communication preferences are respected
- How duplicate reminders are prevented
- Which replies should create a staff task
Planning examples at different customer volumes
A workshop with 100 eligible follow-ups per month may only need a small queue and a few approved templates. At 500, suppression rules and reporting become more important. At 1,000, segmenting by service type, outlet or customer status may help keep communication relevant.
Important note about the examples
Workflow examples, enquiry volumes and document-volume calculations in this article are illustrative and are provided to explain possible automation designs. Actual integrations, processing time, extraction accuracy and operational outcomes depend on source quality, business rules, connected systems, APIs, account access and human-review requirements. Performance figures are only presented as tested results where specifically identified.