False Alarms can happen. But they can be very time-consuming, and there are some simple steps you and your team can take to reduce them.

Many of these steps will need to be taken by the User on an individual level, but if you are receiving many of these False Alarms, you may need to discuss their reasons with your Team.

Not getting Notifications from the app is the leading cause of missed Check-ins and Session Expiry Alarms. This is usually caused by the User not setting their app Permissions correctly.

We have guides on setting Permissions for iOS and Android to help your Team set their them correctly.

Force closing the StaySafe app is easy to do, but causes many False Alarms as it prevents the app from sending the User Notifications informing them that they need to Check-in.

Keep the app running in the background instead of hard-closing it to prevent this.

Depending on your Organisation's settings, Audible Alert's may or may not be required for your Lone Workers. If they are not turned on, this can cause Notifications to be missed.

You can see a guide on setting up Audible Alerts for your Organisation or Team here. Alternatively, your Users can set them up individually using this guide.

Using a Bluetooth speaker or headphones can prevent Notifications from getting through with some devices.

With iOS devices, you can override this by going to the phone's Settings > StaySafe > Announce Notifications > On

With Android Devices, go to Audible Alerts > toggle on Override System Volume.

Some Alerts are optional. If they are not needed for your User's specific situation, they can trigger False Alerts.

The Discreet Panic functionality on Android can often cause False Alarms. The app measures the phone screen by turning ON/OFF rather than pressing the power button. On some phones, your screen can behave in this way when you receive a message, your alarm goes off, or when you are on the phone.

Users need to test this case on their device and change the settings. If this is causing a lot of False Alerts, the following steps can also be taken.

Go to Settings > Discreet Panic > toggle on Ignore when on a call > toggle off Detect when not running a session.

Non-Movement Alerts can cause some False Alarms. This is often because of the sensitivity of the accelerometers on your phone. It's always a good idea to recalibrate the accelerometers to ensure accuracy.

Using the Non-Movement feature when it's not required is also a leading cause of False Alarms. Turn this feature off when you do not need it.

If Fall Detection is enabled on either your User's phone or a wearable device, it can cause False Alarms. You can choose the device's sensitivity in the App, and decrease it if you continue to have False Alarms.

Phone signal is another leading cause of False Alarms. It is one that StaySafe cannot affect as we are using the signal that a phone has access to.

It's always advisable for your Users to give themselves some extra time on their Sessions and be mindful when in remote areas.

Find out how StaySafe uses phone signal here.

It is not uncommon for a User to miss notifications while driving. We recommend that they Check-in or extend their Sessions before beginning their journey.

We are currently working on Driving Mode to remove distractions whilst driving, and stay inline with the latest legal changes to handling of phones whilst driving. Driving Mode will be available to Users soon.

Find out about Using the Map Page, how to access an Individual's Session View and How to Respond to an Alert.