AlleyTrak version 5.117.0 Introduces Customizable Waiver Questions, SelectPi Integration Updates, and More!
Customizable Waiver Questions
We're excited to launch the first iterative of customizable waiver questions. Similar to custom booking questions, you can now create custom questions and fields for customers to review and fill out as part of their waiver submission.
For the initial launch of customizable waiver questions, we've added the ability to create custom text fields and checkbox input collection options. Similar to custom booking questions, you can create validation rules to determine if the fields are required or optional.
SelectPi Integration Updates
We've added a new control to help determine when AlleyTrak will communicate with SelectPi to generate the ball redemption code. This new control supports two options At the time the booking is created, and at the time the event is checked in.
Creating the pin at the time of the booking is a great and simple way to go. It's the default and our recommended approach. However there are some benefits of creating the code instead at check-in.
Reporting in SelectPi only records transactions at the time the pin code is generated. This can create some accounting accrual considerations to manage.
SelectPi pin codes are available immediately after redemption. By delaying the pin-code redemption process until the customer is checked in, will avoid the customer redeeming the balls before their scheduled event date/time.
If the customer has a remaining balance, and they pay that balance the day of their event, AlleyTrak will automatically generate and send the pin-code to them. If the customer pays their remaining balance before the day of the event, we will not generate the code until check-in.
Other Updates
We've redefined the term presented to customers when showing how many “spaces” are available for bookings by time of day. Instead of spaces, we've renamed it to bookings. This should more accurately describe to the customer that at the various times, there are x bookings available.
We've resolved a small bug impacting Custom Hour creation for specific dates, that would not apply correctly if the underlying start/end dates did not encompass the selected specific date.
We've revised the SMS/text message tokens for Inrange and SelectPi to output a string containing the term and code to better support instances if/when the Inrange or SelectPi pin was not generated.