By industry

Med spa consultation form: the unsure visitor

A visitor wants to fix the lines under her eyes before a wedding and cannot match that goal to a treatment name. Mimiq sends simulated visitors through your consult form and shows the field where each one stopped.

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

Why do undecided visitors stop on a med spa consultation form?

Undecided visitors stop on a med spa consultation form when a required treatment dropdown makes them name a treatment before the form will move on. A visitor who has a goal, such as smoother skin before an event, has to match it to a treatment name first. If the dropdown has no not sure option, the visitor either picks something they have not chosen or leaves to ask someone else. A simulated test sends a visitor with a goal and no treatment name, then shows the field where the request stopped.

What this looks like in a report

Who
Ilka, wants to fix the lines under her eyes before her sister's wedding
How they arrived
Clicked a search ad for med spa consultation near me
Where they stopped
Consultation form, on the required treatment dropdown

“I want something for the lines under my eyes before my sister's wedding. The list says neurotoxin, filler or laser. There's no not sure option, so I'll ask a friend first.”

The fix. Add a Not sure yet option above the treatment names, and make the treatment field optional. Add a goal box that asks what the visitor wants to change, such as lines under the eyes, and have the clinic reply with the options.

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

The treatment menu asks for a product before the visitor knows the problem

A med spa consult form usually starts with a dropdown. The options are the clinic's own treatment names, often grouped the way staff talk: injectables, energy devices, body contouring, skin. A visitor arrives with a problem, such as lines under the eyes or dark spots, and has to translate it into a product name before the form will continue. A visitor who has never had a treatment may not know the names well enough to choose. A required dropdown with no way out leaves a careful visitor choosing a treatment they do not want, or closing the tab.

  • Is there a not sure option at the top of the treatment dropdown, and is the field required?
  • Do the treatment names match the problems people search for, such as lines under the eyes?
  • Can a visitor describe a goal, such as a wedding next month, in a free-text box before choosing?
  • Does the form say what happens after it is sent, and whether a call or a text follows?

Treatment names a visitor cannot match to a problem

The clinic's treatment names are vocabulary the staff use every day. A first-time visitor lacks that vocabulary and searches with outcomes instead: fewer lines, less redness, a glow before an event. The dropdown cannot match the search, so the visitor either guesses or stops. Check it yourself. Type the outcomes new clients describe into your site's search box, or read your menu with them in mind, and see whether any one of them leads to a treatment name. If no page or heading on your site connects under-eye lines to a treatment name, the visitor has to make that link alone.

A required dropdown with no not sure option

A dropdown marked required is a question with one wrong answer for an undecided visitor. When every option is a treatment and none is a question, the visitor picks the nearest one or abandons. Picking the nearest one is worse for the clinic, because the consult then starts from a treatment the client never chose, and someone on the staff has to correct it later. The fix is structural: make the field optional, put a not sure option at the top, and let the goal box carry the question.

Look at the order of the fields too. A form that asks for a phone number before the goal makes a visitor hand over their number for a question they have not finished asking. The test shows the order in the run, from the first field to the send button, so you can see whether a visitor reached the goal box at all.

The confirmation text a simulated visitor cannot receive

Some forms say the clinic will text to confirm the consult, and ask for a mobile number that must receive a code. A simulated visitor has an email inbox but cannot receive a text, so a run stops at that step, and the report names it. That is a limit of the test, and it is also a warning: a visitor whose phone cannot take a text may not finish either. Ask the clinic what happens when the code does not arrive, then check that fallback by hand on a real phone.

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 treatment on the menu can push the not sure option out of view

Menus grow: a new device, a seasonal package, a new specialty. On a phone a longer dropdown can push the not sure option or the goal box below the fold. After each change, run the under-eye visitor again and check that the goal box still appears above the phone field. Then run a visitor who already knows the treatment, since a fix for the undecided visitor should not slow the decided one down.

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 a simulated test show how many visitors will request a consult?

No. The test does not predict how many visitors will request a consult, and it cannot say how many would have phoned instead. It shows the dropdown, goal box or confirmation where a simulated visitor stopped. Request counts come from your form tool and your inbox, not from a run.

Can a simulated visitor get through a text confirmation?

No. A visitor has an email inbox, so an email reaches it, but a visitor cannot receive a text message or type in a text code. A form that depends on one stops the run there, and the report names the step. Check the text path yourself with a real phone.

Should I put real health details into the consult form during a test?

No. Use invented answers, an invented name and a test inbox. Real consult forms can ask about medication or past treatments, but a test should never hold that information. Keep client details out of the run and out of any notes you add to the report.

Does the test judge whether a treatment suits a client?

No. The test shows whether a visitor can choose a treatment, describe a goal and send a request. It does not judge suitability, risk or what a practitioner would recommend. That call belongs to a clinician, after the consult.

Do I need to run it again when a new treatment joins the menu?

Yes. A new treatment adds a name to the dropdown, and it can push the not sure option out of view or change the order of the fields. Run the under-eye visitor again after each change, then one who already knows the treatment they want, to check both paths.

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 .