Reminders for vehicles owned by a business account use the same machinery as private-customer reminders — event-scheduled, template-based, sent by the daily cron. What's different is who receives them, and how that routing is set up.
Per-contact, per-reminder-type opt-ins
Pistonlog routes long-lead reminders (MOT, service, timing belt, custom) via the businessContactReminderPrefs table — a per-(contact × reminder-type) opt-in flag. There's no "primary contact default":
| Contact | MOT | Service | Timing Belt | Custom |
|---|---|---|---|---|
| Fleet manager | ✓ | ✓ | — | — |
| Lead driver | — | — | ✓ | — |
| Accounts | — | — | — | ✓ |
For a given reminder template firing on a vehicle linked to this business, Pistonlog sends to every contact opted into that reminder type.
Appointment reminders / confirmations go a different way
Appointment-type reminders aren't routed via businessContactReminderPrefs. Instead they go to whichever contacts you linked to the jobcard via the jobcardBusinessContacts join — see Business contacts.
What's in the message
The reminder email or SMS uses the standard placeholders: {customer_name} resolves to the chosen contact, {business_name} to the business account name, {vehicle_reg} to the plate, {garage_name} to yours. Full list in Reminder channels and placeholders.