Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
stylenone
typelist
printabletrue

5-Minute Robot

A "Late Return" is where a

car

vehicle is due back at a certain time and is running late. Emails can be sent when the system recognises a booking that was due back is not back yet, and subsequent emails can continue to be sent until the booking is checked in (this is system settings dependent).

PoolCar has the ability to automatically send email alerts for Late Returns to System Administrators, Pool Managers or Vehicle Contacts via a "5 Minute Robot".

A Robot is a digital housekeeper that runs a certain automated task. The "5 Minute" variety means the Robot fires every 5 minutes, 24 hours a day, and is useful for automating anything that needs a watchful eye ... such as cars not back on time

Image Removed
Image Added

What constitutes a Late Return?

When a user makes a booking, they specify the start and end times. The end time is when they expect to be back. A Late Return is when the

car

vehicle is not back

when

by the time the booking was due to end.

A Late Return is usually either because the driver is stuck in traffic, or they have not allowed enough time for their journey. There are other potential reasons, of course, such as a breakdown, accident or some other reason that may warrant a welfare check.

In a context when we are sharing

cars

vehicles, Late Returns can cause flow on effects for other staff members who have booked the

car

vehicle for a certain time, because they assume

the car

the vehicle will be back on time from the previous booking. Examples include take home

 cars

 vehicles, or part-private-use

 cars

 vehicles, i.e. a staff member commutes home in the

car

vehicle as part of their salary package and needs to leave by 4pm so therefore the

car

vehicle must be back by 4pm.

How does the system know the

car

vehicle is Late?

An important point to note is that you must be using Check Out/In. When a Check Out occurs it tells the system the booking is in progress. A Check Out can happen when:

  • You have a central kiosk PC set to display the Check Out/In page. A Check Out occurs when the user taps the Check Out button to indicate they have commenced their booking.

  • Or, when a user taps the Commence Journey button on the mobile website/app.

  • Or, if you have key cabinets installed, a Check Out occurs when the user removes the key from the cabinet.

  • Or, if you have automated check out/in via the vehicle generating an exit geofence event when it leaves its base location (for vehicles installed with Smartrak Telematics only)

Conversely, a Check In tells the system the booking is complete. Such as returning the key to the key cabinet.

The 5-Minute Robot is constantly checking the time between the Booking End time and whether or not a Check In has occurred. If the Booking End time has been and gone, with no Check In, then the

car

vehicle is deemed to be "Late".

How Late is Late?

When doing the Late check, the system will allow a certain time buffer.

By default, this is 15 minutes (5 minutes in example below) and

you

can

change this

be changed to suit your organisation from the Application Settings > Robots page

Image Removed

As depicted in the screen shot, the system will send

alerts continuously

late return notifications every 15 minutes after the initial "Late" determination.

With the Late return alerts active hours, you can select if you want the alerts to be sent out only during business hours or at all times.

Image Added

Who receives the alerts?

Alerts are sent via email to the System Administrators

. At the present time there is no way to specify who should receive the alerts - it is fixed at being all users in the System Administrator role

, Pool Managers or Vehicle Contacts. As well as the option of sending the alert to the overdue booking holder as well.

There are two types of alerts sent. The first is a "normal" alert, where a Late Return has been determined but there is no real pressure as the next booking is not for some time. You can treat these alerts as an FYI or the trigger for a welfare check.

Image Removed
Image Added

The second type is a little more urgent, because the system has detected an adjacent booking

which

that may need your attention. The adjacent booking will be impacted if the

car

vehicle is not back soon. In which case you, as the System Administrator, may need to reassign the next booking to another

car. At present there is no way to automatically reassign the next booking, but we anticipate this being a new feature in the future

vehicle, or if the automated re-allocation is enabled, then the PoolCar system can re-allocate automatically.

The contents of the alert will be as above, with some additional text:

Image Removed
Image Added
  • If you are unable to find an answer to your question in here please log a support request via the Smartrak Service Desk 

Self Help | Service Desk | Service Desk Help | Knowledge Base | Trouble shooting | Smartrak Portfolios