The SOS button on every walt adds a layer of safety for all of your employees. If someone triggers the SOS button, an alarm will ring the walt, letting others around them know they need help. But then what? We can walk through how you can set up a workflow on the backend, so when an SOS is triggered, the right teams are made aware and can take action ASAP.
To create an SOS workflow, you will need to navigate to your Workflows tab at the bottom left of your screen, then select the blue Add Workflow button at the top.
It will pull you into a General page. Here, you will name your workflow (example below).
You will also want to make sure the Enabled checkbox is selected for the Workflow to be active.
Determine what sites you want this Workflow to be under, as well as any tags that are needed. Click the blue Save button at the bottom right of the screen, then move on to the Workflow tab.
You will start building your Workflow by clicking Add under Add Trigger.
The SOS Triggered option will be at the bottom of the dropdown.
You will then see an option to add a conditional filter, which will allow only that group of people to activate the workflow if they trigger their SOS button. This is not required to create a workflow, so if you leave this blank, everyone at that site will be able to trigger this workflow.
Once you save that, you will now want to add a Then action.
Click on Unless if you want to add other Triggers to prevent a Workflow from running.
Once you click Then, the below Action banner will appear.
Our example: Action is Send channel message if SOS button is triggered.
- Action: Send channel message
- Message: {{person.firstName}} {{person.lastName}} has triggered the SOS man down button!
- Variables such as First Name and Last Name can be inputted into the message (see drop down below)
- Channels: Safety (Admin Defined Channel)
- Action Targets: People with craft equal to Safety
Pro Tip! If you have geofences built out, you can add a geofence variable which will send the users last known location to give you a better idea of where an incident occurred.
- After a workflow has been created and triggered, you are able to review the history of those occurrences.
- The history includes date of triggered workflow, person who triggered the workflow, and what site it was triggered on.
Pro Tip! This history tab is great for audits so you can review anytime an SOS button was triggered.
Setting up an SOS workflow ensures that when someone signals for help, the right people are alerted immediately and can respond without delay. By customizing triggers, messages, and recipients, you can tailor the workflow to fit your organization’s safety protocols and structure. Once in place, this automated response adds a critical layer of protection and peace of mind for your entire team.