¶ Scenario triggers
A scenario is triggered by an event. Triggers are available based on the compatibility of the devices available in the customer environment. Each scenario has to be configured with one triggering event type.
¶ Any alarm
Category: Alarms
An alarm of any alarm type is generated by the selected device(s).
¶ Generic alarm
Category: Alarms
An alarm of the type generic alarm is generated by the selected device(s).
¶ SOS button
Category: Alarms
An alarm of the type SOS button is generated by the selected device(s).
¶ Man down
Category: Alarms
An alarm of the type man down is generated by the selected device(s).
¶ Ripcord
Category: Alarms
An alarm of the type ripcord is generated by the selected device(s).
¶ Timer
Category: Alarms
An alarm of the type timer is generated by the selected device(s).
¶ ARC alarm
Category: Alarms
An alarm that is dispatched to an ARC (available in reseller environment only).
¶ Alarm closed
Category: Alarms
An alarm of the selected device(s) is closed.
¶ Assistance request closed
Category: Alarms
Any assistance request is closed.
¶ Connection changed
Category: Device status
The connection of (one of) the selected device(s) changes. The device needs to support a live or periodic connection with the platform in order to be able to use this trigger.
Select the trigger Connection change.
To configure this scenario:
You can select the source of the trigger, this can either be one or more devices (or any device), one geofence or one team (only when these modules are enabled for this customer account).
You can invert the selection, so that you can exclude the selected source.
You must choose the connection trigger for this scenario. This is either connection lost or connection established.
You must choose the timeout for the trigger. This will make sure it only triggers when the device is in a (dis)connected state for a specified duration. For example, to reliably determine if a device is actually offline, we recommend to configure a timeout of 60 seconds. This will filter false positives when the device has a short disruption like changing GSM antennae.
¶ Docked
Category: Device status
(One of) the selected device(s) is connected to a charger or docking station.
¶ Undocked
Category: Device status
(One of) the selected device(s) is disconnected from the charger or docking station.
¶ Low battery
Category: Device status
(One of) the selected device(s) has a low battery.
¶ Config error
Category: Device status
(One of) the selected device(s) is having a failed configuration process (available in reseller environment only).
¶ Geofence entered
Category: Localization
A device of one of the selected devices has entered a geofence.
¶ Geofence exit
Category: Localization
A device of one of the selected devices has left a geofence.
¶ Beacon battery
Category: Localization
The battery of the (Twig SRD) beacon is low (battery low signal is received by a compatible device).
¶ SMS message
Category: Other
An SMS message (meeting the filter requirements) has been received by the platform.
¶ Webhook
Category: Other
A webhook request is received by the platform.
¶ Quick button
Category: Other
A quick button configured with this scenario is pressed on a device.
It is also possible to create a tile on a dashboard that serves as a quick button trigger.
¶ I/O change
Category: Other
An I/O change occurred on a connected gateway - configurable to trigger on ‘make’, ‘break’ or any change.
¶ ESPA message
Category: Other
An ESPA message that meets the configured (REGEX) filter is generated by the ESPA gateway.
Category: Other
An email is received on a uniquely generated email address.
¶ Multi-tenant
Category: Other
Another customer account triggered this scenario with one of their scenario actions.
¶ Scenario disabled
Category: Other
It will trigger when;
- The selected scenarios will be disabled automatically because it is triggered too many times;
- The selected scenarios are disabled by a user manually;
- The selected scenarios are disabled by an account manager.
It will not trigger when the scenarios are automatically disabled when an account is archived.
¶ Message not acknowledged
Category: Follow-up
The text message was not acknowledged in time.
¶ Too little turnout for assistance requests
Category: Follow-up
After the given delay, there are too little people that have accepted the assistance request.
¶ Inverted scenario trigger explained
You can create quite complex scenarios with the inversion option on certain triggers. This inversion is created to be able to address an virtually unlimited number of situations.
You will find a small explanation written beneath the inversion switch.
But because this is a bit limited. Here is an example.
Given there are 3 devices.
- Android
- iOS
- Twig
There are 2 teams.
- Team Android, with Android connected
- Team iOS, with iOS connected
Twig is not connected to a team.
There are 2 geofences.
- Geofence Android, with Android connected
- Geofence iOS, with iOS connected
Here is a table of scenarios and a
| Scenario |
Event |
|||
| Alarm by Android and present in Geofence Android | Alarm by Android and not present in Geofence Android | Alarm by iOS | Alarm by Twig | |
| Alarm from device Android | ✅ | ✅ | ❌ | ❌ |
| Alarm from device iOS | ❌ | ❌ | ✅ | ❌ |
| Alarm NOT from device Android | ❌ | ❌ | ✅ | ✅ |
| Alarm from device iOS or Android | ✅ | ✅ | ✅ | ❌ |
| Alarm NOT from device iOS or Android | ❌ | ❌ | ❌ | ✅ |
| Alarm from Team Android | ✅ | ✅ | ❌ | ❌ |
| Alarm NOT from Team Android | ❌ | ❌ | ✅ | ✅ |
| Alarm from Geofence Android | ✅ | ❌ | ❌ | ❌ |
| Alarm NOT from Geofence Android | ❌ | ❌ | ✅ | ✅ |
| Alarm from Geofence Android or iOS | ✅ | ❌ | ✅ | ❌ |
| Alarm NOT from Geofence Android or iOS | ❌ | ❌ | ❌ | ✅ |
| Alarm from Team Android or iOS | ✅ | ✅ | ✅ | ❌ |
| Alarm NOT from Team Android or iOS | ❌ | ❌ | ❌ | ✅ |