Before you launch or pay for traffic

Online schedule booking website: why slots fail

A visitor who books a slot expects the time they tapped to hold. Mimiq books simulated visitors through your schedule, so you see where a free-looking slot turns out to be taken.

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

How should an online schedule booking website work for a first-time visitor?

The visitor should choose the service first, then see only the times that fit it, in a time zone they can read. The slot they tap should still be free when they tap it, and the confirmation should say what happens next. A simulated run books a slot from start to confirmation and records the step where the visitor was stopped, such as a taken time or a time shown in the wrong zone.

What this looks like in a report

Who
Aziz, a teacher who wants a haircut before the new term starts
How they arrived
Opened the studio's booking link from a text message
Where they stopped
Time picker, after choosing a service

“The times do not show which time zone they are in, and the first one I tapped said it was taken just as I pressed it. I am not sure the other ones are free either.”

The fix. Show the time zone next to the slot list, and convert the times to the visitor's zone when the browser allows it. Check each slot again when it is tapped, and when one is taken, show the next free times on the same screen.

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

A slot that looks open can be taken by the time the visitor taps

The schedule on the page is usually a snapshot. It is loaded when the visitor arrives, and a booking made by phone, by a staff member or through another tool since then may not appear on it. The visitor picks a time that looked free, presses it, and gets a message that it is taken, sometimes after they have typed their name and email. Another visitor then sees the same time offered, because the page still shows it as open. The owner checks the calendar, sees a full afternoon, and does not know why the page keeps offering the gap.

  • Does the visitor pick the service before the calendar shows any times?
  • Are the times shown in a time zone the visitor can read, with the zone named?
  • Is a slot checked again when it is pressed, not only when the page first loaded?
  • Does a taken slot show the next free times on the same screen?
  • Does the confirmation show the date, time, place and how to move the booking?

Choose the service first, or the calendar offers times that do not fit

A calendar that shows every open time before the visitor picks anything forces a guess about length. Wrong: the page lists twenty-minute gaps, the visitor picks one for a ninety-minute service, and the booking fails at the last step. Right: the service and its length come first, and the calendar offers only the start times where that length fits without running into the next booking. The same rule applies to staff. If a visitor can pick a person, the times should belong to that person, not to the whole team.

A run shows this as a slot pressed, then a return to the list, then the same slot pressed again. The visitor's note usually names the length or the person they wanted, which tells you which rule is missing. Read the note before you change the calendar settings, because a longer slot length will not fix a missing staff filter.

A free-looking slot has to still be free when it is tapped

Many schedule pages read availability once, when they load, and keep it on screen so the page feels fast. That is fine until someone else books the same time. A phone call, a walk-in or a booking in another tool can fill the slot while the visitor reads the page. The owner's calendar then shows the time as taken, and the booking page still offers it. The visitor finds out only when they press it.

Check the moment of the press. A booking page that checks the slot again at that moment can say 'this time was just taken' and show the next free times. A page that does not check will either accept a double booking or fail after the visitor has typed their details. Neither is acceptable for a clinic or a studio, so ask your booking tool how it handles a press on a slot taken moments earlier, and test that case directly.

The confirmation has to say what the visitor does next

A confirmation that reads 'Booking received' with no date, no place and no way to change the time leaves the visitor unsure whether anything was booked. They may book again, or call to check, which is the work the page was meant to remove. Wrong: a grey box saying the request was sent. Right: the date and time with the time zone named, the address or the video link, a line on how to move or cancel, and the same details in the confirmation email.

Visitors have a working inbox, so the run can check that the confirmation email arrives and what it says. If a deposit is due, the run stops at the payment step, because visitors do not pay with a real card. Book one test slot yourself to see the full confirmation, and cancel it afterwards. Compare the screenshot with the email word by word, since a date that is off by one day is the kind of mismatch a visitor will not report.

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 staff member or a changed opening time can reopen taken slots

A new staff member, a changed opening time, a different slot length or a new time zone setting can all change what the calendar offers without any visible notice. Rerun the same visitor bookings after each of those changes, including one from another time zone. Keep the earlier run, so you can see which slot list changed and which setting changed it.

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

Does a run book a real slot in my calendar?

It can, if the run gets as far as the confirmation on your live site. A completed booking is a real booking, so run the test on a service you have set aside for testing, or on a time you can cancel. Do not run it against a slot a customer might want.

Will more people book if the calendar shows more slots?

Showing more slots helps only when the slots were the problem. The test does not predict how many visitors will book. A visitor who taps a taken slot and leaves points to a stale calendar, not a shortage of times. Track booking counts in your own records to see whether a change moved them.

Should visitors pick a person or take the first free slot?

Either can work if the page says which one applies. A choice of person suits a regular client who wants someone in particular, and first available suits a first visit. Mixing the two without saying so is the trap, because a visitor who picked a person and got another one leaves.

What happens when the visitor is in another time zone?

The browser sets their zone, so the page must show slot times in a form they can read. If the page shows only the studio's zone, the run records a visitor who could not tell which time they were booking. That is the step to fix, and a clear zone label usually solves 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.

5 visitors try to .