By industry
Gym booking software best practices: first class
A new member picks a class, reads a waiver, and finds the class gone when they return. Mimiq sends simulated visitors through the first booking and shows the step where each one gave up.
What are the best practices for gym booking software when a new member books a first class?
Put the single visit option, the waiver requirement and the account step on the class page, before anyone is asked for a password. Keep the chosen class held through the waiver, the account step and the payment step, and say how the waitlist and the cancellation rule work before the member confirms. A simulated test books a first class as a visitor with no account, follows every step to the payment screen, and shows where the booking broke and what the screen said.
What this looks like in a report
“I picked the 6 pm class and now it wants me to read a waiver. I have to scroll a long page to find the checkbox. When I came back, the class was not highlighted, so I'm starting again.”
The fix. Keep the chosen class selected when the visitor returns from the waiver, and say on the class page that a first visit needs a signed waiver.
An illustration. Run a test to see your own.See a real sample report
A selected class disappears when the waiver is signed
A new member finds a class, clicks Book and is asked to make an account. After the account, the waiver appears as a separate page. The member reads it, signs, and returns to the booking, which has lost the class. The class is not shown as selected, and the page offers no obvious way back to the schedule. The member has now made an account and signed a waiver without a class in hand. Some will not find the schedule again, and the gym sees a signed waiver with no booking attached.
- Book as a visitor with no account. Does the class page say whether an account comes first?
- Sign the waiver. Is the chosen class still selected when you return?
- Find a full class. Does it offer a waitlist button that works, or only the word Full?
- Check the confirmation text. Does it say booked, requested or held?
- Look for the cancellation rule before you pay, not only in the confirmation email.
How it works
- 01
Book one class with no account
Start from the public schedule on a phone and choose a class you have never taken. Write down every screen between the class and the first request for an account, a payment or a waiver. The first wrong turn is usually on the class page, where a visitor cannot yet see whether a single visit is possible.
- 02
Sign the waiver, then come back
Sign the waiver as a new member would. Note whether the class is still selected when you return, whether the time and the instructor are still shown, and whether a back link leads to the schedule. A booking that resets at this step is one way a first visit gets lost.
- 03
Try a full class and the payment step
Pick a class with no spots left, and see whether the page offers a waitlist with a button that works. Then take a class with spots and go to the payment step, and stop there, since the test cannot pay with a real card.
Wrong and right: the class page before any account step
A wrong version sends every visitor to 'Sign up to book' on a class card. A visitor who only wants one class learns, one screen too late, whether a single visit is possible. A right version puts a short line on the class page: whether a first visit needs an account, what a single class costs in the gym's own terms, and whether a waiver must be signed first. Visitors who cannot book one class do not need to know the rest. Visitors who can should see the path before they type a password.
Check the class page with a visitor who has no account and no membership. Write down the first word that asks for one. If that word comes before the class details, the page sends a casual visitor to a form they did not expect. Then compare with a visitor who already has an account, since a logged in view can hide the same wall from you.
Waivers and holds: the booking that resets
A wrong version holds the class only in the browser session, so a waiver page that takes a while or a page refresh clears the choice. The visitor returns to a schedule with nothing highlighted and starts again. A right version keeps the class in the booking through the waiver and the account step, shows how long the spot is held in plain words, and gives a visible way back to the schedule.
Full classes, waitlists and the word booked
A wrong version shows Full with no button, so a member who wanted that class leaves and does not come back. A right version offers a waitlist with a clear button and a note on what happens next, such as an email when a spot opens. A visitor who sees Full and nothing else will assume the class is closed for good.
The confirmation is the last place a booking goes wrong. A screen that says booked when the spot is only held makes a visitor believe they are in the class, and then they are surprised by a cancellation rule they never read. A right version uses the word the booking really means, repeats the cancellation rule on the confirmation screen, and sends the same words in the email.
What you get with Mimiq
- 01
Run it by hand, or on every pull request
Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.
- 02
Bugs and usability problems in one report
The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.
- 03
Visitors that behave like your audience
Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.
- 04
A prompt to fix each problem
Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.
- 05
Follow every visitor
See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.
The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.
A new class type or a changed waiver can send new members back to the start
The first run finds where a new member's booking reset, filled up or was called booked too early. A fix changes the class page, the waiver step or the confirmation text, and a new class type, a timetable change or a revised waiver can bring the reset back. Run a first time member with no account after each change, then a waitlist member, so both paths get checked.
Starter
Try it on one launch
About 4 tests of 5 visitors
- Visitors on your landing page, signup and checkout
- Where they left and why, with a fix to copy for each problem
- Run it in the app or on every pull request
- Ask any visitor a question, included
- Test accounts and protected previews
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Can this tell me how many new members will book a first class?
No. It does not predict how many new members will book, and it cannot tell you how many chose a different gym. It shows the step where a simulated visitor stopped, what the screen said, and whether the booking held.
Can a test visitor sign a real waiver?
A test visitor can reach a waiver page and tick the box if the form allows it, but that signature is not a real one from a real member. Use invented names, and keep real member details out of the run, since they are personal data.
Does the test check my membership rules or pricing?
No. The test follows the screens. It does not check whether a membership covers a class, whether a drop in rate is right, or whether your cancellation rule suits your local rules.
What does the test stop at?
The test stops at the payment step. Visitors cannot pay with a real card, so a paid class ends there, and the report shows that screen. A free or drop in booking can go further if the site allows it.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.