← All features

Feature

Automation EngineComing soon

You write a rule that says what should happen when something changes, and the system carries it out. The aim is the small admin that currently depends on someone remembering.

What it does

Send reminders and updates without anyone having to remember.

Act the moment a vehicle reaches a place, not when somebody notices.

Chase an expiry date before it expires.

Give the team their time back for the work itself.

A scenario to try

A van enters a customer's gate and an insurance date is thirty days off

A demo can run both rules for you. A geofence around the customer's site fires a rule you wrote, and the arrival message goes out with no one at a desk noticing the van.

Across the office, an insurance renewal is thirty days away, so the reminder goes to the person who owns it. Neither task would be missed on a good week. The point is the bad week.

How it works

  1. You set rules in the form: when this happens, do that.
  2. Geofence triggers fire actions when a vehicle enters or leaves a place.
  3. Expiry reminders send themselves ahead of the date.
  4. Status changes can trigger notifications and follow-on actions with nobody in the loop.

Rules engineGeofence triggersAuto reminders

Who it suits

Offices where reminders and chase-ups sit with whoever happens to remember. Do not confuse it with the Device Event Engine, which reacts to inputs on the vehicle. This one reacts to business events such as arrivals, expiries and status changes.

Coming soon

Not live yet. Automation belongs to the Complete plan, which has not launched. The vehicle-input rules in the Device Event Engine are live today.

Worth asking in a demo

  • What each rule can send, and to whom
  • How reminder timing is set
  • Where this page's rules end and the device rules begin

Related features

Next feature

Access Control →

Book a demo →