We offer easy check in solutions via bluetooth beacons and the mobile passage addon for Mobility. Which allows the users to see their coming booked classes and check in to them through the Go Active! app.
Conditions for Enabling Check-In
The booking must not already be in a "checked-in" status
The arriveInterval and beacon related settings must be properly configured from BRP Configuration
The booking's start date must be the current date
The booking's start time should fall within the arriveInterval
How to enable the check-in button.
The “Arrival time" corresponds to the current time. The "arriveInterval" is applied to this current time to establish a specific time range. If the booking's start time falls within this calculated range, the check-in button will show to the user.
According to this example, the check-in button will be shown from 2.05 p.m. to 2.35 p.m.
We check the check-in status of every group activity booking every 30 seconds.
The check-in opens button will appear, starting one hour before check-in, which will be a reminder for the user about the check-in class until the check-in begins.
Additionally, the booking will be displayed under the coming up section on the explore page from the reminder time to check-in end time. The user can navigate to the My Bookings page by clicking the arrow icon of that booking.
The user must allow all the permissions related to location and Bluetooth to check in to the class.
If there is a primary device mismatch, the primary device change drawer appears after clicking the check-in button.
After successfully checking in, the booking card's status will change to "checked-in," indicating that the user has successfully completed the check-in process.
Settings Used
Check-In Interval
arriveInterval - Check-in interval for classes [minutes from start]
Entrances
beaconUUID - The UUID of the beacons to search for
beaconIdentifier - The identifier of the beacons to search for
enableMobilePassageTry - Allow entrance from the mobile device
Managing primary device
The setting `numberOfDaysBetweenSwitchingPassageDevice` dictates how frequently the customer can update their primary device. (e.g. if the value is 5, the customer can only change the primary device after 5 days. If they change the primary device yesterday, they will not be able to change the primary device today).