Rides left at a glance
Each member sees classes remaining, the expiry date and the date of the last ride, in one short list.
A customer portal website for indoor cycling studios gives members one secure place to check their class pack balance, pause a membership and update a card, without calling the front desk. SIZ Group builds that portal around the way riders and staff actually use it, from Austin, Texas.
Once a rider has a monthly unlimited plan or a ten-class pack, the questions change. They want to know how many rides are left, when the plan renews, why a card was declined and whether a missed class can be credited. Right now most studios answer those questions by phone or text during the busiest hour of the day, which is also when the instructors are getting the room ready.
A member portal moves those answers to a screen the rider already checks. It works best when it is a short, honest list of what the member can do, and it leaves the sensitive steps to a staff member who can verify identity. The goal is fewer interruptions at the desk, not a locked-down account page that nobody opens.
Freezing a membership for a holiday trip, moving a class pack to a different family member, and updating a card after it expires make up most of the requests we would expect to see in a studio of this kind. Each one takes a few minutes of staff time, and each one can be wrong if it is entered in a rush. Those three actions are the strongest candidates for self-service.
Changes that affect revenue, such as refunds, late cancellation fees and retroactive credits, should stay with staff. The portal can show the rule and the member's history, then send the request to the desk with the right details already filled in, so the person at the front never has to ask the rider to repeat the same story.
Most cycling studios already keep memberships and class packs in a platform such as Mindbody or a similar studio management tool. The portal should read from that system and write back through its supported connection, so a rider who pauses a membership online appears paused on the front desk screen within the same minute. Two copies of the same membership record are how studios end up double-charging people.
Payments should go through the processor your studio already uses. Stripe is common for this kind of billing, and it lets the portal show the last four digits of a card without the studio ever holding the full number. We confirm the exact connection in the scoping call, because some older platforms only allow read access.
Each member sees classes remaining, the expiry date and the date of the last ride, in one short list.
Riders ask for a pause with dates, and the request reaches the desk with the membership terms attached.
New cards are entered on a secure payment form, so the studio never holds the full number.
Past classes, late cancellations and credits show on one timeline that matches the front desk record.
Instructors, desk staff and managers each see only the screens their job needs.
Member accounts hold names, phone numbers, payment history and sometimes injury notes, so the portal needs clear limits. Staff should see only what their job requires: the instructor sees the class roster, while the office manager sees billing. Access by role is set up before launch, and removing a former employee takes one step.
Card handling should follow PCI DSS requirements, and the simplest way to meet them is to keep card data with the processor. Password resets go to the verified email on file, and sessions time out on shared gym tablets. Health notes stay in the intake record, not the member's profile page, so a rider's knee injury is never printed on a screen near the bikes.
The most common mistake is building an account system before the studio has agreed who handles exceptions. A rider asks for a refund, the portal says no, and the front desk says yes, and the member loses trust in both. Write the rules for refunds, freezes and transfers down first, then build the portal to match them.
Another mistake is asking members to create a password on the first visit with no reason shown. Riders who have never logged in will abandon the form. Offer a one-time sign-in link sent to the phone or email they already gave at booking, and ask for a password only if they want one.
January is the peak for new sign-ups and for pack purchases made as resolutions. Many riders then freeze or cancel by March, which means the portal should make pauses easy to request without any penalty wording that feels like a trap. Summer brings holiday freezes and travel, so a clear pause option protects the membership count.
Late autumn is quieter for memberships, but it is when many renewals come round. A reminder that goes out two weeks ahead, with a one-click pause option, keeps the count from sliding over the new year.
Usually yes, if the studio platform exposes pack balances through a supported connection, and that is one of the first things we check on the scoping call. Where the data stays locked inside the platform, riders can ask for a balance through a short form, and the desk answers the same day.
The owner sets that rule. Many studios let riders request a freeze in the portal and approve it against the written policy, while refunds and fee waivers stay with the manager. Every request is timestamped, so a decision never disappears into a text thread.
Card numbers stay with the processor, and staff never see a rider's password. Each team member sees only what their role needs. Access is set before launch and written down, so the studio can answer who sees billing and who sees the roster.
It is a common order. The booking site and the portal read the same schedule and account records, so the portal is one more set of screens added later rather than a rebuild. The order of work is put in writing before anything is built.
Send us your membership types, the rules behind refunds and freezes, and the software you run today. The free call sets the scope, and the price arrives in writing before any build starts.