By industry
Vacation rental booking engine: fees and dates
A couple sees a nightly rate, picks dates and watches the total climb at the last screen. Mimiq sends simulated guests through your direct booking and shows which fee or blocked night made them leave.
Why do guests leave a vacation rental booking before checkout?
Guests compare the total with other listings, so a nightly rate that climbs at the end, from cleaning and service fees, makes them stop. Some calendars also block a night that is actually free, or refuse a check in day without saying why. A simulated test chooses dates and guests the way a family would and shows the screen where the total or the calendar changed the outcome.
What this looks like in a report
“The nightly rate looked fine. Now the total has a cleaning fee, a service fee and a tax line I did not see, and the toddler seems to count too. I can't tell what I'd be paying for.”
The fix. Show the cleaning fee and any guest charge in the nightly rate line once dates are picked, and show the full total on the first results row. Put the minimum stay next to the date picker, so a family sees it before choosing a Monday check in.
An illustration. Run a test to see your own.See a real sample report
The total changes after the dates are picked
A family finds a house with a nightly rate that looks reasonable and picks their dates. The results page shows the rate, then the checkout adds a cleaning fee, a service fee and a tax line they did not see. The total is higher than the rate multiplied by the nights, and the difference only appears at the last step. A date they wanted may also be greyed out for no reason they can see, or the form may refuse a stay that starts on a Monday. The family compares the total with another house and leaves.
- Pick dates and guests. Are the cleaning fee and service fee shown before the checkout step?
- Pick a check in day you know is free. Does the calendar let you choose it?
- Does a minimum stay appear next to the date picker, or only after a short stay is picked?
- Add a child or an infant. Do the guest count and the total change on the same screen?
- Does the total on the results page match the total at the payment step?
The fees that appear after the rate
A rate shown first and fees shown later is common in rental booking, and it is hard to judge from the owner's side because the owner knows every fee already. A guest meets the rate in a large type size, and the fees arrive in a small line at the bottom of the summary. Check the order on your own booking. Choose dates and guests, then write down the first screen where the total appears and the first screen where a fee appears. If the first total is lower than the last one, the difference is what a guest will compare with another listing, and it is the one part of the flow they cannot see until the end.
Blocked nights, minimum stays and the check in day
A night can show as blocked because of a real booking, a block the owner set, or a sync from another calendar that has not cleared. A guest cannot tell which one they hit. A minimum stay can also stay hidden until a short stay is chosen, so the guest sees a free Monday, picks it, and gets a message they did not expect. To check, pick a night you know is free, then one you know is booked, then a short stay on a day with a minimum. Note whether the calendar explains each refusal in words a guest would understand.
Toddlers and infants show how the guest count works
A toddler is the booking that exposes the guest count. Some forms count an infant in the guest field and some do not, and a guest limit lower than the sleeping arrangement sends a family away after they have built their stay. Test a family with a toddler and an infant, and check whether the total changes on the same screen as the count. The limit belongs next to the guest field, not only in the house rules at the bottom of the page.
Five ways to find where a direct booking guest leaves
| Method | What it shows | What it misses |
|---|---|---|
| Analytics funnel | Where visitors leave between pages and how many reach checkout | Why they left, and what the total or calendar showed them |
| Session replay | What one real guest did on each screen, including hesitation and scrolling | Guests you never recorded, and screens nobody reached |
| Scripted end to end test | Whether a fixed path still reaches the payment step after a change | Whether the path makes sense to a guest who is comparing prices |
| Simulated guest run | The screen where a guest with a stated task stopped, and what the page said | Real booking rates, real prices and what real guests decide |
| Guest interviews | Why a real person thought the total was too high | How many other guests think the same, unless you ask many |
The methods answer different questions, and none of them tells you how many guests will book.
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 minimum stay or calendar sync can block dates you thought were open
The first run finds the night or the fee that stopped the guest. The fix changes the minimum stay, the fee line or the calendar sync, and a later change to any of them can bring the problem back. Run the same couple through after each change, then the family with a toddler, so both the total and the guest count get checked. Repeat it before a busy season or whenever you add a booking channel.
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 guests will book a stay directly?
No. It does not predict how many guests will book, and it cannot tell you how many leave for another listing. It shows the screen where a simulated guest stopped and what the total or calendar said at that point. Booking rates come from your reservation records and your analytics.
Will a test hold a night on my calendar?
The test goes up to the payment step and stops. Visitors can read email, so a confirmation email reaches them, but they cannot pay with a real card. If your calendar holds a night before payment, a test can leave a hold behind, so point the test at a staging calendar if you have one.
Should I give a real guest's name and card in a test?
No. Use invented guests, invented dates on a test calendar if you have one, and a test email inbox. Screenshots in the report show what the visitor typed, so keep real guest names, card details and booking records out of the run.
Does the test check the house or the reviews?
No. The test checks whether a guest can read the total, pick dates and reach the payment step. It does not check the property, whether the photos match the real house, the reviews or the local rental rules. Those belong to your own checks and the rules for your area.
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.