By industry

Bike repair online booking: the grey next button

A rider with an e-bike picks other in the bike type list, and the next button turns grey with no reason shown. Mimiq sends simulated riders through your booking and shows each step where one stalled.

5 visitors try to .
First test free with an accountRun it from your coding agent

Why does a bike repair booking stall before the rider picks a date?

A bike repair booking stalls when a rider picks an option the form did not expect, such as other, and a required field keeps the next button grey with no message. Forms often list road, mountain and hybrid bikes and little else, so an e-bike or a folding bike has no clean choice. A simulated test picks the bike the way a rider would and shows the field that stopped the run and whether any message appeared.

What this looks like in a report

Who
Wen, rides an e-bike across the river to work every morning
How they arrived
Opened the booking link from a bike shop's listing on her phone
Where they stopped
Bike details, after picking other from the bike type list

“There is no e-bike anywhere in this list. I picked other and typed e-bike, and now the next button is grey and nothing says why. Is it broken, or do I need something else first?”

The fix. Add e-bike and folding bike to the bike type list, and when a rider picks other, show a text field with a line that says what the shop needs next. Put a message under any disabled button that names the missing answer, and make sure the button works from a keyboard.

An illustration. Run a test to see your own.See a real sample report

An e-bike rider meets a list that was written for other bikes

The bike type question sits near the top of most bike repair forms, and it decides what comes next. A rider with an e-bike, a folding bike or a cargo bike looks for their bike and finds nothing close. They pick other, and a text box appears that wants a make or a description. If the box is empty, or the rider types a character the form does not expect, the next button stays grey. Nothing says why. The rider tries the button again, then tries another shop. The owner tested with a road bike and never saw the grey button.

  • Is there an e-bike or a folding bike in the bike type list, or only road and mountain?
  • After you pick other, does a field appear with a line saying what to type?
  • With the next button grey, is there a message near the field that says what is missing?
  • Can you move through the form with the Tab key on a laptop and reach the next button?
  • On a phone, does the next button stay visible while the on-screen keyboard is open?

The bike type list sets the rest of the form

Once the bike type is chosen, the rest of the booking often changes. A road bike may skip a question about tire width, while an e-bike may ask for a battery check or a service the shop only offers on certain days. When the list has no match, the form has no path to follow. The owner sees a tidy dropdown and assumes riders will find their bike. Count the bike types on your list, then compare them with what riders actually bring in. Add the common ones that are missing, even if the service is only a basic check, so the form has a route for them.

A disabled button with no message, and how to find it

A grey button is a state, not an answer. The rider does not know which field is holding it. To find the cause, open the booking on your own phone and walk the form. Pick other, leave the text box empty, and try the button. Then type one word and try again. If the button comes alive only after the box has text, the form needs an answer it never explains. Next, walk the same path with a laptop keyboard. If the Tab key moves past the field without landing on it, a rider who cannot tap will not get through either. Write down the field where the button changed state.

A rider with a flat and a rider with a full tune-up

A rider with a flat and a rider booking a full tune-up meet the same form, and it has to tell them apart. If every service asks for a drop off day, a rider who needs a tube swapped sees a wait they did not expect and leaves. Compare the service list with the time list. Each service should say how long the shop keeps the bike before the rider picks a time, and that wait should match what the shop actually does.

What you get with Mimiq

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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 bike type can add a field that stalls the next button again

The first run finds the field. The fix adds bike types, a text box or a message under the button, and a later edit can undo any of them. Walk the same e-bike rider through after each change, then a road bike rider, so the common path still works. Repeat it when you add a service or change the drop off days, since one small change to a list can disable the button for every rider with that bike.

Starter

Try it on one launch

$9 once
120 credits, never expire

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
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Can this tell me how many riders will book a repair online?

No. It does not predict how many riders will book, and it cannot tell you how many riders you lose at the bike type step. It shows the field where a simulated rider stopped and whether the form said anything about it. Booking rates come from your booking tool and your site analytics.

Can a simulated rider finish a booking?

The test goes as far as the last step a rider can finish. Visitors have an email inbox, so a confirmation reaches them, but they cannot receive a text code and cannot pay a deposit with a real card. If the booking takes a deposit, the run ends at the payment step.

Should I give the rider a real name and a frame serial number?

No. Use made-up details, including a made-up bike and a test email inbox. Screenshots in the report show what the visitor typed, so keep customer names, phone numbers and frame serial numbers out of the run.

What if the bike type list loads from another tool?

The test does not care where the list comes from. It sees the page a rider sees. If the list is slow or never becomes usable on a phone, the report shows the step and whether the field ever worked, so check it on a phone in a private window first.

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.

5 visitors try to .