Description
Numerous trackers are equipped with the valuable SOS button functionality, either in the form of an external button or integrated within a personal tracker device. The SOS button offers a vital lifeline during critical situations, enabling individuals to swiftly seek assistance. For instance, in scenarios where a child activates the SOS button, immediate SMS or email alerts are triggered, alerting parents or guardians to the urgency of the situation.
This rule holds substantial utility across various contexts. In a personal safety context, elderly individuals or those living alone can promptly summon help during medical emergencies. Similarly, for outdoor enthusiasts or workers in remote areas, the SOS button ensures a quick response in case of accidents or unforeseen predicaments.
In business applications, consider a scenario involving lone workers or field service personnel. Equipped with trackers featuring an SOS button, these employees can promptly notify their supervisors or emergency teams if they encounter hazards or require immediate assistance. This rule bridges the gap between safety and rapid response, proving indispensable in enhancing personal security and efficient crisis management.
Please be aware that there are two ways to utilize the SOS button function. It can either involve an SOS button connected to the digital discrete input or a dedicated SOS input socket on the tracker. Both methods can yield the same results; however, the approaches to understanding and utilization on the platform differ. When utilizing a discrete input, users simply create a discrete input within the Devices and Settings menu, under the Sensors and Buttons section. In this scenario, the "Input Triggering" rule type should be employed. Conversely, using the "Pressing SOS button" rule type involves relying on the hardware component and its configurations, obviating the need to create a discrete sensor and specify the input number and its type.
Settings
As this rule is based on hardware configurations, there is not much to configure in the rule itself.
Bind zone to rule:
Enables geofence rule binding.
Geofence:
Fill out the section if the rule needs to work only inside/outside of the selected geofences.
Map button:
Shows bound geofences on the map.
Notifications
Emergency notification:
is used for important events. A message on the screen and the sound signal can only be disabled by clicking on the notification. Please note, some browsers can block notification sound until user activity is recorded on the page.
Push notifications:
Receive push notifications on the mobile app and web interface.
Add geofence name to the notification:
Adds names of the specified geofences to the notification text. This option is available only when the "Inside" geofence binding radio button is selected on the "Settings" tab.
SMS notifications:
List of recipients for SMS notifications when the event occurs.
Email notifications:
List of recipients for email notifications when the event occurs.
Schedule
Set a schedule for when the rule will run. If your schedule indicates that the event should not run some day or time period, it will not appear as a notification in the user interface, and notifications via SMS or email will not be sent. Additionally, you can choose a default template for quick scheduling.
The platform specifics:
- The "Pressing SOS button" alert has a 30-second reset timer, meaning the alert event will not occur more often than once every 30 seconds. If this type of event occurs in time the rule has been waiting for the reset, this event will be omitted by the platform, including the reports.
- In this rule type, users have the flexibility to select multiple trackers which they wish to receive notifications from. The only requirement is that the selected trackers must support "Pressing SOS button" events and the feature must be integrated on the platform for given trackers. This means that users can choose multiple compatible trackers to receive notifications from, allowing them to monitor harsh driving events across various vehicles or devices in a convenient way.
- Whenever the platform identifies a hardware event of this type from a packet of tracker data with no valid coordinates in it, the platform counts the event as a valid one and displays it regardless of whether the event occurred within or outside the bound geofences. The logic of the Inside/Outside radio buttons is also ignored in this case. This behaviour is due to the fact that showing a controversial event once more is better than omitting it.
Event reports
To view the dates when the events were received, you can build the "Report on all events" report.
