Instead of hard-wired reminders you write your own rules: one trigger, one action, done. Whoever wrote it can see beforehand what it would do today — and afterwards what it did.
Automations are not a scripting editor and not a second product, but a short rule: pick a trigger, pick an action, name the recipients. Three trigger kinds cover what actually happens in a fleet — a deadline coming up, an event on a vehicle, a fixed schedule. The module is not licence-gated; the right to manage automations is enough.
Roadworthiness test, UVV inspection, safety inspection, tachograph, fire extinguisher, maintenance due date, seasonal tyre change, lease end, notice period on vehicle and device contracts, vehicle tax, insurance policy end, licence expiry, due licence check and due driver instruction. The rule fires a chosen number of days before or after.
When a vehicle is created as planned, put into service or retired, an action can hang off that — the procurement note, the handover checklist, the de-registration.
Some things have no due date, only a rhythm: 'ask for odometer readings every 30 days'. Intervals from one to 365 days are free to choose.
Send an email, send drivers an odometer reminder, raise an in-app notification, create a task in the vehicle file, or call a webhook. Only actions compatible with the chosen trigger are offered.
Free addresses, the contacts of a CRM partner, or all fleet managers at once — plus an optional CC recipient on the same message rather than a second send.
Deadline rules answer, on demand, who they would write to today — with a count and samples. Only then do you arm them.
Every run is recorded with its time and outcome: succeeded, failed, or skipped because there was nothing to do.
The more important question is who an automatic message did not reach. A dedicated report names the case and the reason for the last 30 days — a driver without an email address, for instance.
No. Automations are part of the platform and included in every edition. They hang off a permission, not a licence flag: whoever may manage automations sees the area, everyone else does not.
For deadline rules, yes. The preview computes who the rule would write to in the current state and shows a count and samples — without sending. Schedule rules can additionally be triggered once by hand if you want to see a real run.
The case is skipped and the skip is recorded. That is what the skip report is for: it answers who the automation did not reach in the last 30 days and why — instead of leaving the impression that everyone was informed.
Yes, through the webhook action: the rule calls a URL you configure when it fires. That connects a ticket system, an intranet or your own interface without us having to build anything for it.
Every system email in your wording and your design — with placeholders, live preview and an auditable send queue.
Maintenance templates, plans by time or mileage, service history and reminders.
Leases, rentals and purchases with mileage terms, expiry monitoring, a return cockpit and vehicle tax.
Licence data, recurring visual checks, UVV driver safety instructions and a booking block when the required class is missing.
30 minutes, no sales pressure: we show the module in the context of your fleet — self-hosted in your data centre, GDPR-compliant, made in Germany.