Update: AlleyTrak v5.33.0
Posted on 2022-07-24

AlleyTrak version 5.33.0 Introduces Customer Blacklisting,  Reporting Enhancements, Enhancements for Double Booking Prevention, and Enhanced Address Verification.

Reservation Blocks Revamp

We're so excited to have a revamp for Reservation Blocks for everyone to use. Previously Reservation Blocks were created through a task queue which resulted in a delay for block creation. This delay usually took 2-3 minutes to create, but on busy days and many blocks in the queue the delay could have been a bit longer.

This new and improved method for creating Reservation Blocks is instantaneous. This provides a faster editing process and removes the delay between creation request and when it is available for end-users. In addition to these benefits, we've been able to extend the max duration for blocks to now run for up to 12 months (previously 6 months). 

Enhancements for Double Booking Prevention

We've added new enhancements to our double booking prevention tools which will close a gap that was identified within the system. This enhancement taps into preexisting functionality and requires no modifications to implement.

Enhanced Address Verification

In an effort to strengthen payment processing and authentication, we've implemented new functionality to support the Authorize.Net service for Enhanced Address Verification. This functionality will have the customer provide additional address information as part of the checkout process to further prove they are the intended card owner.

With this new functionality, you are able to more tightly define your enhanced Address Verification settings in AUthorize.Net based on your centers preferences.

Customer Blacklisting

If you've ever wanted to prevent specific customers from booking reservations online, this new control is for you. With the new Customer Blacklist functionality you can prevent specific customers from booking reservations online.

The Customer Blacklisting control allows you to prevent customers by specific provided parameters like Customer Email, Phone Number, and IP Address.

It's worth noting that Customer Blacklisting is not a guarantee to block customers from booking. For example the blacklist prevents customers with a matching email or phone number from booking a reservation. However if the customer restarts the booking process and uses a different email or phone number, they could get around the blacklist rule.

The IP Address rule is a little bit more “sticky”. Assuming the customer stays on the same network when booking a reservation, that IP address will always be blocked and can't be worked around by changing their contact details. However changing the users internet network (switching off wifi for example) could allow them around this rule. It's also worth noting that if for example you blocked an IP address for one customer who made a purchase while connected to their work wifi, all other customers who would attempt to book while on that same wifi network would be blocked.