Your customers can now use a Google authentication button on the mobile view of the public schedule to create a new account.

Membership renewal payments that fail in Stripe are now flagged more quickly so they can be handled proactively. Instead of waiting for the payment to fail 3 times before taking action, now we immediately mark the pass as suspended and payment failed. We also let the business admin know and tell them whether or not Stripe is going to retry the payment. We do not email the customer.

For express reservations where we show a list of passes that can be used to book into a class, we will only show passes that will be active on the date of the class. So if there is a pass type that has a fixed expiration date that is BEFORE the class date….we won’t show that pass as an option to book.

Before today, if a customer was marked as ‘trustworthy’, we were not showing if they needed a pass for a class they had a reservation for. That was unintentional – trusted access is meant to give customers special access to booking classes, but not to treat them any differently after they have booked. We have fixed that, so now if a ‘trustworthy’ customer does not have an eligible pass for a reservation, then we will display the ‘needs pass’ flag.

We now show a customer’s email address in the dropdown when merging customers. So now when admins have to merge 2 customer profiles into 1, it’s much easier to be sure you are selecting the correct one.

Paused memberships were showing the incorrect paused date. We’ve fixed it, so now the correct date is shown.

There had been a problem under a specific set of circumstances: 1) a customer converted a membership to be paid via credit card AND 2) the current pass was unpaid AND 3) the initial charge for the card FAILED, the system was not linking the current pass to the newly-created invoice. This is fixed, and the pass will now be linked to the failed invoice and will be marked unpaid.

The text that was displayed below the booking button was not respecting the formatting applied in the app editor. That’s been fixed.

A loophole has been cleaned up related to booking when a series has a waitlist. Admins were previously able to circumvent a series waitlist by using the bulk reservation form available on the Customers page. That was leading to waitlisted reservations for individual instances in a series, which should not be allowable. This has been fixed. So now if a series is full and has a waitlist we do NOT show the checkbox for that on the bulk reservation page…which prevents the admin from choosing it. In that situation, any series reservations need to be done from one of the series instance pages.

We have added value totals to two very important reports — the Active Passes and Pass Sales Details reports. If the report spans multiple pages, we’ll show totals for both the page & the entire report.