In this article, you will learn how to activate geofence location services.
Users with Admin roles can activate this feature. To change user permissions, refer to the How to Add, Edit and Remove Users article for assistance.
React Mobile Geofencing feature allows users to decide whether they would like to receive mobile notifications while they are away from work/property or not. By default, this feature is disabled. To learn more about the Geofence Feature, refer to the What is the Responder Geofence Feature? article for assistance.
To Enable the React Mobile Geofencing Feature
- Navigate to the Customer Portal (https://portal.reactmobile.com) and log in as an Admin.
- In the top right corner, navigate to Settings.
- Scroll down in settings and find the Responder Geofence section.
- Under the Responder Geofence section, toggle from “Disabled” to “Enabled”.
- Fill out the remaining fields:
- Miles: This indicates the radius of the geofence. For example, if you enter "1" mile, when a responder is 1 mile (or further) from the property, they will stop receiving mobile notifications.
- Latitude and Longitude: if your address is already in your settings, this will be generated automatically. If not, follow either one of the below steps:
- Navigate to the "Admin" tab on the top right corner of the screen, select "Edit Property and Users," and enter the correct address OR;
- Navigate to https://www.google.com/maps and search for your property. From there, right-click on your property and it will provide you with the latitude and longitude. Enter these numbers into the appropriate box (for example, Lat: 47.60949, Long: -122.33017).
- Select “APPLY CHANGES” and Geofence for the responders will be enabled.
Important to note: This setting will enable Geofencing for all the Responders. However, each Responder can choose to receive alerts even if they are outside the Geofence within React Mobile Hospitality application.
For a walkthrough of these steps, refer to the video located at the bottom of this article.
Comments
0 comments
Article is closed for comments.