Start with the room schedule
An escape room sells a session with a group size, a start time and a room capacity. Check that the software models those things directly. A simple appointment calendar may not handle your private groups, minimum charge or room turnaround the way you expect.
Write down one real operating day: each room's first session, game duration, reset time, minimum and maximum players, and any closures. Recreate it in a trial. Then book through the guest page and check what your team sees in the staff calendar.
- Can guests book outside your intended opening times?
- Does a private reservation remove the remaining places from sale?
- What happens when two guests try to take the last available session?
- When staff move or cancel a booking, does online availability update?
In Riddlio, start with room scheduling and availability. Test the exact capacity and booking mode your venue will use.
Try the whole booking on a phone
Do more than look at the first screen. Choose a room, change the player count, select a date, review the price and follow the payment step. Check the confirmation and find the booking reference. Someone who has not seen the dashboard should be able to understand the next step.
Embed the widget on a test page of your actual website. Check it on a narrow phone screen and a desktop. If payment opens a provider page or app, confirm that the handoff and return path make sense. A hosted booking link is also useful if you cannot change your website immediately.
Use the Riddlio booking-to-check-in walkthrough to see the guest and staff sides of a sample booking. Its screenshots use demo data.
Compare the total cost, not just the headline price
Ask each provider to separate the subscription, booking commission, payment processing, SMS, number rental, optional add-ons and applicable tax. Check whether annual billing, a minimum commitment or a particular payment gateway is required.
Use the same expected booking revenue, payment volume, message count and currency for every quote. A booking commission and a card-processing fee are different charges; paying one does not necessarily replace the other.
| Cost | What to ask |
|---|---|
| Software | Which plan covers your rooms, widgets, staff and required features? |
| Booking fees | Is there a percentage or fixed fee per booking, and who pays it? |
| Payments | What does the payment provider charge, including refunds or international cards? |
| Messages | Are SMS credits, long-message segments and a two-way number charged separately? |
| Switching | What migration, setup, training or cancellation charges apply? |
For illustration, a 2% booking fee on US$10,000 of bookings is US$200, before a subscription or payment processing. That is a worked calculation, not a quote from another provider.
Riddlio's monthly plans are US$29 for Starter, US$79 for Pro and US$199 for Unlimited, with 0% Riddlio booking commission. Provider fees, SMS usage and applicable taxes are separate. Compare current plans and limits; do not assume the lowest plan includes every feature.
Check what happens after payment
Run a test group through the arrival process. Can staff find the booking and any outstanding balance quickly? Can they tell which participants have completed the required waiver? Are internal notes clearly separated from messages sent to guests?
Use your venue's arrival policy. A request to arrive early should match your briefing and check-in routine, rather than another venue's default. Review reminder timing, cancellation wording and the phone number guests should call when running late.
Explore waivers and participant preparation, deposits and payment records, and daily venue management as separate parts of the decision. They do not all have to come from the same tool, but the handoffs need to work.
Plan the switch before changing your booking links
Ask for a sample import using data you are authorised to share. Review future bookings, customer details, outstanding balances and voucher balances separately. A successful booking import does not prove that historical payments, refunds or voucher liabilities have moved correctly.
- Export and keep a recovery copy from your existing provider.
- Agree which records will move, which fields are unavailable and how duplicates will be handled.
- Check sample bookings against the original source, including time zones and payment status.
- Test your new booking links, confirmations, payment connection and staff access.
- Choose a cutover time and account for reservations made during the transition.
Keep access to the old records for reconciliation and any legal retention needs. Do not charge a guest again because an imported booking lacks a new payment-provider receipt. For Riddlio migration help, contact the team before assuming a source export can be imported in full.
Bring these tests to a demo
Ask the person demonstrating the product to use your example, not only a prepared booking. Take notes on what is included, what needs an integration and what requires staff to do something manually.
- A private group at the minimum and maximum player count.
- A deposit booking with the remaining balance collected later.
- A rescheduled booking and the guest notification it produces.
- A voucher redemption and the balance left afterwards.
- A staff account with limited permissions.
- A mobile booking and a guest who needs help at arrival.
- A data export and the process for leaving the service.
The best fit is the system that meets your venue's requirements at a cost you understand. If Riddlio is on your shortlist, review the booking software overview, compare plans or book a demo around your own checklist.