Now admins can see all emails sent via Punchpass in two places: (1) the customer’s account on the emails tab, and (2) the email messages report. Also, for emails that were sent manually (non-transactional emails), we’ve added a link so you can click and see details about a specific email that was sent.

When you set up a series and you link it to a certain pass, we will now prompt your customers to pay in order to register (even if you don’t have the ‘Require Active Pass to Book’ box checked).

A fix has been made to the installation process for the app (PWA): On iOS, the PWA was showing certain pop-ups twice, and it was breaking the ‘progress loader’ if the client clicked Cancel.

Now when an admin reviews the emails that were sent via Punchpass, you’ll see the Client Messages list more cleanly, page by page, rather than in one giant list.

Punchpass now uses a different Stripe API to process payments made through the admin side of Punchpass (e.g., the ‘Assign Pass’ button on the customer details page). Everything essentially works exactly as it did before except for one change – when an admin goes to assign a pass or membership, you’ll choose the past first and then proceed to the payment info page.

Punchpass now sends your customers an email when they’ve got a membership that’s scheduled to expire in 10 days. If you sell your memberships online, we also provide a link prompting the customer to click and renew online.

Punchpass’s text editor has been upgraded! Now when you copy text from another source and paste it into Punchpass, you won’t lose your formatting. So if you have a place where you’ve drafted your write ups — say, an email or a class description — you won’t have to redo those italics 🙂

When an admin navigates to Manage => Passes, we now show the correct # of memberships under the ‘Total Sold’ column. This number had previously shown the number of passes assigned within the membership.

We’ve closed a loophole that previously allowed admins to enable an archived passtype with fixed start/end dates that were in the past. Now we require the admin to bring the archived pass up-to-date in order to sell it again.

Now when a business admin is assigning a membership to a customer, they can select whether or not payment for the first pass has been received. This mimics the prompt we offer for passes when they’re being assigned by an admin.