By industry

Dentist online booking: why new patients leave

A new patient on a phone wants a cleaning and a time they can keep. Find the screen where they give up, and see what a simulated visitor does on each one before you change anything.

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

Why do new patients leave before they book online with a dentist?

New patients often leave at the first screen that asks for something they do not know yet: which visit to book, which dentist, whether they are new, or their insurance details. Check whether a time shows before the form asks for any of that. A simulated test sends a visitor through the booking on a phone and shows the step where they stopped and what they could not answer.

What this looks like in a report

Who
Mei, 34, moved to the area last month
How they arrived
Searched dentist online booking on her phone and opened the first practice
Where they stopped
Booking page, first screen, before any time was shown

“It wants me to pick a visit and a dentist. I am new, I do not know which dentist, and I am not sure hygiene means a cleaning. I will just call them.”

The fix. Put the next open new patient times on the first screen, and add an 'any dentist' option next to the dentist list. Rename each visit in plain words, such as new patient cleaning, then check the booking as a new patient on a phone.

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

New patients get stuck on questions they cannot answer yet

A phone call lets the front desk fill the gaps. A patient says they are new, the receptionist asks about insurance later, and the appointment still gets booked. An online form cannot do that. It asks for every answer up front, and a new patient often has to stop and find a card or a date before continuing. The worse case is order. If the calendar appears only after the details step, the patient has already given their date of birth and insurance before they know whether any time is open. Each unanswered question is a place to close the tab.

  • On a phone, can you see the booking button without scrolling or opening a menu?
  • Does the visit list name a new patient cleaning in plain words?
  • Is 'any dentist' an option, so a new patient does not have to know one?
  • Does a time appear before the form asks for date of birth or insurance?
  • If the booking sends a text code, does it reach the number typed on that same phone?

The order a new patient meets it

A new patient arrives from a search, usually on a phone. The first stop is the booking button. If it sits below the first screen, or inside a menu that only opens after a tap, many people will call the number they can see instead. The second stop is the visit list. Booking tools often label visits the way the front desk does, with names like recall or hygiene visit, so a new patient cannot tell which one is a cleaning. The third stop is the calendar. If new patient times are open for only one dentist, a patient who wants any dentist sees an empty week and leaves.

No open time, a form before the time, or a code that never comes

You can separate the causes by looking at the order of the screens, not at traffic. Open your booking as a new patient, on your own phone, in a private window. Count what the form asks for before the first open time appears. If no time appears for a new patient at all, the problem is availability: the calendar has nothing to show. If times appear but the form asks for date of birth, insurance and a reason before the patient can confirm, the problem is the order. If a time is chosen and the code never arrives, the problem is the phone field or the code step. Write down which one you hit first.

The task and visitor to send through now

Send one simulated visitor from your homepage with this task: book a new patient cleaning for next week. The visitor is an adult new to the area who searches for a dentist on a phone and needs a cleaning. The task makes the visitor pass every step on the way. Leave the dentist's name out of the task. A new patient does not know one yet, so a test that needs a particular dentist tells you about the name, not the booking. Run it again after each change and check whether the visitor now reaches the calendar.

Where the run stops: text codes, deposits and CAPTCHAs

A test ends at the first step a visitor cannot pass. Visitors have an email inbox, so an email confirmation reaches them. A code sent by text does not, because the visitor cannot read a phone. A deposit that needs a real card also ends the test at the payment step. A CAPTCHA on the booking page stops the visitor too, and the report marks that as blocked by the site. The test does not predict how many patients will book. It shows where a simulated visitor stopped and why. Use made-up details throughout, and do not type a real patient's name, date of birth or insurance number into it.

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 dentist on the calendar can hide the new patient times again

The first run finds the screen. The fix changes it: a visit renamed in plain words, an 'any dentist' option added, a field moved below the times. Run the same new patient again and see whether they reach the calendar or the confirmation. Repeat it after the booking tool changes, after a new dentist joins, and before you send paid traffic to the booking page.

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 this tell me how many patients will book online?

No. Mimiq does not predict booking rates, and it cannot say how many new patients will book in a month. It shows the step where a simulated visitor stopped and what the form asked for at that point. For rates, use your booking tool's own reports or your site analytics.

Can a visitor book a real appointment?

No. The test goes as far as the last step a visitor can reach. Visitors cannot receive a text code and cannot pay with a real card, so a booking that needs either stops there. If your booking takes a deposit, the test ends at the payment step.

Should I put real patient details into a test?

No. Give the visitor made-up details, and do not upload a list of patients or type a real patient's name, date of birth or insurance number into a test. A test does not check your booking for privacy or health records rules. Keep real patient records out of it entirely.

Can I test a booking widget that lives on another site?

Yes, if it loads in a normal browser at a public address. The visitor starts on your site and follows the booking link, so the handoff is covered. A booking app installed on a phone cannot be opened by a visitor, so test the web version that patients would see in their browser.

What if a CAPTCHA appears on the first booking screen?

The visitor stops there, and the report marks it as blocked by the site. Mimiq does not solve CAPTCHAs. If one shows on a phone, every new patient meets it too, so treat it as a problem with the booking, not only with the test.

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 .